Try OGGM online¶
You can try OGGM in your web browser without having to install anything! This is the best way to run the tutorials or even do exploratory research to test the model, before you move on to more serious computations.
Binder is the solution available to anyone without registration, but provide only temporary environments. Perfect for the tutorials!
OGGM-Hub is our own deployment on our cloud resources. Use OGGM-Hub if you want to rely on a persistent environment and more computing resources to run your experiments.
Using Binder is very simple. Just click on the link below to get you started!
If you are new to the Jupyter Notebooks or to Binder, you will probably find this introduction on OGGM-Edu quite useful.
Important: Binder environments are only temporary! Perfect for trying and learning, but not suitable for development work.
This is our own JupyterHub deployment of OGGM on the cloud.
Thanks to a grant from Google’s Data Solutions for Change, we are able to provide free resources to anyone interested in using and testing OGGM more seriously. In order to be able to log-in on hub.oggm.org, you will need to have a Github account (it’s free!) and be a registered member of the OGGM, pangeo-data or informatics-lab github organisations. Get in touch if you want to try it out!
hub.oggm.org is still experimental and we cannot guarantee that your work will always be safe here. We will do our best, but, you know, we are scientists after all. Please, make a copy of your files from time to time!
How does this work?¶
We use resources provided by Google Cloud to run a virtual cluster. This cluster “scales” with the number of users logged-in at each time: each user gets a fixed amount of computing resources and when the demand grows, the cluster grows. This is why logging-in can take longer or shorter, depending on the cluster load at that time.
Currently (we are still trying things out), each user gets up to 2 CPUs (4 processes) and enough RAM to run OGGM. This is not enough to do heavy work, but will get you through the exploratory phase or even small regional runs. Each user also gets a persistent 10Gb disk so save input data, notebooks and scripts.
Pulling the tutorials (and other content) with nbgitpuller¶
The command that is executed at each log-in is:
$ gitpuller https://github.com/OGGM/oggm-edu-notebooks master notebooks
Which means that the OGGM-Edu notebooks are copied into the notebooks folder in your home directory. You can use the a similar command in your lab’s terminal to pull content from other repositories as well. Another way to pull content is to use a special link to open your hub. Say, for example, that you would like to download the content of Lizz’ glacier course in your lab as well. You can use the link generator to create the following link which, once clicked, will open your workspace with the new notebooks in it:
nbgitpuller will never overwrite changes that the user made to the files in the pulled folder. This is very important to remember: sometimes your students would like to get an updated version of the notebooks for example, and this will not work if the file changed. Therefore, it is always a good idea to make a working copy of the original file/folder before working in it (right-click -> rename).
The full set of rules used by nbgitpuller while pulling is explained here
FAQ: copy-pasting text in the terminal in JupyterLab¶
Copying to and from JupyterLab can be annoying at times (context). This is one of the most frequent issue hitting users of JupyterLab, when: - working in a terminal (Launcher -> Start a terminal), - selecting text from the output of jupyter cells.
In these cases, press
shift + right click to experience a standard
“copy/paste” mouse menu.