Starting an application
Outcome You launch an application and have it open ready for use.
Before you start
The application has been added to an Instance you have access to.
You hold at least the Instance Editor role in that instance (applications can only run with Editor rights).
You are signed in to Nuvolos.
Applications are the interactive tools you use to do your work - JupyterLab, RStudio, MATLAB, VS Code, and others. The procedure below works the same for any role; what differs is who installed the application and where it lives in your space. For the conceptual model, see Concepts › How Applications work.
Start from the Dashboard
The fastest path when the application has been used recently:
Go to the Dashboard of the organisation that contains your course or project.
Your three most recently used applications are listed.
Click the application name to open it.
Start from your Instance
Use this path the first time you start an application, or when the application is not in your recent list:
Navigate to the space containing your instance.
Navigate to the instance.
Make sure you are in the Current state - applications can only run in the Current state, not in a snapshot view.
On the sidebar, click the screen icon (applications) to see the Application list.
Click the power button or the application name to start it.
Application startup typically takes 30–60 seconds. The first start may take longer if packages or configuration files need to be initialised. If the first start exceeds about 5 minutes, the cohort or environment may need pre-warming - ask the Space Administrator.
Role-specific notes
You start applications in the Master Instance to develop and maintain teaching material. To pre-start applications for an entire student cohort (so students don't all wait at once during a session), see How-to › For Instructors › Pre-start student Applications.
If your course uses GPU Lab Sessions, your instructor schedules the GPU-enabled application - you don't start it yourself. Hover over the Application icon to confirm GPU is enabled (a green badge with the GPU model appears). See How-to › For Students › Work with a GPU in a course for the full distinction between Lab Sessions and On-Demand GPU access.
Application startup time matters more for credit-based GPU sizes than for Included sizes - Credit charges start when you click the start button, not when the web UI loads. Make sure you have at least 30 consecutive minutes available before starting a credit-based application.
Last updated
Was this helpful?