![]() ![]() Switching To Classic Notebooksįor users who would prefer using the Classic Notebook interface, simply go to the commands tab on the left hand side and go to Help > Launch Classic Notebook. We also encourage you to check out the tutorials that are available at ‘JupyterLinks/tutorialNotebooks’ on all of the systems. For more information on JupyterLab usage check out documentation here. Once you have logged in and been allocated resources for your session, you will be dropped by default into the JupyterLab IDE. To access the hub control panel, in JupyterLab go to File > Hub Control Panel, or in the Classic Notebook go to the “Control Panel” button in the upper right hand corner of your window. The session will only terminate if you run out of time in your Slurm allocation or if you click “Stop My Server” on the Hub Control Panel. Regardless of whether you close your browser or not, or even log out, your session will persist, and your work will still run. It is also important to understand how your session will (and will not) terminate. Or in the Classic Notebook, click the running tab on the top of your screen.In JupyterLab, click the icon on the left hand side that looks like a circle with a square inside.If you are running multiple notebooks, consoles, and/or terminals, they will be competing for your own resources. Once you have an allocation, whatever you do inside of the session will be constrained to the resources allocated by Slurm. If you would update your default allocation, please contact support. ![]() Please note that any jobs that you submit through the Jupyter session will not be constrained to this default. At this time when your session starts it will be billed to your default allocation. We are working on integrating this functionality in the future. We currently do not support non-default allocation selection when spawning Jupyter sessions. If your use case seems to require a different job profile, please submit a ticket to NCCS Support by messaging users on the Discover JupyterHub, the session is charged to your default project allocation. Keep in mind that, if there aren’t resources available, you will not be able to get a session. These options will provide different tiers of resources to be allocated to your session. Once you have logged into one of the hubs, you will be presented with a drop-down menu to select a job profile. While you do not need to know how to use Slurm to use JupyterHub, it is useful to know that your Jupyter user session will be effectively a Slurm job running on the backend compute associated with the hub. Session allocation on JupyterHub is handled through the Slurm scheduler. If you have forgotten or need to reset your password, click here. Once you have connected to one of the above hubs, you will need to log in with your NCCS LDAP username and password. While we offer broad access to resources on ADAPT and Discover, if your group would like a JupyterHub for your team's ADAPT VMs not listed here, please send a request to Logging In Once you have submitted your request, please send a ticket to NCCS support stating which specific JupyterHub you are requesting and we will ensure that you have access. Note that you will only be able to submit NAMS requests from the NASA network/VPN. If so, you will have to create a NAMS request for either 'NCCS Discover JupyterHub' (link to asset) for accessing the Discover hub, or ' NCCS Web Services' for any of the ADAPT hubs. When attempting to connect to any of the hubs, you may be prompted to submit a NAMS request. Please note: Access to some of the JupyterHub sites may only be accessed from the NASA network or via VPN. We currently have the following JupyterHubs deployed: Your browser does not support HTML5 video.įor more information on Anaconda environments, check out the “Anaconda on ADAPT” video in the full collection of NCCS Instructional videos. ![]()
0 Comments
Leave a Reply. |