Getting in
- Logging in
- Enrolment is closed; log in every time at the same address
Go to app.nuvolos.cloud and sign in. If you are registered for the course but never enrolled, or you cannot get in, email the teaching assistant from your university address.
- Which account
- The one you enrolled with
Log in with the account you enrolled with. If you no longer know which one that was, email the teaching assistant from your university address.
- First login
- Organisation, space, instance
Nuvolos is organised as HEC Lausanne → Advanced Data Analytics 2026 → your own instance, named after your email. Everything you do lives in that instance. Nobody else sees it, and nothing you do there affects anyone else.
- Nothing to install
- Everything runs in the browser
No Python, no Anaconda, no packages on your laptop. Any machine with a browser will do. Your files persist between sessions and across devices.
Starting to work
- Start JupyterLab
- Applications, then the power button next to JupyterLab
In the left-hand column of your instance, open Applications. The course application is JupyterLab 4.5.0 with Python 3.12 and TeX Live, and every package used in the course is already installed in it. Click its name or the power button; the first start takes a minute, later ones a few seconds. It opens in a new tab.
- If no application is listed
- Add it once from the catalogue
Click the plus next to Applications, search for JupyterLab, and add the entry that says Python 3.12 and TeX Live. Then start it as above. If a package is missing when you run a notebook,
pip install <name> in a terminal installs it into your workspace, and tell the teaching assistant so it is added for everyone.
- Your files
/files is your workspace; JupyterLab opens in it
The file browser on the left of JupyterLab shows the same folders as Files in the Nuvolos sidebar. You will find README.md, the guide to the workspace, and refresher/. Week folders appear after each Monday's session.- Open a notebook
- Go into its folder first, then double-click it
Every notebook expects to be run from the folder it lives in, so that its data files are found. Run cells with Shift+Enter. If a notebook misbehaves, Kernel → Restart Kernel and Run All Cells is the first thing to try.
- The refresher
- Twelve short notebooks, from calculator to pandas
In
refresher/. If you have not written Python for a while, work through them this week and next, in order; they are also readable here. Nothing is submitted.
Two rules and a habit
- Week folders get overwritten
- Keep your own work outside them
When material for a week is updated, the whole
week-NN/ folder is replaced, and your edits inside it are gone. Copy a notebook to a folder of your own (my-work/, for example) before you change it.
- Stop the application when you are done
- Power button in Applications
Your files are saved continuously; stopping the application loses nothing. It frees the compute that the course is given for free, and it avoids the "already running elsewhere" message when you log in from another machine.
- A terminal is one click away
- File → New → Terminal, inside JupyterLab
For
pip, git, and running scripts. The project you will build later is a git repository; the terminal here is where it can live and run.
When something is wrong
- "You are not a member of this space"
- You logged in with a different account than you enrolled with
Log out, and sign in with the account you enrolled with. If you cannot remember which, email the teaching assistant with both addresses.
- The workspace is empty
- Material arrives by distribution
Refresh the Files view. If
README.md and refresher/ are still not there, email the teaching assistant; everything is also downloadable from this site in the meantime.
- Anything else
- anna.smirnova@unil.ch
Say what you clicked and what you saw; a screenshot helps more than a description.
