
The preferred method of running Jupyter at NCI is through the ' Open on Demand' (OOD) service.


Jupyter provides a 'notebook' interface for working with Python - you can combine Python code, text, latex equations and plots in a web interface. To recreate the environment from the environment file:Ĭonda env create -f environment.yml Interactive Analysis / Jupyter You can use any name for the environment file. Files on scratch are deleted if no longer used, so this file allows you to re-create your environment if some of the files are deleted. You can create your own environment if needed, but please be cautious of both the size on disk and number of files that Conda environments can create.Ĭreate an environment file: environment.yml. Conda environment.yml descriptions of past environments are available at. Normally after three quarters have passed old environments are removed, to reduce disk space and support burden. When we do our quarterly update the unstable environment becomes the new stable environment. If you ask for a new package it will be installed here. The unstable environment gets updated more often, as we install new packages or apply updates to existing ones. Module load conda/analysis3 Unstable Environment Otherwise everything in the environment stays fixed, we don't update packages or install new packages unless something is very broken. We update the stable environment once a quarter, around when NCI do their quarterly maintenance of Gadi. They do not work on accessdev, as this has a very old system version that is no longer compatible. Note that these conda environments will work on gadi login and compute nodes, and in the OOD cloud environment. If you need to use the conda environment in a PBS job you will need to add the hh5 project to your storage flags, e.g. It can go in the if in_interactive_shell then section of the file.

You can safely put this in your ~/.bashrc file.

CMS maintain an Anaconda Python environment at NCI, with a wide variety of climate and weather related libraries.
