...
Before getting started please ensure you are familiar with the following:
The University's ssh Protocols
The University's Research Storage
...
Files in this artifact are readable and writable. This space is useful for living files that are being edited and worked on. Files such as Jupyter notebooks (.ipynb), python scripts, etc, are useful to put here as you work on them between sessions. It is wise to always have a workspace mounted as a save space for in progress files.
Results
This directory exists in each job and can be used to direct outputs into. Doing so ensures that your outputs are available post job completion.
**Do not save notebooks or files in directories that are not under /mount or under /results**
You can also download datasets and workspaces, and convert them to results as well to reupload re-upload into other spaces. For example, if you are finished working on a script in a workspace, you might download and then reupload it as a dataset such that you have an immutable copy of the script to reference. Once you have selected a dataset or workspace to include, a text box will appear under the 'Mount Point' column. Here you can enter /mount/data, or any other custom path to your data or workspace. In your Jupyter Notebook, you can access this data using this path. Scrolling down even further will show a /results path for any output you may generate.
...
Finally, to start the job scroll down to the Launch Job section. The default runtime for a job is 30 days (2592000 seconds).
Job Priority should always be set to Normal. Changing this priority can disrupt jobs for other users, and if everyone sets the priority to High, then no one is prioritized. Please respect your colleagues by not using higher-priority values in this field. ITS may terminate jobs that disrupt the useability of computing resources.
Preemption Options should be 'Resumable'. This ensures that your job can be paused if the system experiences high usage or needs to be taken down for maintenance.
Job Order will run jobs in the order specified, ranging from 1 to 99. If you submit two jobs, one with order 2, and another with order 1, the job with order 1 will execute first. This ordering is only relevant to you as the user and does not affect other users. The default value if left blank is 50. In the CLI, one can set job order using the --order flag, here is an example job submitted with order 66.
...