If you are new to DKRZ and want to access our JupyterHub, please consult the Quick Start page.
If the batch queue is filled with waiting jobs, it might take some time to start the notebook server. There is an internal timelimit specified until which the resources should be ready. If not the spawner will reject and ask you to start again (maybe with reduced resources specified).
On September 1st, 2020, we deployed a new version of our Jupyterhub server. Check the Changelog for all notable changes. Furthermore, the new release has been also presented during the DKRZ Tech Talks.
You can switch from
lab notebook simply by adding
/tree in the URL.
Undo this operation to go back to switch again to
If you encounter any issue or you have request for new features, please send us an e-mail to email@example.com.
There are a few points you should be aware of when working with Jupyter Notebooks on the jupyterhub server:
Sessions are persistent. If you close the browser tab without stopping the server before, you can revisit the jupyterhub site and carry on working
Closing browser’s tab or log-in out will not stop your session, your session will continue consuming resources (see next point)
- It is preferable to close the session when you finish. This depends on how you started the session (preset, advanced)
Hub Control Panel-> (preset/advanced) and then
Control Panel-> (preset/advanced) and then
SLURMmight cancel your server session if a timeout occurs after 8 hours
stderrof the SLURM batch job that is spawned by Jupyterhub is written to your
HOMEdirectory on the HPC system. In order to make it simple to locate the log file:
if you use the
presetoptions form: the log file is named
if you use the
advancedoptions form: the log file is named
jupyterhub_slurmspawner_advanced_<id>.log. You can even change the name of the output log file (
Log File Name).
Log File Namealso allows you to change the
Pathof the output log file to a diffrent directory where you have write permissions. Example: