execnotebook
The execnotebook
command allows a user to execute a Jupyter notebook for up to 24 hours without staying connected to the cluster. Users are recommended to checkpoint their work to prevent data loss.
Prerequisites
- The user must have executed
mynotebook
prior to runningexecnotebook
- The .ipynb file must not be located in the scratch directory.
Limitations
- Each job will be executed for up to 24 hours.
- Users should wait for the job to complete before reading or writing to the .ipynb file.
Guide to using execnotebook
-
On the cluster execute the command
execnotebook
-
You will be prompted for the filename of the ipynb file you would want the program to execute
-
Input the ipynb filename and press enter
Location of ipynb files
The ipynb files must be located within your home directory.
-
Input your email address when prompted
-
Select the build environment you require
Modules
Modules loaded in your Jupyter notebook will not be affected by the options selected here
-
Select if you would want to override your existing notebook
Overwriting files
If you choose to overwrite the notebook, the output format of the new ipynb file will be
nameofnotebook.output.ddmmyyyyHHMMSS.ipynb
-
Select your GPU requirements
-
Displayed screen upon successful job submission
Submitted batch job 1742 ======================= JOB QUEUE ======================= JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON) 1742 project ipynbRun IS000G3 R 11:32:05 1 aloha ======================= JOB QUEUE ======================= ===================== Job states ======================== R = RUNNING | PD = PENDING | F = FAILED | CG = COMPLETING ===================== Job states ======================== ...output redacted
Troubleshooting & Tips
Job state is pending
Refer to the myinfo
command to find out more about entitlement for concurrent jobs.