...
Jupyterlab would effectively run within a job on the Atos HPCF or ECS with certain resources on the allocated node for the job, and would allow you to conveniently interact with it from your browser without the need of any other connection to the HPCF using other methods.
| Note | ||
|---|---|---|
| ||
All JupyterLab sessions running on this service are time limited. When the time is up, the instance will be killed automatically along with any active processing that may be taking place. . You can only have one JupyterLab instance running. If you left one running, JupyterHub will connect you straight back into it. |
First use: enabling access to your account from JupyterHub
...
| Tip | ||
|---|---|---|
| ||
By default, the session standard output will not be saved. If you run into problems starting JupyterLab, or something does not work as you would expect once within JupyterLab, you may enable the debug option to generate the job output in your HOME directory, which will be directed to a file called
|
When you are ready, click Start
You may need to wait between 30 seconds and several minutes for the system to schedule your new job and connect to your new JupyterLab session
After a few minutes, your session will be up and running. Take note of the finishing time at the top right corner of the page. Your session will be terminated automatically once that time is reached.
Stopping your JupyterLab
To stop your JupyterLab session, you may go to the top bar menu, and then click on File - Hub Control Panel
This will bring you back to your JupyterHub Home, from which you will be able to Stop your server (red button) or connect back to it (blue button)
