Re: Courselab Product Key

0 views
Skip to first unread message
Message has been deleted

Sibyl Piccuillo

unread,
Jul 11, 2024, 11:11:05 PM7/11/24
to mingpagarlo

The department maintains general-purpose machines called "courselab" (currently, two machines that each have 2 Intel Xeon E5 2670v3 processors and 128GB of DDR4 2133MHz memory) and "armlab" (currently, two machines that each have 2 ThunderX CP 48-core processors and 128GB of DDR4 2400MHz memory). These machines are accessible via SSH at courselab.cs.princeton.edu or at armlab.cs.princeton.edu using one's NetID and OIT password. The USB Boot only machines in FC 011 and FC 012 are dedicated for courses where students develop custom boot loaders (e.g., COS 318).

In order to get access to courselab you must first get access to the OIT Nobel System. This page will guide through getting access to Nobel. You will need to set your Unix shell which you can do by reading "see Unix: How do I enable/change the default Unix shell on my account?". Here is the direct link to update your Unix shell. After your shell has been set you will need to ssh to Nobel by using the following SSH command:

Courselab Product Key


Download https://pimlm.com/2yVSmf



Accounts on the courselab machines are removed at the end of the semester. If you would like to keep your files please make sure you copy your files off the lab machines before the end of the semester.

The Unix shell on these machines is the same one that is used when a user logs in to an OIT Unix machine (e.g., hats). As a consequence, if you have not enabled your OIT account to be able to access the Unix machines (and set a shell), you will also not be able to login to the courselab machines. To enable Unix access and specify a particular shell (/bin/bash is a good choice if you don't otherwise have a preference), see this OIT KnowledgeBase article: Unix: How do I enable/change the default Unix shell on my account?

Navigation buttons are inactive - there could be a lot of reasons for it. First, if there's no previous (or next) slide, then corresponding button (previous or next) becomes inactive automatically. Second, if you use Strict Navigation mode in navigation buttons object (see checkbox in object properties - it is on by default), then buttons become inactive while slide content is played - depending on slide content actions, delays and transitions. Third, if you switch off navigation buttons manually by NAVIGATION action, then they will be inactive until you switch them on by the same action. These reasons are most probable. Also feel free to ask our Support at sup...@courselab.com or at CourseLab Support section of our site.

I've already answered your question on CourseLab forums. In short, it may be the bug that is already fixed, but to be sure we need to test your course sample to give you correct recommendations. Please send the short sample to sup...@courselab.com


I don't want to see the course structure in the Moodle pane, just the tabs for contents. how do i switch this off in courselab please? When i run my module in scorm cloud the extra menu isn't there (that's the way i want it to look). reload scorm player also doesn't show the extra menu. when it plays in moodle it shows and i need to switch it off please. i took a screenshot but it's bigger than permitted file size

A request to open consists of the client's key and an identifier for every lab, which is likely to be a combination of the course name and the lab name (i.e. courselab for autograding jobs). open checks if a directory for courselab exists. If a directory for courselab exists, a dict of MD5 hashes corresponding to every file in that directory is returned. If the directory does not exist, it is created and a folder for output files is also created within the courselab directory. Since no files exist in the newly created directory, an empty dict of MD5 hashes is returned.

After uploading the appropriate files, the client uses this command to run the job for the files specified as files in the courselab and on an instance of a particular VM image. Each file has localFile and destFile attributes which specify what the file is called on the Tango server and what it should be called when copied over to a VM (for autograding) respectively. Exactly one of the specified files should have the destFile attribute set to Makefile, and the Makefile must contain a rule called autograde. Clients can also specify an optional timeout value (timeout) and maximum output file size (max_kb). This command is non-blocking and returns immediately with a status message. Additionally, the command accepts an optional parameter, callback_url. If the callback_url is specified, then the Tango server sends a POST request to the callback_url with the output file once the job is terminated. If the callback_url is not specified, the client can then send a poll request for the output_file to check the status of that job and retrieve the output file from the Tango server if autograding is complete.

aa06259810
Reply all
Reply to author
Forward
0 new messages