2025-12-16T19:17:42Z

Willis2: /* Job submission */

{|align=right
|-
|[[Image:ood-logo.png|480px]]
|-
|}

= Porting existing virtual environments to Open OnDemand =

'''IMPORTANT: Because of the change of operating system and software stack, your exisiting virtual environment kernels for Python may not work right away in the OnDemand site. You should be able to activate your python environments in a Trillium terminal (see [[Open_OnDemand_Quickstart#Terminal access|Terminal access]]), with all required Trillium modules loaded, and then issue the command <code>venv2jup</code> to get them working correctly.'''

=Introduction=

This guide will walk you through the basic steps to get started with the SciNet Open OnDemand portal.
Open OnDemand (OOD) is a web-based platform that provides access to a wide range of scientific applications and computing resources, such as Jupyter Lab, R Studio, and VS Code. It allows you to interact with Trillium through a web browser instead of via a terminal, without the need to install any software on your local machine. You will be able to perform file management, submit/monitor jobs and run applications interactively. More information on this project can be found at [https://openondemand.org https://openondemand.org].

=Logging into the Open OnDemand portal=

[[Image:ood-dashboard.png|thumb|right|600px|Figure 1: Dashboard.]]

To access the Open OnDemand portal, open a web browser and navigate to the following page: https://ondemand.scinet.utoronto.ca. You will be prompted to enter your Alliance username and password, followed by a second factor authentication via Duo or Yubikey. Once you have logged in, you will be taken to the Open OnDemand dashboard. From here you can access the various tools and applications available on the platform.

=File management=

[[Image:ood-file-browser.png|thumb|right|600px|Figure 2: File browser.]]

The Open OnDemand platform provides a file browser that allows you to manage your files and directories on the filesystem. To access the file browser, click on the '''Files''' tab and select which directory you want to manage from the drop-down (<code>HOME</code>, <code>SCRATCH</code> or <code>PROJECT</code>). You will be taken to the file browser interface, where you can:

* Navigate through your directories
* Upload/download files
* Create new files/directories
* Delete files/directories
* Edit existing files

==Uploading files==

The current file size upload limit is 10GB, if you need to upload a file larger than this or are facing upload issues due to a bad internet connection for example please try using [https://docs.scinet.utoronto.ca/index.php/Globus Globus]. There is a Globus button in the file browser at the top right, [[File:Globus_button.png | 300px]], which will take you to the Globus web interface where you can login with your Alliance username and password. The path navigated to in the Open OnDemand file browser will be the same path opened in Globus.

=Job submission=

Open OnDemand also provides a job submission interface that allows you to submit batch jobs to Trillium.

The [https://github.com/RIKEN-RCCS/OpenComposer Open Composer] app provides a suite of Slurm job template scripts that can be submitted directly to the Trillium scheduler. It also provides an interface to monitor your submitted jobs, via the '''History''' tab. You can access Open Composer by navigating to the '''Jobs''' drop-down menu and selecting '''Open Composer''' or by clicking on one of the Slurm job templates e.g. '''MPI Slurm Job''', '''OpenMP Slurm Job''' and '''Hybrid MPI/OpenMP Slurm Job'''.

[[Image:ood-oc-shortcuts.png|thumb|right|600px|Figure 3: Open Composer shortcuts.]]

Once you have selected a job template, you will be taken to the job submission page. This is split between the job parameters on the left and the job script itself on the right. The job parameters let you control how many resources your job will use, such as the number of nodes, number of tasks per node, wall clock time and output file name. The job script section displays the script that will be submitted to the scheduler. Any changes made to the job parameters will be reflected in the job script automatically. You may also edit the job script directly if you wish.

The extra fields at the top of the page allow you to change how your job is submitted:

* '''Script Location''': specifies the directory where the job script will be saved and where your job will be run from.
* '''Script Name''': specifies the name of the job script file.
* '''Job Name''': specifies the name of the job that will appear in the job queue.
* '''Cluster''': allows you to change which cluster to submit your job to, e.g. Trillium (default) or Trillium-GPU. Selecting Trillium-GPU will provide an additional job parameter to request GPU resources [[File:ood-oc-gpus.png | 200px]].

Once you are happy with your job script, click on the '''Submit''' button to submit the job to the scheduler and save your script to the '''Script Location'''. If your job was submitted successfully, you will see a confirmation message at the top of the page with your job ID: [[File:ood-oc-job-submit.png | 400px]].

[[Image:ood-oc-job.png|thumb|center|600px|Figure 4: Open Composer job script editor.]]

Note: The template scripts provided in Open Composer are basic examples to get you started. You will need to modify the job script further to suit your specific needs, such as loading your required modules and specifying input/output files.

==Monitoring jobs in Open Composer==

To monitor your submitted jobs in Open Composer, navigate to the '''History''' tab. This will display a list of all your submitted jobs, along with their status: Queued, Running, Completed, Failed. You can filter the jobs by using the '''Filter''' text box at the top right or by using the checkboxes below. Clicking on different column fields will give different information about the job:

* '''Job ID''': displays detailed Slurm information about the job
* '''Application''': opens the job script editor of the template you used
* '''Script Location''': opens an OOD file browser window at the location of the job script. Clicking on the the small terminal icon will open a terminal in the job script location.
* '''Script Name''': displays the job script that was submitted to the scheduler

To resubmit or modify a previously run job click on the job script under the '''Script Name''' column and click '''Load Parameters'''. This will take you back to the job submission page where further modifications can be made to the job.

[[Image:ood-oc-history.png|thumb|center|600px|Figure 5: Open Composer job monitoring.]]

==Supported applications==

Open Composer currently supports the following applications:

* MPI Slurm Job
* OpenMP Slurm Job
* Hybrid MPI/OpenMP Slurm Job
* Python Slurm Job

=Job monitoring=

To get an overview of all your jobs in the queue you can use the job monitoring interface. Navigate to the '''Jobs''' tab and select '''Active Jobs'''. You can filter the jobs by using the '''Filter''' text box at the top right. Columns can also be sorted by clicking on the column headers, for example you can sort by job status (running, completed, failed, etc.). Clicking on <code>></code> to the left of a job will show you more details about the job, such as the start/end time, node list and account charged etc. You might also want to show all jobs in the queue, you can do this by clicking on the drop-down menu at the top right and selecting '''All Jobs'''. A more detailed view of your jobs can still be found using the [https://my.scinet.utoronto.ca myscinet portal].

[[Image:ood-active-jobs.png|thumb|center|600px|Figure 6: Active Jobs.]]

=Interactive applications=

Open OnDemand also features interactive applications that can be run directly from your web browser. To access the applications, navigate to the '''Interactive Apps''' tab and select the application you want to run from the drop-down. This will then bring you to the job submission page where you can choose job parameters such as:

* Length of job in hours
* Number of cores
* Amount of memory to allocate (GB)
* Notify me by email when the job starts

When you have chosen your job parameters click on the '''Launch''' button to submit your job to the queue. You will be taken to the '''My Interactive Sessions''' page where you can see the status of your job, i.e. queued, running or completed. Once the job has been assigned a node and is running, you can click on the '''Connect to ...''' button to launch the application. The application will open in a new tab in your browser, and you can interact with it as if it was running locally.

If you would like terminal access to the node where the application is running, to monitor the performance for example you can click on the button beside '''Host''' starting with <code>>_</code>. This will open a terminal window in your browser where you can run commands on the node directly.

If for whatever reason you would like to kill the job, you can do so by clicking on the red '''Delete''' button in the job panel in the '''My Interactive Sessions''' page.

<div style="margin: 0 auto; display: table;">
{| class="wikitable"
|-
| <div style="text-align: center;">
[[Image:jupyter-submit.png|600px]]
 Figure 7: Interactive app submission form.
</div>
| <div style="text-align: center;">
[[Image:ood_session_tab.png|600px]]
 Figure 8: Interactive sessions page.
[[Image:jupyter-session.png|600px]]
 Figure 9: Interactive app session.
</div>
|}
</div>

==Installed applications==

We currently support the following applications:

* [https://jupyter.org Jupyter Lab/Notebook]
* [https://posit.co/products/open-source/rstudio/?sid=1 Rstudio]
* [https://code.visualstudio.com VSCode]
* Trillium Desktop
* [https://www.paraview.org ParaView]
* [https://www.linaroforge.com Forge DDT/MAP]
* [https://www.sas.com/en_ca/home.html SAS]4
* [https://www.stata.com Stata]4
* [https://github.com/RIKEN-RCCS/OpenComposer Open Composer]

If you would like an application installed please email us at: [mailto:support@scinet.utoronto.ca support@scinet.utoronto.ca].

=Running an application GUI=

If you would like to run software that has a graphical user interface (GUI) and is not yet installed as an interactive application, such as Octave or Blender, you can do so using the '''Trillium Desktop''' application. This app provides a remote desktop environment that you can access through your web browser. In the following example we will run Octave's GUI:

# Navigate to the '''Interactive Apps''' tab and select '''Trillium Desktop''' from the drop-down.
# You will be taken to the job submission page. Choose how many cores and amount of memory you would like to allocate for your session in addition to your job length in hours. Then click on the '''Launch''' button to submit your job to the queue.
# This will take you to the '''My Interactive Sessions''' page. Once your job is running, you have the option to improve the '''Image Quality''' and '''Image Compression''' of the desktop session. Depending on the speed of your internet connection you may want to set these lower to improve performance and responsiveness of the desktop. Click on the '''Connect to Trillium Desktop''' button to launch the remote desktop environment in a new tab.
# Once the desktop environment has loaded, open a terminal window using the desktop shortcut and load the required modules for Octave:
#:<pre> $ module load StdEnv/2023 gcc/12.3 openmpi/4.1.5 octave/7.2.0</pre>
# Now launch Octave's GUI by typing <code>octave --gui</code> in the terminal window.

You should now see Octave's GUI appear in the remote desktop environment. You can use this method to run other GUI applications as well, just make sure to load the appropriate modules before launching the application. Applications may have different ways to launch their GUI, so please refer to the application's documentation for more information. You can see the list of binaries installed for a given application by looking at it's environment variable, e.g. run <code>ls $EBROOTOCTAVE/bin</code> to see the list of Octave binaries.

[[Image:ood-desktop-octave.png|thumb|centre|600px|Figure 10: Octave GUI running in a Trillium Desktop.]]

=Terminal access=

[[Image:ood-terminal.png|thumb|right|600px|Figure 11: Terminal]]

Sometimes you might prefer to use a terminal to interact with Trillium, Open OnDemand provides a web-based terminal that you can use to access the command line interface. To access the terminal, navigate to the '''Clusters''' tab and select '''Trillium Shell Access'''. This will open a new tab in your browser with a terminal window where you can run commands as you would in a regular terminal session.

= Differences compared to the Jupyter Hub=

{| class="wikitable"
!feature !! Jupyter Hub (decommissioned) !! Open OnDemand
|-
| ''authentication'' || password || password + MFA
|-
| ''first installed'' || 2017 || 2025
|-
| ''last update'' || 2021 || 2025
|-
| ''supports''
| Jupyter Notebook, JupyterLab (R, Python, Julia)
| Jupyter Notebook, JupyterLab (R, Python), Rstudio, VSCode, Desktop, SAS4, Stata4, ParaView, Forge DDT/MAP
|-
| ''start and continue later'' || Yes || Yes1
|-
| ''command terminal'' || No || Yes
|-
| ''file management'' || Yes (limited) || Yes
|-
| ''monitor jobs'' || No || Yes
|-
| ''submit jobs'' || No || Yes
|-
| ''core limit'' || 8 cores2 || 20 cores (8 for high memory)3
|-
| ''memory limit'' || 48 GB2 || 85 GB (500 GB for high memory)3
|-
| ''time limits'' || 3 days2 || 3 days3
|-
| ''operating system'' || CentOS 7 || RockyLinux 9
|-
| ''software stack'' || NiaEnv, CCEnv || CCEnv
|-
| ''system issue alerts'' || No || Yes
|-
| ''user quota alerts'' || No || Yes
|-
| ''error logs'' || No || Yes
|-
| ''hardware'' || 1 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM || 62 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 180GB RAM (default) 3 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM (high memory)
|}

1 Within the requested limits.

2 Limits on JupyterHub were not implementated very strictly, so you could temporarily exceed these.

3 Limits need to be requested before starting an application.

4 Only for users with a license for these products.

= Debugging errors =

[[Image:ood-session-id.png|thumb|right|600px|Figure 12: Accessing error logs via the session card]]

If you encounter any errors while using an interactive Open OnDemand job, you can check the logs for more information. To access the logs, navigate to the '''My Interactive Sessions''' tab and find your active session. Click on the <code>output.log</code> link (see Figure. 8) to open a separate tab which displays the output of your job. This file contains the standard output and error messages generated by the job, which can help you identify any issues that may have occurred during the session. When submitting a ticket to SciNet support, please include the <code>output.log</code> file, your '''Session ID''', which is displayed as a long string of characters, e.g. ''' 8feb45fa-bc65-4846-8398-2a73c1bf8e5a''', and any other relevant information to help us assist you more effectively.

File:Ood-oc-gpus.png

2025-12-16T19:17:25Z

Willis2:

Open OnDemand Quickstart

2025-12-16T19:16:13Z

Willis2: /* Job submission */

{|align=right
|-
|[[Image:ood-logo.png|480px]]
|-
|}

= Porting existing virtual environments to Open OnDemand =

'''IMPORTANT: Because of the change of operating system and software stack, your exisiting virtual environment kernels for Python may not work right away in the OnDemand site. You should be able to activate your python environments in a Trillium terminal (see [[Open_OnDemand_Quickstart#Terminal access|Terminal access]]), with all required Trillium modules loaded, and then issue the command <code>venv2jup</code> to get them working correctly.'''

=Introduction=

This guide will walk you through the basic steps to get started with the SciNet Open OnDemand portal.
Open OnDemand (OOD) is a web-based platform that provides access to a wide range of scientific applications and computing resources, such as Jupyter Lab, R Studio, and VS Code. It allows you to interact with Trillium through a web browser instead of via a terminal, without the need to install any software on your local machine. You will be able to perform file management, submit/monitor jobs and run applications interactively. More information on this project can be found at [https://openondemand.org https://openondemand.org].

=Logging into the Open OnDemand portal=

[[Image:ood-dashboard.png|thumb|right|600px|Figure 1: Dashboard.]]

To access the Open OnDemand portal, open a web browser and navigate to the following page: https://ondemand.scinet.utoronto.ca. You will be prompted to enter your Alliance username and password, followed by a second factor authentication via Duo or Yubikey. Once you have logged in, you will be taken to the Open OnDemand dashboard. From here you can access the various tools and applications available on the platform.

=File management=

[[Image:ood-file-browser.png|thumb|right|600px|Figure 2: File browser.]]

The Open OnDemand platform provides a file browser that allows you to manage your files and directories on the filesystem. To access the file browser, click on the '''Files''' tab and select which directory you want to manage from the drop-down (<code>HOME</code>, <code>SCRATCH</code> or <code>PROJECT</code>). You will be taken to the file browser interface, where you can:

* Navigate through your directories
* Upload/download files
* Create new files/directories
* Delete files/directories
* Edit existing files

==Uploading files==

The current file size upload limit is 10GB, if you need to upload a file larger than this or are facing upload issues due to a bad internet connection for example please try using [https://docs.scinet.utoronto.ca/index.php/Globus Globus]. There is a Globus button in the file browser at the top right, [[File:Globus_button.png | 300px]], which will take you to the Globus web interface where you can login with your Alliance username and password. The path navigated to in the Open OnDemand file browser will be the same path opened in Globus.

=Job submission=

Open OnDemand also provides a job submission interface that allows you to submit batch jobs to Trillium.

The [https://github.com/RIKEN-RCCS/OpenComposer Open Composer] app provides a suite of Slurm job template scripts that can be submitted directly to the Trillium scheduler. It also provides an interface to monitor your submitted jobs, via the '''History''' tab. You can access Open Composer by navigating to the '''Jobs''' drop-down menu and selecting '''Open Composer''' or by clicking on one of the Slurm job templates e.g. '''MPI Slurm Job''', '''OpenMP Slurm Job''' and '''Hybrid MPI/OpenMP Slurm Job'''.

[[Image:ood-oc-shortcuts.png|thumb|right|600px|Figure 3: Open Composer shortcuts.]]

Once you have selected a job template, you will be taken to the job submission page. This is split between the job parameters on the left and the job script itself on the right. The job parameters let you control how many resources your job will use, such as the number of nodes, number of tasks per node, wall clock time and output file name. The job script section displays the script that will be submitted to the scheduler. Any changes made to the job parameters will be reflected in the job script automatically. You may also edit the job script directly if you wish.

The extra fields at the top of the page allow you to change how your job is submitted:

* '''Script Location''': specifies the directory where the job script will be saved and where your job will be run from.
* '''Script Name''': specifies the name of the job script file.
* '''Job Name''': specifies the name of the job that will appear in the job queue.
* '''Cluster''': allows you to change which cluster to submit your job to, e.g. Trillium (default) or Trillium-GPU. Selecting Trillium-GPU will provide an additional job parameter to request GPU resources [[File:ood-oc-gpus.png | 400px]].

Once you are happy with your job script, click on the '''Submit''' button to submit the job to the scheduler and save your script to the '''Script Location'''. If your job was submitted successfully, you will see a confirmation message at the top of the page with your job ID: [[File:ood-oc-job-submit.png | 400px]].

[[Image:ood-oc-job.png|thumb|center|600px|Figure 4: Open Composer job script editor.]]

Note: The template scripts provided in Open Composer are basic examples to get you started. You will need to modify the job script further to suit your specific needs, such as loading your required modules and specifying input/output files.

==Monitoring jobs in Open Composer==

To monitor your submitted jobs in Open Composer, navigate to the '''History''' tab. This will display a list of all your submitted jobs, along with their status: Queued, Running, Completed, Failed. You can filter the jobs by using the '''Filter''' text box at the top right or by using the checkboxes below. Clicking on different column fields will give different information about the job:

* '''Job ID''': displays detailed Slurm information about the job
* '''Application''': opens the job script editor of the template you used
* '''Script Location''': opens an OOD file browser window at the location of the job script. Clicking on the the small terminal icon will open a terminal in the job script location.
* '''Script Name''': displays the job script that was submitted to the scheduler

To resubmit or modify a previously run job click on the job script under the '''Script Name''' column and click '''Load Parameters'''. This will take you back to the job submission page where further modifications can be made to the job.

[[Image:ood-oc-history.png|thumb|center|600px|Figure 5: Open Composer job monitoring.]]

==Supported applications==

Open Composer currently supports the following applications:

* MPI Slurm Job
* OpenMP Slurm Job
* Hybrid MPI/OpenMP Slurm Job
* Python Slurm Job

=Job monitoring=

To get an overview of all your jobs in the queue you can use the job monitoring interface. Navigate to the '''Jobs''' tab and select '''Active Jobs'''. You can filter the jobs by using the '''Filter''' text box at the top right. Columns can also be sorted by clicking on the column headers, for example you can sort by job status (running, completed, failed, etc.). Clicking on <code>></code> to the left of a job will show you more details about the job, such as the start/end time, node list and account charged etc. You might also want to show all jobs in the queue, you can do this by clicking on the drop-down menu at the top right and selecting '''All Jobs'''. A more detailed view of your jobs can still be found using the [https://my.scinet.utoronto.ca myscinet portal].

[[Image:ood-active-jobs.png|thumb|center|600px|Figure 6: Active Jobs.]]

=Interactive applications=

Open OnDemand also features interactive applications that can be run directly from your web browser. To access the applications, navigate to the '''Interactive Apps''' tab and select the application you want to run from the drop-down. This will then bring you to the job submission page where you can choose job parameters such as:

* Length of job in hours
* Number of cores
* Amount of memory to allocate (GB)
* Notify me by email when the job starts

When you have chosen your job parameters click on the '''Launch''' button to submit your job to the queue. You will be taken to the '''My Interactive Sessions''' page where you can see the status of your job, i.e. queued, running or completed. Once the job has been assigned a node and is running, you can click on the '''Connect to ...''' button to launch the application. The application will open in a new tab in your browser, and you can interact with it as if it was running locally.

If you would like terminal access to the node where the application is running, to monitor the performance for example you can click on the button beside '''Host''' starting with <code>>_</code>. This will open a terminal window in your browser where you can run commands on the node directly.

If for whatever reason you would like to kill the job, you can do so by clicking on the red '''Delete''' button in the job panel in the '''My Interactive Sessions''' page.

<div style="margin: 0 auto; display: table;">
{| class="wikitable"
|-
| <div style="text-align: center;">
[[Image:jupyter-submit.png|600px]]
 Figure 7: Interactive app submission form.
</div>
| <div style="text-align: center;">
[[Image:ood_session_tab.png|600px]]
 Figure 8: Interactive sessions page.
[[Image:jupyter-session.png|600px]]
 Figure 9: Interactive app session.
</div>
|}
</div>

==Installed applications==

We currently support the following applications:

* [https://jupyter.org Jupyter Lab/Notebook]
* [https://posit.co/products/open-source/rstudio/?sid=1 Rstudio]
* [https://code.visualstudio.com VSCode]
* Trillium Desktop
* [https://www.paraview.org ParaView]
* [https://www.linaroforge.com Forge DDT/MAP]
* [https://www.sas.com/en_ca/home.html SAS]4
* [https://www.stata.com Stata]4
* [https://github.com/RIKEN-RCCS/OpenComposer Open Composer]

If you would like an application installed please email us at: [mailto:support@scinet.utoronto.ca support@scinet.utoronto.ca].

=Running an application GUI=

If you would like to run software that has a graphical user interface (GUI) and is not yet installed as an interactive application, such as Octave or Blender, you can do so using the '''Trillium Desktop''' application. This app provides a remote desktop environment that you can access through your web browser. In the following example we will run Octave's GUI:

# Navigate to the '''Interactive Apps''' tab and select '''Trillium Desktop''' from the drop-down.
# You will be taken to the job submission page. Choose how many cores and amount of memory you would like to allocate for your session in addition to your job length in hours. Then click on the '''Launch''' button to submit your job to the queue.
# This will take you to the '''My Interactive Sessions''' page. Once your job is running, you have the option to improve the '''Image Quality''' and '''Image Compression''' of the desktop session. Depending on the speed of your internet connection you may want to set these lower to improve performance and responsiveness of the desktop. Click on the '''Connect to Trillium Desktop''' button to launch the remote desktop environment in a new tab.
# Once the desktop environment has loaded, open a terminal window using the desktop shortcut and load the required modules for Octave:
#:<pre> $ module load StdEnv/2023 gcc/12.3 openmpi/4.1.5 octave/7.2.0</pre>
# Now launch Octave's GUI by typing <code>octave --gui</code> in the terminal window.

You should now see Octave's GUI appear in the remote desktop environment. You can use this method to run other GUI applications as well, just make sure to load the appropriate modules before launching the application. Applications may have different ways to launch their GUI, so please refer to the application's documentation for more information. You can see the list of binaries installed for a given application by looking at it's environment variable, e.g. run <code>ls $EBROOTOCTAVE/bin</code> to see the list of Octave binaries.

[[Image:ood-desktop-octave.png|thumb|centre|600px|Figure 10: Octave GUI running in a Trillium Desktop.]]

=Terminal access=

[[Image:ood-terminal.png|thumb|right|600px|Figure 11: Terminal]]

Sometimes you might prefer to use a terminal to interact with Trillium, Open OnDemand provides a web-based terminal that you can use to access the command line interface. To access the terminal, navigate to the '''Clusters''' tab and select '''Trillium Shell Access'''. This will open a new tab in your browser with a terminal window where you can run commands as you would in a regular terminal session.

= Differences compared to the Jupyter Hub=

{| class="wikitable"
!feature !! Jupyter Hub (decommissioned) !! Open OnDemand
|-
| ''authentication'' || password || password + MFA
|-
| ''first installed'' || 2017 || 2025
|-
| ''last update'' || 2021 || 2025
|-
| ''supports''
| Jupyter Notebook, JupyterLab (R, Python, Julia)
| Jupyter Notebook, JupyterLab (R, Python), Rstudio, VSCode, Desktop, SAS4, Stata4, ParaView, Forge DDT/MAP
|-
| ''start and continue later'' || Yes || Yes1
|-
| ''command terminal'' || No || Yes
|-
| ''file management'' || Yes (limited) || Yes
|-
| ''monitor jobs'' || No || Yes
|-
| ''submit jobs'' || No || Yes
|-
| ''core limit'' || 8 cores2 || 20 cores (8 for high memory)3
|-
| ''memory limit'' || 48 GB2 || 85 GB (500 GB for high memory)3
|-
| ''time limits'' || 3 days2 || 3 days3
|-
| ''operating system'' || CentOS 7 || RockyLinux 9
|-
| ''software stack'' || NiaEnv, CCEnv || CCEnv
|-
| ''system issue alerts'' || No || Yes
|-
| ''user quota alerts'' || No || Yes
|-
| ''error logs'' || No || Yes
|-
| ''hardware'' || 1 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM || 62 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 180GB RAM (default) 3 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM (high memory)
|}

1 Within the requested limits.

2 Limits on JupyterHub were not implementated very strictly, so you could temporarily exceed these.

3 Limits need to be requested before starting an application.

4 Only for users with a license for these products.

= Debugging errors =

[[Image:ood-session-id.png|thumb|right|600px|Figure 12: Accessing error logs via the session card]]

If you encounter any errors while using an interactive Open OnDemand job, you can check the logs for more information. To access the logs, navigate to the '''My Interactive Sessions''' tab and find your active session. Click on the <code>output.log</code> link (see Figure. 8) to open a separate tab which displays the output of your job. This file contains the standard output and error messages generated by the job, which can help you identify any issues that may have occurred during the session. When submitting a ticket to SciNet support, please include the <code>output.log</code> file, your '''Session ID''', which is displayed as a long string of characters, e.g. ''' 8feb45fa-bc65-4846-8398-2a73c1bf8e5a''', and any other relevant information to help us assist you more effectively.

Open OnDemand Quickstart

2025-12-16T19:14:38Z

Willis2:

{|align=right
|-
|[[Image:ood-logo.png|480px]]
|-
|}

= Porting existing virtual environments to Open OnDemand =

'''IMPORTANT: Because of the change of operating system and software stack, your exisiting virtual environment kernels for Python may not work right away in the OnDemand site. You should be able to activate your python environments in a Trillium terminal (see [[Open_OnDemand_Quickstart#Terminal access|Terminal access]]), with all required Trillium modules loaded, and then issue the command <code>venv2jup</code> to get them working correctly.'''

=Introduction=

This guide will walk you through the basic steps to get started with the SciNet Open OnDemand portal.
Open OnDemand (OOD) is a web-based platform that provides access to a wide range of scientific applications and computing resources, such as Jupyter Lab, R Studio, and VS Code. It allows you to interact with Trillium through a web browser instead of via a terminal, without the need to install any software on your local machine. You will be able to perform file management, submit/monitor jobs and run applications interactively. More information on this project can be found at [https://openondemand.org https://openondemand.org].

=Logging into the Open OnDemand portal=

[[Image:ood-dashboard.png|thumb|right|600px|Figure 1: Dashboard.]]

To access the Open OnDemand portal, open a web browser and navigate to the following page: https://ondemand.scinet.utoronto.ca. You will be prompted to enter your Alliance username and password, followed by a second factor authentication via Duo or Yubikey. Once you have logged in, you will be taken to the Open OnDemand dashboard. From here you can access the various tools and applications available on the platform.

=File management=

[[Image:ood-file-browser.png|thumb|right|600px|Figure 2: File browser.]]

The Open OnDemand platform provides a file browser that allows you to manage your files and directories on the filesystem. To access the file browser, click on the '''Files''' tab and select which directory you want to manage from the drop-down (<code>HOME</code>, <code>SCRATCH</code> or <code>PROJECT</code>). You will be taken to the file browser interface, where you can:

* Navigate through your directories
* Upload/download files
* Create new files/directories
* Delete files/directories
* Edit existing files

==Uploading files==

The current file size upload limit is 10GB, if you need to upload a file larger than this or are facing upload issues due to a bad internet connection for example please try using [https://docs.scinet.utoronto.ca/index.php/Globus Globus]. There is a Globus button in the file browser at the top right, [[File:Globus_button.png | 300px]], which will take you to the Globus web interface where you can login with your Alliance username and password. The path navigated to in the Open OnDemand file browser will be the same path opened in Globus.

=Job submission=

Open OnDemand also provides a job submission interface that allows you to submit batch jobs to Trillium.

The [https://github.com/RIKEN-RCCS/OpenComposer Open Composer] app provides a suite of Slurm job template scripts that can be submitted directly to the Trillium scheduler. It also provides an interface to monitor your submitted jobs, via the '''History''' tab. You can access Open Composer by navigating to the '''Jobs''' drop-down menu and selecting '''Open Composer''' or by clicking on one of the Slurm job templates e.g. '''MPI Slurm Job''', '''OpenMP Slurm Job''' and '''Hybrid MPI/OpenMP Slurm Job'''.

[[Image:ood-oc-shortcuts.png|thumb|right|600px|Figure 3: Open Composer shortcuts.]]

Once you have selected a job template, you will be taken to the job submission page. This is split between the job parameters on the left and the job script itself on the right. The job parameters let you control how many resources your job will use, such as the number of nodes, number of tasks per node, wall clock time and output file name. The job script section displays the script that will be submitted to the scheduler. Any changes made to the job parameters will be reflected in the job script automatically. You may also edit the job script directly if you wish.

The extra fields at the top of the page allow you to change how your job is submitted:

* '''Script Location''': specifies the directory where the job script will be saved and where your job will be run from.
* '''Script Name''': specifies the name of the job script file.
* '''Job Name''': specifies the name of the job that will appear in the job queue.
* '''Cluster''': allows you to change which cluster to submit your job to, e.g. Trillium (default) or Trillium-GPU. Selecting Trillium-GPU will provide an additional job parameter to request GPU resources [File:ood-oc-gpus.png | 400px]].

Once you are happy with your job script, click on the '''Submit''' button to submit the job to the scheduler and save your script to the '''Script Location'''. If your job was submitted successfully, you will see a confirmation message at the top of the page with your job ID: [[File:ood-oc-job-submit.png | 400px]].

[[Image:ood-oc-job.png|thumb|center|600px|Figure 4: Open Composer job script editor.]]

Note: The template scripts provided in Open Composer are basic examples to get you started. You will need to modify the job script further to suit your specific needs, such as loading your required modules and specifying input/output files.

==Monitoring jobs in Open Composer==

To monitor your submitted jobs in Open Composer, navigate to the '''History''' tab. This will display a list of all your submitted jobs, along with their status: Queued, Running, Completed, Failed. You can filter the jobs by using the '''Filter''' text box at the top right or by using the checkboxes below. Clicking on different column fields will give different information about the job:

* '''Job ID''': displays detailed Slurm information about the job
* '''Application''': opens the job script editor of the template you used
* '''Script Location''': opens an OOD file browser window at the location of the job script. Clicking on the the small terminal icon will open a terminal in the job script location.
* '''Script Name''': displays the job script that was submitted to the scheduler

To resubmit or modify a previously run job click on the job script under the '''Script Name''' column and click '''Load Parameters'''. This will take you back to the job submission page where further modifications can be made to the job.

[[Image:ood-oc-history.png|thumb|center|600px|Figure 5: Open Composer job monitoring.]]

==Supported applications==

Open Composer currently supports the following applications:

* MPI Slurm Job
* OpenMP Slurm Job
* Hybrid MPI/OpenMP Slurm Job
* Python Slurm Job

=Job monitoring=

To get an overview of all your jobs in the queue you can use the job monitoring interface. Navigate to the '''Jobs''' tab and select '''Active Jobs'''. You can filter the jobs by using the '''Filter''' text box at the top right. Columns can also be sorted by clicking on the column headers, for example you can sort by job status (running, completed, failed, etc.). Clicking on <code>></code> to the left of a job will show you more details about the job, such as the start/end time, node list and account charged etc. You might also want to show all jobs in the queue, you can do this by clicking on the drop-down menu at the top right and selecting '''All Jobs'''. A more detailed view of your jobs can still be found using the [https://my.scinet.utoronto.ca myscinet portal].

[[Image:ood-active-jobs.png|thumb|center|600px|Figure 6: Active Jobs.]]

=Interactive applications=

Open OnDemand also features interactive applications that can be run directly from your web browser. To access the applications, navigate to the '''Interactive Apps''' tab and select the application you want to run from the drop-down. This will then bring you to the job submission page where you can choose job parameters such as:

* Length of job in hours
* Number of cores
* Amount of memory to allocate (GB)
* Notify me by email when the job starts

When you have chosen your job parameters click on the '''Launch''' button to submit your job to the queue. You will be taken to the '''My Interactive Sessions''' page where you can see the status of your job, i.e. queued, running or completed. Once the job has been assigned a node and is running, you can click on the '''Connect to ...''' button to launch the application. The application will open in a new tab in your browser, and you can interact with it as if it was running locally.

If you would like terminal access to the node where the application is running, to monitor the performance for example you can click on the button beside '''Host''' starting with <code>>_</code>. This will open a terminal window in your browser where you can run commands on the node directly.

If for whatever reason you would like to kill the job, you can do so by clicking on the red '''Delete''' button in the job panel in the '''My Interactive Sessions''' page.

<div style="margin: 0 auto; display: table;">
{| class="wikitable"
|-
| <div style="text-align: center;">
[[Image:jupyter-submit.png|600px]]
 Figure 7: Interactive app submission form.
</div>
| <div style="text-align: center;">
[[Image:ood_session_tab.png|600px]]
 Figure 8: Interactive sessions page.
[[Image:jupyter-session.png|600px]]
 Figure 9: Interactive app session.
</div>
|}
</div>

==Installed applications==

We currently support the following applications:

* [https://jupyter.org Jupyter Lab/Notebook]
* [https://posit.co/products/open-source/rstudio/?sid=1 Rstudio]
* [https://code.visualstudio.com VSCode]
* Trillium Desktop
* [https://www.paraview.org ParaView]
* [https://www.linaroforge.com Forge DDT/MAP]
* [https://www.sas.com/en_ca/home.html SAS]4
* [https://www.stata.com Stata]4
* [https://github.com/RIKEN-RCCS/OpenComposer Open Composer]

If you would like an application installed please email us at: [mailto:support@scinet.utoronto.ca support@scinet.utoronto.ca].

=Running an application GUI=

If you would like to run software that has a graphical user interface (GUI) and is not yet installed as an interactive application, such as Octave or Blender, you can do so using the '''Trillium Desktop''' application. This app provides a remote desktop environment that you can access through your web browser. In the following example we will run Octave's GUI:

# Navigate to the '''Interactive Apps''' tab and select '''Trillium Desktop''' from the drop-down.
# You will be taken to the job submission page. Choose how many cores and amount of memory you would like to allocate for your session in addition to your job length in hours. Then click on the '''Launch''' button to submit your job to the queue.
# This will take you to the '''My Interactive Sessions''' page. Once your job is running, you have the option to improve the '''Image Quality''' and '''Image Compression''' of the desktop session. Depending on the speed of your internet connection you may want to set these lower to improve performance and responsiveness of the desktop. Click on the '''Connect to Trillium Desktop''' button to launch the remote desktop environment in a new tab.
# Once the desktop environment has loaded, open a terminal window using the desktop shortcut and load the required modules for Octave:
#:<pre> $ module load StdEnv/2023 gcc/12.3 openmpi/4.1.5 octave/7.2.0</pre>
# Now launch Octave's GUI by typing <code>octave --gui</code> in the terminal window.

You should now see Octave's GUI appear in the remote desktop environment. You can use this method to run other GUI applications as well, just make sure to load the appropriate modules before launching the application. Applications may have different ways to launch their GUI, so please refer to the application's documentation for more information. You can see the list of binaries installed for a given application by looking at it's environment variable, e.g. run <code>ls $EBROOTOCTAVE/bin</code> to see the list of Octave binaries.

[[Image:ood-desktop-octave.png|thumb|centre|600px|Figure 10: Octave GUI running in a Trillium Desktop.]]

=Terminal access=

[[Image:ood-terminal.png|thumb|right|600px|Figure 11: Terminal]]

Sometimes you might prefer to use a terminal to interact with Trillium, Open OnDemand provides a web-based terminal that you can use to access the command line interface. To access the terminal, navigate to the '''Clusters''' tab and select '''Trillium Shell Access'''. This will open a new tab in your browser with a terminal window where you can run commands as you would in a regular terminal session.

= Differences compared to the Jupyter Hub=

{| class="wikitable"
!feature !! Jupyter Hub (decommissioned) !! Open OnDemand
|-
| ''authentication'' || password || password + MFA
|-
| ''first installed'' || 2017 || 2025
|-
| ''last update'' || 2021 || 2025
|-
| ''supports''
| Jupyter Notebook, JupyterLab (R, Python, Julia)
| Jupyter Notebook, JupyterLab (R, Python), Rstudio, VSCode, Desktop, SAS4, Stata4, ParaView, Forge DDT/MAP
|-
| ''start and continue later'' || Yes || Yes1
|-
| ''command terminal'' || No || Yes
|-
| ''file management'' || Yes (limited) || Yes
|-
| ''monitor jobs'' || No || Yes
|-
| ''submit jobs'' || No || Yes
|-
| ''core limit'' || 8 cores2 || 20 cores (8 for high memory)3
|-
| ''memory limit'' || 48 GB2 || 85 GB (500 GB for high memory)3
|-
| ''time limits'' || 3 days2 || 3 days3
|-
| ''operating system'' || CentOS 7 || RockyLinux 9
|-
| ''software stack'' || NiaEnv, CCEnv || CCEnv
|-
| ''system issue alerts'' || No || Yes
|-
| ''user quota alerts'' || No || Yes
|-
| ''error logs'' || No || Yes
|-
| ''hardware'' || 1 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM || 62 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 180GB RAM (default) 3 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM (high memory)
|}

1 Within the requested limits.

2 Limits on JupyterHub were not implementated very strictly, so you could temporarily exceed these.

3 Limits need to be requested before starting an application.

4 Only for users with a license for these products.

= Debugging errors =

[[Image:ood-session-id.png|thumb|right|600px|Figure 12: Accessing error logs via the session card]]

If you encounter any errors while using an interactive Open OnDemand job, you can check the logs for more information. To access the logs, navigate to the '''My Interactive Sessions''' tab and find your active session. Click on the <code>output.log</code> link (see Figure. 8) to open a separate tab which displays the output of your job. This file contains the standard output and error messages generated by the job, which can help you identify any issues that may have occurred during the session. When submitting a ticket to SciNet support, please include the <code>output.log</code> file, your '''Session ID''', which is displayed as a long string of characters, e.g. ''' 8feb45fa-bc65-4846-8398-2a73c1bf8e5a''', and any other relevant information to help us assist you more effectively.

Open OnDemand Quickstart

2025-12-16T18:32:02Z

Willis2:

{|align=right
|-
|[[Image:ood-logo.png|480px]]
|-
|}

= Porting existing virtual environments to Open OnDemand =

'''IMPORTANT: Because of the change of operating system and software stack, your exisiting virtual environment kernels for Python may not work right away in the OnDemand site. You should be able to activate your python environments in a Trillium terminal (see [[Open_OnDemand_Quickstart#Terminal access|Terminal access]]), with all required Trillium modules loaded, and then issue the command <code>venv2jup</code> to get them working correctly.'''

=Introduction=

This guide will walk you through the basic steps to get started with the SciNet Open OnDemand portal.
Open OnDemand (OOD) is a web-based platform that provides access to a wide range of scientific applications and computing resources, such as Jupyter Lab, R Studio, and VS Code. It allows you to interact with Trillium through a web browser instead of via a terminal, without the need to install any software on your local machine. You will be able to perform file management, submit/monitor jobs and run applications interactively. More information on this project can be found at [https://openondemand.org https://openondemand.org].

=Logging into the Open OnDemand portal=

[[Image:ood-dashboard.png|thumb|right|600px|Figure 1: Dashboard.]]

To access the Open OnDemand portal, open a web browser and navigate to the following page: https://ondemand.scinet.utoronto.ca. You will be prompted to enter your Alliance username and password, followed by a second factor authentication via Duo or Yubikey. Once you have logged in, you will be taken to the Open OnDemand dashboard. From here you can access the various tools and applications available on the platform.

=File management=

[[Image:ood-file-browser.png|thumb|right|600px|Figure 2: File browser.]]

The Open OnDemand platform provides a file browser that allows you to manage your files and directories on the filesystem. To access the file browser, click on the '''Files''' tab and select which directory you want to manage from the drop-down (<code>HOME</code>, <code>SCRATCH</code> or <code>PROJECT</code>). You will be taken to the file browser interface, where you can:

* Navigate through your directories
* Upload/download files
* Create new files/directories
* Delete files/directories
* Edit existing files

==Uploading files==

The current file size upload limit is 10GB, if you need to upload a file larger than this or are facing upload issues due to a bad internet connection for example please try using [https://docs.scinet.utoronto.ca/index.php/Globus Globus]. There is a Globus button in the file browser at the top right, [[File:Globus_button.png | 300px]], which will take you to the Globus web interface where you can login with your Alliance username and password. The path navigated to in the Open OnDemand file browser will be the same path opened in Globus.

=Job submission=

Open OnDemand also provides a job submission interface that allows you to submit batch jobs to Trillium.

The [https://github.com/RIKEN-RCCS/OpenComposer Open Composer] app provides a suite of Slurm job template scripts that can be submitted directly to the Trillium scheduler. It also provides an interface to monitor your submitted jobs, via the '''History''' tab. You can access Open Composer by navigating to the '''Jobs''' drop-down menu and selecting '''Open Composer''' or by clicking on one of the Slurm job templates e.g. '''MPI Slurm Job''', '''OpenMP Slurm Job''' and '''Hybrid MPI/OpenMP Slurm Job'''.

[[Image:ood-oc-shortcuts.png|thumb|right|600px|Figure 3: Open Composer shortcuts.]]

Once you have selected a job template, you will be taken to the job submission page. This is split between the job parameters on the left and the job script itself on the right. The job parameters let you control how many resources your job will use, such as the number of nodes, number of tasks per node, wall clock time and output file name. The job script section displays the script that will be submitted to the scheduler. Any changes made to the job parameters will be reflected in the job script automatically. You may also edit the job script directly if you wish.

The extra fields at the top of the page allow you to change how your job is submitted:

* '''Script Location''': specifies the directory where the job script will be saved and where your job will be run from.
* '''Script Name''': specifies the name of the job script file.
* '''Job Name''': specifies the name of the job that will appear in the job queue.
* '''Cluster''': allows you to change which cluster to submit your job to, e.g. Trillium (default) or Trillium-GPU. Selecting Trillium-GPU will provide an additional job parameter to request GPU resources [File:ood-oc-gpus.png | 400px]].

Once you are happy with your job script, click on the '''Submit''' button to submit the job to the scheduler and save your script to the '''Script Location'''. If your job was submitted successfully, you will see a confirmation message at the top of the page with your job ID: [[File:ood-oc-job-submit.png | 400px]].

[[Image:ood-oc-job.png|thumb|center|600px|Figure 4: Open Composer job script editor.]]

Note: The template scripts provided in Open Composer are basic examples to get you started. You will need to modify the job script further to suit your specific needs, such as loading your required modules and specifying input/output files.

==Monitoring jobs in Open Composer==

To monitor your submitted jobs in Open Composer, navigate to the '''History''' tab. This will display a list of all your submitted jobs, along with their status: Queued, Running, Completed, Failed. You can filter the jobs by using the '''Filter''' text box at the top right or by using the checkboxes below. Clicking on different column fields will give different information about the job:

* '''Job ID''': displays detailed Slurm information about the job
* '''Application''': opens the job script editor of the template you used
* '''Script Location''': opens an OOD file browser window at the location of the job script. Clicking on the the small terminal icon will open a terminal in the job script location.
* '''Script Name''': displays the job script that was submitted to the scheduler

To resubmit or modify a previously run job click on the job script under the '''Script Name''' column and click '''Load Parameters'''. This will take you back to the job submission page where further modifications can be made to the job.

[[Image:ood-oc-history.png|thumb|center|600px|Figure 5: Open Composer job monitoring.]]

==Supported applications==

Open Composer currently supports the following applications:

* MPI Slurm Job
* OpenMP Slurm Job
* Hybrid MPI/OpenMP Slurm Job
* Python Slurm Job

=Job monitoring=

To get an overview of all your jobs in the queue you can use the job monitoring interface. Navigate to the '''Jobs''' tab and select '''Active Jobs'''. You can filter the jobs by using the '''Filter''' text box at the top right. Columns can also be sorted by clicking on the column headers, for example you can sort by job status (running, completed, failed, etc.). Clicking on <code>></code> to the left of a job will show you more details about the job, such as the start/end time, node list and account charged etc. You might also want to show all jobs in the queue, you can do this by clicking on the drop-down menu at the top right and selecting '''All Jobs'''. A more detailed view of your jobs can still be found using the [https://my.scinet.utoronto.ca myscinet portal].

[[Image:ood-active-jobs.png|thumb|center|600px|Figure 6: Active Jobs.]]

=Interactive applications=

Open OnDemand also features interactive applications that can be run directly from your web browser. To access the applications, navigate to the '''Interactive Apps''' tab and select the application you want to run from the drop-down. This will then bring you to the job submission page where you can choose job parameters such as:

* Length of job in hours
* Number of cores
* Amount of memory to allocate (GB)
* Notify me by email when the job starts

When you have chosen your job parameters click on the '''Launch''' button to submit your job to the queue. You will be taken to the '''My Interactive Sessions''' page where you can see the status of your job, i.e. queued, running or completed. Once the job has been assigned a node and is running, you can click on the '''Connect to ...''' button to launch the application. The application will open in a new tab in your browser, and you can interact with it as if it was running locally.

If you would like terminal access to the node where the application is running, to monitor the performance for example you can click on the button beside '''Host''' starting with <code>>_</code>. This will open a terminal window in your browser where you can run commands on the node directly.

If for whatever reason you would like to kill the job, you can do so by clicking on the red '''Delete''' button in the job panel in the '''My Interactive Sessions''' page.

<div style="margin: 0 auto; display: table;">
{| class="wikitable"
|-
| <div style="text-align: center;">
[[Image:jupyter-submit.png|600px]]
 Figure 7: Interactive app submission form.
</div>
| <div style="text-align: center;">
[[Image:ood_session_tab.png|600px]]
 Figure 8: Interactive sessions page.
[[Image:jupyter-session.png|600px]]
 Figure 9: Interactive app session.
</div>
|}
</div>

==Installed applications==

We currently support the following applications:

* [https://jupyter.org Jupyter Lab/Notebook]
* [https://posit.co/products/open-source/rstudio/?sid=1 Rstudio]
* [https://code.visualstudio.com VSCode]
* Trillium Desktop
* [https://www.paraview.org ParaView]
* [https://www.linaroforge.com Forge DDT/MAP]
* [https://www.sas.com/en_ca/home.html SAS]4
* [https://www.stata.com Stata]4
* [https://github.com/RIKEN-RCCS/OpenComposer Open Composer]

If you would like an application installed please email us at: [mailto:support@scinet.utoronto.ca support@scinet.utoronto.ca].

=Running an application GUI=

If you would like to run software that has a graphical user interface (GUI) and is not yet installed as an interactive application, such as Octave or Blender, you can do so using the '''Trillium Desktop''' application. This app provides a remote desktop environment that you can access through your web browser. In the following example we will run Octave's GUI:

# Navigate to the '''Interactive Apps''' tab and select '''Trillium Desktop''' from the drop-down.
# You will be taken to the job submission page. Choose how many cores and amount of memory you would like to allocate for your session in addition to your job length in hours. Then click on the '''Launch''' button to submit your job to the queue.
# This will take you to the '''My Interactive Sessions''' page. Once your job is running, you have the option to improve the '''Image Quality''' and '''Image Compression''' of the desktop session. Depending on the speed of your internet connection you may want to set these lower to improve performance and responsiveness of the desktop. Click on the '''Connect to Trillium Desktop''' button to launch the remote desktop environment in a new tab.
# Once the desktop environment has loaded, open a terminal window using the desktop shortcut and load the required modules for Octave:
#:<pre> $ module load StdEnv/2023 gcc/12.3 openmpi/4.1.5 octave/7.2.0</pre>
# Now launch Octave's GUI by typing <code>octave --gui</code> in the terminal window.

You should now see Octave's GUI appear in the remote desktop environment. You can use this method to run other GUI applications as well, just make sure to load the appropriate modules before launching the application. Applications may have different ways to launch their GUI, so please refer to the application's documentation for more information. You can see the list of binaries installed for a given application by looking at it's environment variable, e.g. run <code>ls $EBROOTOCTAVE/bin</code> to see the list of Octave binaries.

[[Image:ood-desktop-octave.png|thumb|centre|600px|Figure 10: Octave GUI running in a Trillium Desktop.]]

=Terminal access=

[[Image:ood-terminal.png|thumb|right|600px|Figure 10: Terminal]]

Sometimes you might prefer to use a terminal to interact with Trillium, Open OnDemand provides a web-based terminal that you can use to access the command line interface. To access the terminal, navigate to the '''Clusters''' tab and select '''Trillium Shell Access'''. This will open a new tab in your browser with a terminal window where you can run commands as you would in a regular terminal session.

= Differences compared to the Jupyter Hub=

{| class="wikitable"
!feature !! Jupyter Hub (decommissioned) !! Open OnDemand
|-
| ''authentication'' || password || password + MFA
|-
| ''first installed'' || 2017 || 2025
|-
| ''last update'' || 2021 || 2025
|-
| ''supports''
| Jupyter Notebook, JupyterLab (R, Python, Julia)
| Jupyter Notebook, JupyterLab (R, Python), Rstudio, VSCode, Desktop, SAS4, Stata4, ParaView, Forge DDT/MAP
|-
| ''start and continue later'' || Yes || Yes1
|-
| ''command terminal'' || No || Yes
|-
| ''file management'' || Yes (limited) || Yes
|-
| ''monitor jobs'' || No || Yes
|-
| ''submit jobs'' || No || Yes
|-
| ''core limit'' || 8 cores2 || 20 cores (8 for high memory)3
|-
| ''memory limit'' || 48 GB2 || 85 GB (500 GB for high memory)3
|-
| ''time limits'' || 3 days2 || 3 days3
|-
| ''operating system'' || CentOS 7 || RockyLinux 9
|-
| ''software stack'' || NiaEnv, CCEnv || CCEnv
|-
| ''system issue alerts'' || No || Yes
|-
| ''user quota alerts'' || No || Yes
|-
| ''error logs'' || No || Yes
|-
| ''hardware'' || 1 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM || 62 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 180GB RAM (default) 3 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM (high memory)
|}

1 Within the requested limits.

2 Limits on JupyterHub were not implementated very strictly, so you could temporarily exceed these.

3 Limits need to be requested before starting an application.

4 Only for users with a license for these products.

= Debugging errors =

[[Image:ood-session-id.png|thumb|right|600px|Figure 11: Accessing error logs via the session card]]

If you encounter any errors while using an interactive Open OnDemand job, you can check the logs for more information. To access the logs, navigate to the '''My Interactive Sessions''' tab and find your active session. Click on the <code>output.log</code> link (see Figure. 8) to open a separate tab which displays the output of your job. This file contains the standard output and error messages generated by the job, which can help you identify any issues that may have occurred during the session. When submitting a ticket to SciNet support, please include the <code>output.log</code> file, your '''Session ID''', which is displayed as a long string of characters, e.g. ''' 8feb45fa-bc65-4846-8398-2a73c1bf8e5a''', and any other relevant information to help us assist you more effectively.

2025-12-08T14:32:07Z

Willis2: /* Supported Applications */

{|align=right
|-
|[[Image:ood-logo.png|480px]]
|-
|}

= Porting existing virtual environments to Open OnDemand =

'''IMPORTANT: Because of the change of operating system and software stack, your exisiting virtual environment kernels for Python may not work right away in the OnDemand site. You should be able to activate your python environments in a Trillium terminal (see [[Open_OnDemand_Quickstart#Terminal access|Terminal access]]), with all required Trillium modules loaded, and then issue the command <code>venv2jup</code> to get them working correctly.'''

=Introduction=

This guide will walk you through the basic steps to get started with the SciNet Open OnDemand portal.
Open OnDemand (OOD) is a web-based platform that provides access to a wide range of scientific applications and computing resources, such as Jupyter Lab, R Studio, and VS Code. It allows you to interact with Trillium through a web browser instead of via a terminal, without the need to install any software on your local machine. You will be able to perform file management, submit/monitor jobs and run applications interactively. More information on this project can be found at [https://openondemand.org https://openondemand.org].

=Logging into the Open OnDemand portal=

[[Image:ood-dashboard.png|thumb|right|600px|Figure 1: Dashboard.]]

To access the Open OnDemand portal, open a web browser and navigate to the following page: https://ondemand.scinet.utoronto.ca. You will be prompted to enter your Alliance username and password, followed by a second factor authentication via Duo or Yubikey. Once you have logged in, you will be taken to the Open OnDemand dashboard. From here you can access the various tools and applications available on the platform.

=File management=

[[Image:ood-file-browser.png|thumb|right|600px|Figure 2: File browser.]]

The Open OnDemand platform provides a file browser that allows you to manage your files and directories on the filesystem. To access the file browser, click on the '''Files''' tab and select which directory you want to manage from the drop-down (<code>HOME</code>, <code>SCRATCH</code> or <code>PROJECT</code>). You will be taken to the file browser interface, where you can:

* Navigate through your directories
* Upload/download files
* Create new files/directories
* Delete files/directories
* Edit existing files

==Uploading Files==

The current file size upload limit is 10GB, if you need to upload a file larger than this or are facing upload issues due to a bad internet connection for example please try using [https://docs.scinet.utoronto.ca/index.php/Globus Globus]. There is a Globus button in the file browser at the top right, [[File:Globus_button.png | 300px]], which will take you to the Globus web interface where you can login with your Alliance username and password. The path navigated to in the Open OnDemand file browser will be the same path opened in Globus.

=Job submission=

[[Image:ood-job-composer.png|thumb|right|600px|Figure 3: Job Composer.]]

Open OnDemand also provides a job submission interface that allows you to submit batch jobs to Trillium. Navigate to the '''Jobs''' tab and select '''Job Composer''', this will take you to the job submission form. From here click on the '''New Job''' button which will offer you the following options:

* '''From Default Template''' - allows you to create a job from scratch
* '''From Template''' - allows you to select from some example jobs, e.g. MPI and OpenMP
* '''From Specified Path''' - allows you to use an existing job that you already have on the file system
* '''From Selected Job''' - copies the current job for you.

You can specify job parameters such as the job script and account name using the '''Job Options''' button. The remaining parameters such as the number of nodes, number of cores, wall clock time, etc. can be modified by editing the job script directly with the '''Open Editor''' button. Once you have filled in the required fields, click on the '''Submit''' button to submit the job.

The page also shows the status of your job so you can see whether it is queued, running or completed. You can also view the output and error logs of the job once it is finished by clicking on the relevant files under the '''Folder Contents''' section of the '''Job Details''' panel to the right.

=Job monitoring=

To get an overview of all your jobs in the queue you can use the job monitoring interface. Navigate to the '''Jobs''' tab and select '''Active Jobs'''. You can filter the jobs by using the '''Filter''' text box at the top right. Columns can also be sorted by clicking on the column headers, for example you can sort by job status (running, completed, failed, etc.). Clicking on <code>></code> to the left of a job will show you more details about the job, such as the start/end time, node list and account charged etc. You might also want to show all jobs in the queue, you can do this by clicking on the drop-down menu at the top right and selecting '''All Jobs'''. A more detailed view of your jobs can still be found using the [https://my.scinet.utoronto.ca myscinet portal].

[[Image:ood-active-jobs.png|thumb|center|600px|Figure 4: Active Jobs.]]

=Interactive applications=

Open OnDemand also features interactive applications that can be run directly from your web browser. To access the applications, navigate to the '''Interactive Apps''' tab and select the application you want to run from the drop-down. This will then bring you to the job submission page where you can choose job parameters such as:

* Length of job in hours
* Number of cores
* Amount of memory to allocate (GB)
* Notify me by email when the job starts

When you have chosen your job parameters click on the '''Launch''' button to submit your job to the queue. You will be taken to the '''My Interactive Sessions''' page where you can see the status of your job, i.e. queued, running or completed. Once the job has been assigned a node and is running, you can click on the '''Connect to ...''' button to launch the application. The application will open in a new tab in your browser, and you can interact with it as if it was running locally.

If you would like terminal access to the node where the application is running, to monitor the performance for example you can click on the button beside '''Host''' starting with <code>>_</code>. This will open a terminal window in your browser where you can run commands on the node directly.

If for whatever reason you would like to kill the job, you can do so by clicking on the red '''Delete''' button in the job panel in the '''My Interactive Sessions''' page.

<div style="margin: 0 auto; display: table;">
{| class="wikitable"
|-
| <div style="text-align: center;">
[[Image:jupyter-submit.png|600px]]
 Figure 5: Interactive app submission form.
</div>
| <div style="text-align: center;">
[[Image:ood_session_tab.png|600px]]
 Figure 6: Interactive sessions page.
[[Image:jupyter-session.png|600px]]
 Figure 7: Interactive app session.
</div>
|}
</div>

=Open Composer=

The [https://github.com/RIKEN-RCCS/OpenComposer Open Composer] app provides a suite of Slurm job template scripts that can be submitted directly to the Trillium scheduler. It also provides an interface to monitor your submitted jobs, via the '''History''' tab. You can access Open Composer by navigating to the '''Jobs''' drop-down menu and selecting '''Open Composer''' or by clicking on one of the Slurm job templates e.g. '''MPI Slurm Job''', '''OpenMP Slurm Job''' and '''Hybrid MPI/OpenMP Slurm Job'''.

[[Image:ood-oc-shortcuts.png|thumb|right|600px|Figure 8: Open Composer shortcuts.]]

Once you have selected a job template, you will be taken to the job submission page. This is split between the job parameters on the left and the job script itself on the right. The job parameters let you control how many resources your job will use, such as the number of nodes, number of tasks per node, wall clock time and output file name. The job script section displays the script that will be submitted to the scheduler. Any changes made to the job parameters will be reflected in the job script automatically. You may also edit the job script directly if you wish.

The extra fields at the top of the page allow you to change how your job is submitted:

* Script Location: specifies the directory where the job script will be saved and where your job will be run from.
* Script Name: specifies the name of the job script file.
* Job Name: specifies the name of the job that will appear in the job queue.

Once you are happy with your job script, click on the '''Submit''' button to submit the job to the scheduler. If your job was submitted successfully, you will see a confirmation message at the top of the page with your job ID [[File:ood-oc-job-submit.png | 300px]].

[[Image:ood-oc-job.png|thumb|center|600px|Figure 9: Open Composer job script editor.]]

Note: The template scripts provided in Open Composer are basic examples to get you started. You will need to modify the job script further to suit your specific needs, such as loading your required modules and specifying input/output files.

==Monitoring Jobs in Open Composer==

To monitor your submitted jobs in Open Composer, navigate to the '''History''' tab. This will display a list of all your submitted jobs, along with their status: Queued, Running, Completed, Failed. You can filter the jobs by using the '''Filter''' text box at the top right or by using the checkboxes below. Clicking on different column fields will give different information about the job:

* Job ID: displays detailed Slurm information about the job
* Application: opens the job script editor of the template you used
* Script Location: opens an OOD file browser window at the location of the job script. Clicking on the the small terminal icon will open a terminal in the job script location.
* Script Name: displays the job script that was submitted to the scheduler

[[Image:ood-oc-history.png|thumb|center|600px|Figure 10: Open Composer job monitoring.]]

==Supported Applications==

Open Composer currently supports the following applications:

* MPI Slurm Job
* OpenMP Slurm Job
* Hybrid MPI/OpenMP Slurm Job
* Python Slurm Job

==Installed Applications==

We currently support the following applications:

* [https://jupyter.org Jupyter Lab/Notebook]
* [https://posit.co/products/open-source/rstudio/?sid=1 Rstudio]
* [https://code.visualstudio.com VSCode]
* Desktop
* [https://www.paraview.org ParaView]
* [https://www.linaroforge.com Forge DDT/MAP]
* [https://www.sas.com/en_ca/home.html SAS]4
* [https://www.stata.com Stata]4
* [https://github.com/RIKEN-RCCS/OpenComposer Open Composer]

If you would like an application installed please email us at: [mailto:support@scinet.utoronto.ca support@scinet.utoronto.ca].

=Terminal access=

[[Image:ood-terminal.png|thumb|right|600px|Figure 11: Terminal]]

Sometimes you might prefer to use a terminal to interact with Trillium, Open OnDemand provides a web-based terminal that you can use to access the command line interface. To access the terminal, navigate to the '''Clusters''' tab and select '''Trillium Shell Access'''. This will open a new tab in your browser with a terminal window where you can run commands as you would in a regular terminal session.

= Differences compared to the Jupyter Hub=

{| class="wikitable"
!feature !! Jupyter Hub (decommissioned) !! Open OnDemand
|-
| ''authentication'' || password || password + MFA
|-
| ''first installed'' || 2017 || 2025
|-
| ''last update'' || 2021 || 2025
|-
| ''supports''
| Jupyter Notebook, JupyterLab (R, Python, Julia)
| Jupyter Notebook, JupyterLab (R, Python), Rstudio, VSCode, Desktop, SAS4, Stata4, ParaView, Forge DDT/MAP
|-
| ''start and continue later'' || Yes || Yes1
|-
| ''command terminal'' || No || Yes
|-
| ''file management'' || Yes (limited) || Yes
|-
| ''monitor jobs'' || No || Yes
|-
| ''submit jobs'' || No || Yes
|-
| ''core limit'' || 8 cores2 || 20 cores (8 for high memory)3
|-
| ''memory limit'' || 48 GB2 || 85 GB (500 GB for high memory)3
|-
| ''time limits'' || 3 days2 || 3 days3
|-
| ''operating system'' || CentOS 7 || RockyLinux 9
|-
| ''software stack'' || NiaEnv, CCEnv || CCEnv
|-
| ''system issue alerts'' || No || Yes
|-
| ''user quota alerts'' || No || Yes
|-
| ''error logs'' || No || Yes
|-
| ''hardware'' || 1 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM || 62 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 180GB RAM (default) 3 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM (high memory)
|}

1 Within the requested limits.

2 Limits on JupyterHub were not implementated very strictly, so you could temporarily exceed these.

3 Limits need to be requested before starting an application.

4 Only for users with a license for these products.

= Debugging Errors =

[[Image:ood-session-id.png|thumb|right|600px|Figure 12: Accessing error logs via the session card]]

If you encounter any errors while using an interactive Open OnDemand job, you can check the logs for more information. To access the logs, navigate to the '''My Interactive Sessions''' tab and find your active session. Click on the <code>output.log</code> link (see Figure. 8) to open a separate tab which displays the output of your job. This file contains the standard output and error messages generated by the job, which can help you identify any issues that may have occurred during the session. When submitting a ticket to SciNet support, please include the <code>output.log</code> file, your '''Session ID''', which is displayed as a long string of characters, e.g. ''' 8feb45fa-bc65-4846-8398-2a73c1bf8e5a''', and any other relevant information to help us assist you more effectively.

File:Ood-oc-shortcuts.png

2025-12-08T14:23:33Z

Willis2: Willis2 uploaded a new version of File:Ood-oc-shortcuts.png

Main Page

2025-12-03T20:18:57Z

Willis2: /* System Status */

__NOTOC__
{| style="border-spacing:10px; width: 95%"
| style="padding:1em; padding-top:.1em; border:2px solid #0645ad; background-color:#f6f6f6; border-radius:7px"|

==System Status==


{|style="width:100%"
|{{Up3 | Trillium|https://docs.alliancecan.ca/wiki/Trillium_Quickstart}}
|{{Down | Niagara|Niagara_Quickstart}}
|{{Down | Teach|Teach}}
|{{Down | Rouge|Rouge}}
|-
|{{Up | OnDemand|Open_OnDemand_Quickstart}}
|{{Up3 | Scheduler|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Submitting_jobs_to_the_scheduler}}
|{{Up3 | File system|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Storage}}
|{{Up | Burst Buffer|Burst_Buffer}}
|-
|{{Up | HPSS|HPSS}}
|{{Up3 | Login Nodes|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Logging_in}}
|{{Up3 | External Network|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Logging_in}}
|{{Up | Globus |Globus}}
|-
|{{Up | Balam|Balam}}
|{{Up3 | Cvmfs|https://docs.alliancecan.ca/wiki/Standard_software_environments}}
|{{Up | S4H | S4H}}
|}

'''Tue Dec 3, 2025, 11:30 am:''' Open OnDemand is fully operational again.

'''Sat Nov 29, 2025, 00:40 am:''' There has been a problem with the water chiller. Some systems are offline.

'''Wed Nov 5, 2025, 12:55 pm:''' Balam is back online.

'''Wed Nov 5, 2025, 10:00 am:''' Open OnDemand is back online.

'''Tue Nov 4, 2025, 11:00 pm:''' Most of the work is done, data movers, Globus, and HPSS are back online. Remaining services will be worked on tomorrow.

'''Tue Nov 4, 2025, 8:30 am:''' Scheduled network maintenance. Trillium cluster is *not* affected.

'''Tue Oct 21, 2025, 17:30 am:''' Balam maintenance finished.

'''Tue Oct 21, 2025, 7:00 am:''' Balam maintenance day.

'''Thu Oct 15, 2025, 3:55 pm:''' Trillium inbound connections through trillium.alliancecan.ca or trillium.scinet.utoronto.ca are working again.

'''Thu Oct 15, 2025, 3:05 pm:''' Trillium is experiencing external network issues for both incoming traffic. Please try: ssh USERNAME@tri-login01.scinet.utoronto.ca in the meantime.

'''Thu Oct 06, 2025, 8:00 pm:''' HPSS is fully functional. You may submit archive jobs from trillium login nodes, datamovers and robots.

'''Thu Oct 03, 2025, 6:30 pm:''' HPSS is back online, and already accessible via alliancecan#hpss Globus endpoint. Directory tree now follows the other Alliance clusters. We're still working on job submission via Slurm

'''Thu Oct 01, 2025, 0:00 am:''' Niagara compute nodes are now unavailable for regular users. The login nodes will remain available for a while to allow a few last data transfers, although transfers from the Niagara file systems to Trillium are best done on nia-dm1.scinet.utoronto.ca.

'''Thu Oct 01, 2025, 9:30 am:''' HPSS is down for scheduled maintenance, including alliancecan#hpss Globus endpoint


[[Previous messages]]

{|style="border-spacing: 10px;width: 100%"
|valign="top" style="margin: 1em; padding:1em; padding-top:.1em; border:2px solid #000; background-color:#fff; border-radius:7px; width: 49.5%" |

== QuickStart Guides ==
* [https://docs.alliancecan.ca/wiki/Trillium_Quickstart Trillium Quickstart]
* [[Niagara Quickstart]]
* [[HPSS | HPSS archival storage]]
* [[Teach|Teach cluster]]
* [[FAQ | FAQ (frequently asked questions)]]
* [[Acknowledging SciNet]]
| valign="top" style="margin: 1em; padding:1em; padding-top:.1em; border:2px solid #000; background-color:#fff; border-radius:7px; width: 49.5%" |

== Tutorials, Manuals, etc. ==
* [https://education.scinet.utoronto.ca SciNet education material]
* [https://www.youtube.com/c/SciNetHPCattheUniversityofToronto SciNet's YouTube channel]
* [[Modules specific to Niagara|Software Modules specific to Niagara]]
* [[Modules for Mist]]
* [[Commercial software]]
* [[Burst Buffer]]
* [[SSH#SSH Keys|SSH keys]]
* [[SSH Tunneling]]
* [[Visualization]]
* [[Running Serial Jobs on Niagara]]
* [[Jupyter Hub]]
|}

Open OnDemand Quickstart

2025-11-26T21:44:09Z

Willis2: /* Open Composer */

{|align=right
|-
|[[Image:ood-logo.png|480px]]
|-
|}

= Porting existing virtual environments to Open OnDemand =

'''IMPORTANT: Because of the change of operating system and software stack, your exisiting virtual environment kernels for Python may not work right away in the OnDemand site. You should be able to activate your python environments in a Trillium terminal (see [[Open_OnDemand_Quickstart#Terminal access|Terminal access]]), with all required Trillium modules loaded, and then issue the command <code>venv2jup</code> to get them working correctly.'''

=Introduction=

This guide will walk you through the basic steps to get started with the SciNet Open OnDemand portal.
Open OnDemand (OOD) is a web-based platform that provides access to a wide range of scientific applications and computing resources, such as Jupyter Lab, R Studio, and VS Code. It allows you to interact with Trillium through a web browser instead of via a terminal, without the need to install any software on your local machine. You will be able to perform file management, submit/monitor jobs and run applications interactively. More information on this project can be found at [https://openondemand.org https://openondemand.org].

=Logging into the Open OnDemand portal=

[[Image:ood-dashboard.png|thumb|right|600px|Figure 1: Dashboard.]]

To access the Open OnDemand portal, open a web browser and navigate to the following page: https://ondemand.scinet.utoronto.ca. You will be prompted to enter your Alliance username and password, followed by a second factor authentication via Duo or Yubikey. Once you have logged in, you will be taken to the Open OnDemand dashboard. From here you can access the various tools and applications available on the platform.

=File management=

[[Image:ood-file-browser.png|thumb|right|600px|Figure 2: File browser.]]

The Open OnDemand platform provides a file browser that allows you to manage your files and directories on the filesystem. To access the file browser, click on the '''Files''' tab and select which directory you want to manage from the drop-down (<code>HOME</code>, <code>SCRATCH</code> or <code>PROJECT</code>). You will be taken to the file browser interface, where you can:

* Navigate through your directories
* Upload/download files
* Create new files/directories
* Delete files/directories
* Edit existing files

==Uploading Files==

The current file size upload limit is 10GB, if you need to upload a file larger than this or are facing upload issues due to a bad internet connection for example please try using [https://docs.scinet.utoronto.ca/index.php/Globus Globus]. There is a Globus button in the file browser at the top right, [[File:Globus_button.png | 300px]], which will take you to the Globus web interface where you can login with your Alliance username and password. The path navigated to in the Open OnDemand file browser will be the same path opened in Globus.

=Job submission=

[[Image:ood-job-composer.png|thumb|right|600px|Figure 3: Job Composer.]]

Open OnDemand also provides a job submission interface that allows you to submit batch jobs to Trillium. Navigate to the '''Jobs''' tab and select '''Job Composer''', this will take you to the job submission form. From here click on the '''New Job''' button which will offer you the following options:

* '''From Default Template''' - allows you to create a job from scratch
* '''From Template''' - allows you to select from some example jobs, e.g. MPI and OpenMP
* '''From Specified Path''' - allows you to use an existing job that you already have on the file system
* '''From Selected Job''' - copies the current job for you.

You can specify job parameters such as the job script and account name using the '''Job Options''' button. The remaining parameters such as the number of nodes, number of cores, wall clock time, etc. can be modified by editing the job script directly with the '''Open Editor''' button. Once you have filled in the required fields, click on the '''Submit''' button to submit the job.

The page also shows the status of your job so you can see whether it is queued, running or completed. You can also view the output and error logs of the job once it is finished by clicking on the relevant files under the '''Folder Contents''' section of the '''Job Details''' panel to the right.

=Job monitoring=

To get an overview of all your jobs in the queue you can use the job monitoring interface. Navigate to the '''Jobs''' tab and select '''Active Jobs'''. You can filter the jobs by using the '''Filter''' text box at the top right. Columns can also be sorted by clicking on the column headers, for example you can sort by job status (running, completed, failed, etc.). Clicking on <code>></code> to the left of a job will show you more details about the job, such as the start/end time, node list and account charged etc. You might also want to show all jobs in the queue, you can do this by clicking on the drop-down menu at the top right and selecting '''All Jobs'''. A more detailed view of your jobs can still be found using the [https://my.scinet.utoronto.ca myscinet portal].

[[Image:ood-active-jobs.png|thumb|center|600px|Figure 4: Active Jobs.]]

=Interactive applications=

Open OnDemand also features interactive applications that can be run directly from your web browser. To access the applications, navigate to the '''Interactive Apps''' tab and select the application you want to run from the drop-down. This will then bring you to the job submission page where you can choose job parameters such as:

* Length of job in hours
* Number of cores
* Amount of memory to allocate (GB)
* Notify me by email when the job starts

When you have chosen your job parameters click on the '''Launch''' button to submit your job to the queue. You will be taken to the '''My Interactive Sessions''' page where you can see the status of your job, i.e. queued, running or completed. Once the job has been assigned a node and is running, you can click on the '''Connect to ...''' button to launch the application. The application will open in a new tab in your browser, and you can interact with it as if it was running locally.

If you would like terminal access to the node where the application is running, to monitor the performance for example you can click on the button beside '''Host''' starting with <code>>_</code>. This will open a terminal window in your browser where you can run commands on the node directly.

If for whatever reason you would like to kill the job, you can do so by clicking on the red '''Delete''' button in the job panel in the '''My Interactive Sessions''' page.

<div style="margin: 0 auto; display: table;">
{| class="wikitable"
|-
| <div style="text-align: center;">
[[Image:jupyter-submit.png|600px]]
 Figure 5: Interactive app submission form.
</div>
| <div style="text-align: center;">
[[Image:ood_session_tab.png|600px]]
 Figure 6: Interactive sessions page.
[[Image:jupyter-session.png|600px]]
 Figure 7: Interactive app session.
</div>
|}
</div>

=Open Composer=

The [https://github.com/RIKEN-RCCS/OpenComposer Open Composer] app provides a suite of Slurm job template scripts that can be submitted directly to the Trillium scheduler. It also provides an interface to monitor your submitted jobs, via the '''History''' tab. You can access Open Composer by navigating to the '''Jobs''' drop-down menu and selecting '''Open Composer''' or by clicking on one of the Slurm job templates e.g. '''MPI Slurm Job''', '''OpenMP Slurm Job''' and '''Hybrid MPI/OpenMP Slurm Job'''.

[[Image:ood-oc-shortcuts.png|thumb|right|600px|Figure 8: Open Composer shortcuts.]]

Once you have selected a job template, you will be taken to the job submission page. This is split between the job parameters on the left and the job script itself on the right. The job parameters let you control how many resources your job will use, such as the number of nodes, number of tasks per node, wall clock time and output file name. The job script section displays the script that will be submitted to the scheduler. Any changes made to the job parameters will be reflected in the job script automatically. You may also edit the job script directly if you wish.

The extra fields at the top of the page allow you to change how your job is submitted:

* Script Location: specifies the directory where the job script will be saved and where your job will be run from.
* Script Name: specifies the name of the job script file.
* Job Name: specifies the name of the job that will appear in the job queue.

Once you are happy with your job script, click on the '''Submit''' button to submit the job to the scheduler. If your job was submitted successfully, you will see a confirmation message at the top of the page with your job ID [[File:ood-oc-job-submit.png | 300px]].

[[Image:ood-oc-job.png|thumb|center|600px|Figure 9: Open Composer job script editor.]]

Note: The template scripts provided in Open Composer are basic examples to get you started. You will need to modify the job script further to suit your specific needs, such as loading your required modules and specifying input/output files.

==Monitoring Jobs in Open Composer==

To monitor your submitted jobs in Open Composer, navigate to the '''History''' tab. This will display a list of all your submitted jobs, along with their status: Queued, Running, Completed, Failed. You can filter the jobs by using the '''Filter''' text box at the top right or by using the checkboxes below. Clicking on different column fields will give different information about the job:

* Job ID: displays detailed Slurm information about the job
* Application: opens the job script editor of the template you used
* Script Location: opens an OOD file browser window at the location of the job script. Clicking on the the small terminal icon will open a terminal in the job script location.
* Script Name: displays the job script that was submitted to the scheduler

[[Image:ood-oc-history.png|thumb|center|600px|Figure 10: Open Composer job monitoring.]]

==Supported Applications==

Open Composer currently supports the following applications:

* MPI Slurm Job
* OpenMP Slurm Job
* Hybrid MPI/OpenMP Slurm Job

==Installed Applications==

We currently support the following applications:

* [https://jupyter.org Jupyter Lab/Notebook]
* [https://posit.co/products/open-source/rstudio/?sid=1 Rstudio]
* [https://code.visualstudio.com VSCode]
* Desktop
* [https://www.paraview.org ParaView]
* [https://www.linaroforge.com Forge DDT/MAP]
* [https://www.sas.com/en_ca/home.html SAS]4
* [https://www.stata.com Stata]4
* [https://github.com/RIKEN-RCCS/OpenComposer Open Composer]

If you would like an application installed please email us at: [mailto:support@scinet.utoronto.ca support@scinet.utoronto.ca].

=Terminal access=

[[Image:ood-terminal.png|thumb|right|600px|Figure 11: Terminal]]

Sometimes you might prefer to use a terminal to interact with Trillium, Open OnDemand provides a web-based terminal that you can use to access the command line interface. To access the terminal, navigate to the '''Clusters''' tab and select '''Trillium Shell Access'''. This will open a new tab in your browser with a terminal window where you can run commands as you would in a regular terminal session.

= Differences compared to the Jupyter Hub=

{| class="wikitable"
!feature !! Jupyter Hub (decommissioned) !! Open OnDemand
|-
| ''authentication'' || password || password + MFA
|-
| ''first installed'' || 2017 || 2025
|-
| ''last update'' || 2021 || 2025
|-
| ''supports''
| Jupyter Notebook, JupyterLab (R, Python, Julia)
| Jupyter Notebook, JupyterLab (R, Python), Rstudio, VSCode, Desktop, SAS4, Stata4, ParaView, Forge DDT/MAP
|-
| ''start and continue later'' || Yes || Yes1
|-
| ''command terminal'' || No || Yes
|-
| ''file management'' || Yes (limited) || Yes
|-
| ''monitor jobs'' || No || Yes
|-
| ''submit jobs'' || No || Yes
|-
| ''core limit'' || 8 cores2 || 20 cores (8 for high memory)3
|-
| ''memory limit'' || 48 GB2 || 85 GB (500 GB for high memory)3
|-
| ''time limits'' || 3 days2 || 3 days3
|-
| ''operating system'' || CentOS 7 || RockyLinux 9
|-
| ''software stack'' || NiaEnv, CCEnv || CCEnv
|-
| ''system issue alerts'' || No || Yes
|-
| ''user quota alerts'' || No || Yes
|-
| ''error logs'' || No || Yes
|-
| ''hardware'' || 1 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM || 62 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 180GB RAM (default) 3 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM (high memory)
|}

1 Within the requested limits.

2 Limits on JupyterHub were not implementated very strictly, so you could temporarily exceed these.

3 Limits need to be requested before starting an application.

4 Only for users with a license for these products.

= Debugging Errors =

[[Image:ood-session-id.png|thumb|right|600px|Figure 12: Accessing error logs via the session card]]

If you encounter any errors while using an interactive Open OnDemand job, you can check the logs for more information. To access the logs, navigate to the '''My Interactive Sessions''' tab and find your active session. Click on the <code>output.log</code> link (see Figure. 8) to open a separate tab which displays the output of your job. This file contains the standard output and error messages generated by the job, which can help you identify any issues that may have occurred during the session. When submitting a ticket to SciNet support, please include the <code>output.log</code> file, your '''Session ID''', which is displayed as a long string of characters, e.g. ''' 8feb45fa-bc65-4846-8398-2a73c1bf8e5a''', and any other relevant information to help us assist you more effectively.

Open OnDemand Quickstart

2025-11-26T21:38:18Z

Willis2: /* Monitoring Jobs in Open Composer */

{|align=right
|-
|[[Image:ood-logo.png|480px]]
|-
|}

= Porting existing virtual environments to Open OnDemand =

'''IMPORTANT: Because of the change of operating system and software stack, your exisiting virtual environment kernels for Python may not work right away in the OnDemand site. You should be able to activate your python environments in a Trillium terminal (see [[Open_OnDemand_Quickstart#Terminal access|Terminal access]]), with all required Trillium modules loaded, and then issue the command <code>venv2jup</code> to get them working correctly.'''

=Introduction=

This guide will walk you through the basic steps to get started with the SciNet Open OnDemand portal.
Open OnDemand (OOD) is a web-based platform that provides access to a wide range of scientific applications and computing resources, such as Jupyter Lab, R Studio, and VS Code. It allows you to interact with Trillium through a web browser instead of via a terminal, without the need to install any software on your local machine. You will be able to perform file management, submit/monitor jobs and run applications interactively. More information on this project can be found at [https://openondemand.org https://openondemand.org].

=Logging into the Open OnDemand portal=

[[Image:ood-dashboard.png|thumb|right|600px|Figure 1: Dashboard.]]

To access the Open OnDemand portal, open a web browser and navigate to the following page: https://ondemand.scinet.utoronto.ca. You will be prompted to enter your Alliance username and password, followed by a second factor authentication via Duo or Yubikey. Once you have logged in, you will be taken to the Open OnDemand dashboard. From here you can access the various tools and applications available on the platform.

=File management=

[[Image:ood-file-browser.png|thumb|right|600px|Figure 2: File browser.]]

The Open OnDemand platform provides a file browser that allows you to manage your files and directories on the filesystem. To access the file browser, click on the '''Files''' tab and select which directory you want to manage from the drop-down (<code>HOME</code>, <code>SCRATCH</code> or <code>PROJECT</code>). You will be taken to the file browser interface, where you can:

* Navigate through your directories
* Upload/download files
* Create new files/directories
* Delete files/directories
* Edit existing files

==Uploading Files==

The current file size upload limit is 10GB, if you need to upload a file larger than this or are facing upload issues due to a bad internet connection for example please try using [https://docs.scinet.utoronto.ca/index.php/Globus Globus]. There is a Globus button in the file browser at the top right, [[File:Globus_button.png | 300px]], which will take you to the Globus web interface where you can login with your Alliance username and password. The path navigated to in the Open OnDemand file browser will be the same path opened in Globus.

=Job submission=

[[Image:ood-job-composer.png|thumb|right|600px|Figure 3: Job Composer.]]

Open OnDemand also provides a job submission interface that allows you to submit batch jobs to Trillium. Navigate to the '''Jobs''' tab and select '''Job Composer''', this will take you to the job submission form. From here click on the '''New Job''' button which will offer you the following options:

* '''From Default Template''' - allows you to create a job from scratch
* '''From Template''' - allows you to select from some example jobs, e.g. MPI and OpenMP
* '''From Specified Path''' - allows you to use an existing job that you already have on the file system
* '''From Selected Job''' - copies the current job for you.

You can specify job parameters such as the job script and account name using the '''Job Options''' button. The remaining parameters such as the number of nodes, number of cores, wall clock time, etc. can be modified by editing the job script directly with the '''Open Editor''' button. Once you have filled in the required fields, click on the '''Submit''' button to submit the job.

The page also shows the status of your job so you can see whether it is queued, running or completed. You can also view the output and error logs of the job once it is finished by clicking on the relevant files under the '''Folder Contents''' section of the '''Job Details''' panel to the right.

=Job monitoring=

To get an overview of all your jobs in the queue you can use the job monitoring interface. Navigate to the '''Jobs''' tab and select '''Active Jobs'''. You can filter the jobs by using the '''Filter''' text box at the top right. Columns can also be sorted by clicking on the column headers, for example you can sort by job status (running, completed, failed, etc.). Clicking on <code>></code> to the left of a job will show you more details about the job, such as the start/end time, node list and account charged etc. You might also want to show all jobs in the queue, you can do this by clicking on the drop-down menu at the top right and selecting '''All Jobs'''. A more detailed view of your jobs can still be found using the [https://my.scinet.utoronto.ca myscinet portal].

[[Image:ood-active-jobs.png|thumb|center|600px|Figure 4: Active Jobs.]]

=Interactive applications=

Open OnDemand also features interactive applications that can be run directly from your web browser. To access the applications, navigate to the '''Interactive Apps''' tab and select the application you want to run from the drop-down. This will then bring you to the job submission page where you can choose job parameters such as:

* Length of job in hours
* Number of cores
* Amount of memory to allocate (GB)
* Notify me by email when the job starts

When you have chosen your job parameters click on the '''Launch''' button to submit your job to the queue. You will be taken to the '''My Interactive Sessions''' page where you can see the status of your job, i.e. queued, running or completed. Once the job has been assigned a node and is running, you can click on the '''Connect to ...''' button to launch the application. The application will open in a new tab in your browser, and you can interact with it as if it was running locally.

If you would like terminal access to the node where the application is running, to monitor the performance for example you can click on the button beside '''Host''' starting with <code>>_</code>. This will open a terminal window in your browser where you can run commands on the node directly.

If for whatever reason you would like to kill the job, you can do so by clicking on the red '''Delete''' button in the job panel in the '''My Interactive Sessions''' page.

<div style="margin: 0 auto; display: table;">
{| class="wikitable"
|-
| <div style="text-align: center;">
[[Image:jupyter-submit.png|600px]]
 Figure 5: Interactive app submission form.
</div>
| <div style="text-align: center;">
[[Image:ood_session_tab.png|600px]]
 Figure 6: Interactive sessions page.
[[Image:jupyter-session.png|600px]]
 Figure 7: Interactive app session.
</div>
|}
</div>

=Open Composer=

The [https://github.com/RIKEN-RCCS/OpenComposer Open Composer] app provides a suite of Slurm job template scripts that can be submitted directly to the Trillium scheduler. It also provides an interface to monitor your submitted jobs, via the '''History''' tab. You can access Open Composer by navigating to the '''Jobs''' drop-down menu and selecting '''Open Composer''' or by clicking on one of the Slurm job templates e.g. '''MPI Slurm Job''', '''OpenMP Slurm Job''' and '''Hybrid MPI/OpenMP Slurm Job'''.

[[Image:ood-oc-shortcuts.png|thumb|right|600px|Figure 8: Open Composer shortcuts.]]

Once you have selected a job template, you will be taken to the job submission page. This is split between the job parameters on the left and the job script itself on the right. The job parameters let you control how many resources your job will use, such as the number of nodes, number of tasks per node, wall clock time and output file name. The job script section displays the script that will be submitted to the scheduler. Any changes made to the job parameters will be reflected in the job script automatically. You may also edit the job script directly if you wish.

The extra fields at the top of the page allow you to change how your job is submitted:

* Script Location: specifies the directory where the job script will be saved and where your job will be run from.
* Script Name: specifies the name of the job script file.
* Job Name: specifies the name of the job that will appear in the job queue.

Once you are happy with your job script, click on the '''Submit''' button to submit the job to the scheduler. If your job was submitted successfully, you will see a confirmation message at the top of the page with your job ID [[File:ood-oc-job-submit.png | 300px]].

[[Image:ood-oc-job.png|thumb|center|600px|Figure 9: Open Composer job script editor.]]

Note: The template scripts provided in Open Composer are basic examples to get you started. You will need to modify the job script further to suit your specific needs, such as loading your required modules and specifying input/output files.

==Monitoring Jobs in Open Composer==

To monitor your submitted jobs in Open Composer, navigate to the '''History''' tab. This will display a list of all your submitted jobs, along with their status: Queued, Running, Completed, Failed. You can filter the jobs by using the '''Filter''' text box at the top right or by using the checkboxes below. Clicking on different column fields will give different information about the job:

* Job ID: displays detailed Slurm information about the job
* Application: opens the job script editor of the template you used
* Script Location: opens an OOD file browser window at the location of the job script. Clicking on the the small terminal icon will open a terminal in the job script location.
* Script Name: displays the job script that was submitted to the scheduler

[[Image:ood-oc-history.png|thumb|center|600px|Figure 10: Open Composer job monitoring.]]

==Installed Applications==

We currently support the following applications:

* [https://jupyter.org Jupyter Lab/Notebook]
* [https://posit.co/products/open-source/rstudio/?sid=1 Rstudio]
* [https://code.visualstudio.com VSCode]
* Desktop
* [https://www.paraview.org ParaView]
* [https://www.linaroforge.com Forge DDT/MAP]
* [https://www.sas.com/en_ca/home.html SAS]4
* [https://www.stata.com Stata]4
* [https://github.com/RIKEN-RCCS/OpenComposer Open Composer]

If you would like an application installed please email us at: [mailto:support@scinet.utoronto.ca support@scinet.utoronto.ca].

=Terminal access=

[[Image:ood-terminal.png|thumb|right|600px|Figure 11: Terminal]]

Sometimes you might prefer to use a terminal to interact with Trillium, Open OnDemand provides a web-based terminal that you can use to access the command line interface. To access the terminal, navigate to the '''Clusters''' tab and select '''Trillium Shell Access'''. This will open a new tab in your browser with a terminal window where you can run commands as you would in a regular terminal session.

= Differences compared to the Jupyter Hub=

{| class="wikitable"
!feature !! Jupyter Hub (decommissioned) !! Open OnDemand
|-
| ''authentication'' || password || password + MFA
|-
| ''first installed'' || 2017 || 2025
|-
| ''last update'' || 2021 || 2025
|-
| ''supports''
| Jupyter Notebook, JupyterLab (R, Python, Julia)
| Jupyter Notebook, JupyterLab (R, Python), Rstudio, VSCode, Desktop, SAS4, Stata4, ParaView, Forge DDT/MAP
|-
| ''start and continue later'' || Yes || Yes1
|-
| ''command terminal'' || No || Yes
|-
| ''file management'' || Yes (limited) || Yes
|-
| ''monitor jobs'' || No || Yes
|-
| ''submit jobs'' || No || Yes
|-
| ''core limit'' || 8 cores2 || 20 cores (8 for high memory)3
|-
| ''memory limit'' || 48 GB2 || 85 GB (500 GB for high memory)3
|-
| ''time limits'' || 3 days2 || 3 days3
|-
| ''operating system'' || CentOS 7 || RockyLinux 9
|-
| ''software stack'' || NiaEnv, CCEnv || CCEnv
|-
| ''system issue alerts'' || No || Yes
|-
| ''user quota alerts'' || No || Yes
|-
| ''error logs'' || No || Yes
|-
| ''hardware'' || 1 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM || 62 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 180GB RAM (default) 3 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM (high memory)
|}

1 Within the requested limits.

2 Limits on JupyterHub were not implementated very strictly, so you could temporarily exceed these.

3 Limits need to be requested before starting an application.

4 Only for users with a license for these products.

= Debugging Errors =

[[Image:ood-session-id.png|thumb|right|600px|Figure 12: Accessing error logs via the session card]]

If you encounter any errors while using an interactive Open OnDemand job, you can check the logs for more information. To access the logs, navigate to the '''My Interactive Sessions''' tab and find your active session. Click on the <code>output.log</code> link (see Figure. 8) to open a separate tab which displays the output of your job. This file contains the standard output and error messages generated by the job, which can help you identify any issues that may have occurred during the session. When submitting a ticket to SciNet support, please include the <code>output.log</code> file, your '''Session ID''', which is displayed as a long string of characters, e.g. ''' 8feb45fa-bc65-4846-8398-2a73c1bf8e5a''', and any other relevant information to help us assist you more effectively.

Open OnDemand Quickstart

2025-11-26T21:33:30Z

Willis2: /* Monitoring Jobs in Open Composer */

{|align=right
|-
|[[Image:ood-logo.png|480px]]
|-
|}

= Porting existing virtual environments to Open OnDemand =

'''IMPORTANT: Because of the change of operating system and software stack, your exisiting virtual environment kernels for Python may not work right away in the OnDemand site. You should be able to activate your python environments in a Trillium terminal (see [[Open_OnDemand_Quickstart#Terminal access|Terminal access]]), with all required Trillium modules loaded, and then issue the command <code>venv2jup</code> to get them working correctly.'''

=Introduction=

This guide will walk you through the basic steps to get started with the SciNet Open OnDemand portal.
Open OnDemand (OOD) is a web-based platform that provides access to a wide range of scientific applications and computing resources, such as Jupyter Lab, R Studio, and VS Code. It allows you to interact with Trillium through a web browser instead of via a terminal, without the need to install any software on your local machine. You will be able to perform file management, submit/monitor jobs and run applications interactively. More information on this project can be found at [https://openondemand.org https://openondemand.org].

=Logging into the Open OnDemand portal=

[[Image:ood-dashboard.png|thumb|right|600px|Figure 1: Dashboard.]]

To access the Open OnDemand portal, open a web browser and navigate to the following page: https://ondemand.scinet.utoronto.ca. You will be prompted to enter your Alliance username and password, followed by a second factor authentication via Duo or Yubikey. Once you have logged in, you will be taken to the Open OnDemand dashboard. From here you can access the various tools and applications available on the platform.

=File management=

[[Image:ood-file-browser.png|thumb|right|600px|Figure 2: File browser.]]

The Open OnDemand platform provides a file browser that allows you to manage your files and directories on the filesystem. To access the file browser, click on the '''Files''' tab and select which directory you want to manage from the drop-down (<code>HOME</code>, <code>SCRATCH</code> or <code>PROJECT</code>). You will be taken to the file browser interface, where you can:

* Navigate through your directories
* Upload/download files
* Create new files/directories
* Delete files/directories
* Edit existing files

==Uploading Files==

The current file size upload limit is 10GB, if you need to upload a file larger than this or are facing upload issues due to a bad internet connection for example please try using [https://docs.scinet.utoronto.ca/index.php/Globus Globus]. There is a Globus button in the file browser at the top right, [[File:Globus_button.png | 300px]], which will take you to the Globus web interface where you can login with your Alliance username and password. The path navigated to in the Open OnDemand file browser will be the same path opened in Globus.

=Job submission=

[[Image:ood-job-composer.png|thumb|right|600px|Figure 3: Job Composer.]]

Open OnDemand also provides a job submission interface that allows you to submit batch jobs to Trillium. Navigate to the '''Jobs''' tab and select '''Job Composer''', this will take you to the job submission form. From here click on the '''New Job''' button which will offer you the following options:

* '''From Default Template''' - allows you to create a job from scratch
* '''From Template''' - allows you to select from some example jobs, e.g. MPI and OpenMP
* '''From Specified Path''' - allows you to use an existing job that you already have on the file system
* '''From Selected Job''' - copies the current job for you.

You can specify job parameters such as the job script and account name using the '''Job Options''' button. The remaining parameters such as the number of nodes, number of cores, wall clock time, etc. can be modified by editing the job script directly with the '''Open Editor''' button. Once you have filled in the required fields, click on the '''Submit''' button to submit the job.

The page also shows the status of your job so you can see whether it is queued, running or completed. You can also view the output and error logs of the job once it is finished by clicking on the relevant files under the '''Folder Contents''' section of the '''Job Details''' panel to the right.

=Job monitoring=

To get an overview of all your jobs in the queue you can use the job monitoring interface. Navigate to the '''Jobs''' tab and select '''Active Jobs'''. You can filter the jobs by using the '''Filter''' text box at the top right. Columns can also be sorted by clicking on the column headers, for example you can sort by job status (running, completed, failed, etc.). Clicking on <code>></code> to the left of a job will show you more details about the job, such as the start/end time, node list and account charged etc. You might also want to show all jobs in the queue, you can do this by clicking on the drop-down menu at the top right and selecting '''All Jobs'''. A more detailed view of your jobs can still be found using the [https://my.scinet.utoronto.ca myscinet portal].

[[Image:ood-active-jobs.png|thumb|center|600px|Figure 4: Active Jobs.]]

=Interactive applications=

Open OnDemand also features interactive applications that can be run directly from your web browser. To access the applications, navigate to the '''Interactive Apps''' tab and select the application you want to run from the drop-down. This will then bring you to the job submission page where you can choose job parameters such as:

* Length of job in hours
* Number of cores
* Amount of memory to allocate (GB)
* Notify me by email when the job starts

When you have chosen your job parameters click on the '''Launch''' button to submit your job to the queue. You will be taken to the '''My Interactive Sessions''' page where you can see the status of your job, i.e. queued, running or completed. Once the job has been assigned a node and is running, you can click on the '''Connect to ...''' button to launch the application. The application will open in a new tab in your browser, and you can interact with it as if it was running locally.

If you would like terminal access to the node where the application is running, to monitor the performance for example you can click on the button beside '''Host''' starting with <code>>_</code>. This will open a terminal window in your browser where you can run commands on the node directly.

If for whatever reason you would like to kill the job, you can do so by clicking on the red '''Delete''' button in the job panel in the '''My Interactive Sessions''' page.

<div style="margin: 0 auto; display: table;">
{| class="wikitable"
|-
| <div style="text-align: center;">
[[Image:jupyter-submit.png|600px]]
 Figure 5: Interactive app submission form.
</div>
| <div style="text-align: center;">
[[Image:ood_session_tab.png|600px]]
 Figure 6: Interactive sessions page.
[[Image:jupyter-session.png|600px]]
 Figure 7: Interactive app session.
</div>
|}
</div>

=Open Composer=

The [https://github.com/RIKEN-RCCS/OpenComposer Open Composer] app provides a suite of Slurm job template scripts that can be submitted directly to the Trillium scheduler. It also provides an interface to monitor your submitted jobs, via the '''History''' tab. You can access Open Composer by navigating to the '''Jobs''' drop-down menu and selecting '''Open Composer''' or by clicking on one of the Slurm job templates e.g. '''MPI Slurm Job''', '''OpenMP Slurm Job''' and '''Hybrid MPI/OpenMP Slurm Job'''.

[[Image:ood-oc-shortcuts.png|thumb|right|600px|Figure 8: Open Composer shortcuts.]]

Once you have selected a job template, you will be taken to the job submission page. This is split between the job parameters on the left and the job script itself on the right. The job parameters let you control how many resources your job will use, such as the number of nodes, number of tasks per node, wall clock time and output file name. The job script section displays the script that will be submitted to the scheduler. Any changes made to the job parameters will be reflected in the job script automatically. You may also edit the job script directly if you wish.

The extra fields at the top of the page allow you to change how your job is submitted:

* Script Location: specifies the directory where the job script will be saved and where your job will be run from.
* Script Name: specifies the name of the job script file.
* Job Name: specifies the name of the job that will appear in the job queue.

Once you are happy with your job script, click on the '''Submit''' button to submit the job to the scheduler. If your job was submitted successfully, you will see a confirmation message at the top of the page with your job ID [[File:ood-oc-job-submit.png | 300px]].

[[Image:ood-oc-job.png|thumb|center|600px|Figure 9: Open Composer job script editor.]]

Note: The template scripts provided in Open Composer are basic examples to get you started. You will need to modify the job script further to suit your specific needs, such as loading your required modules and specifying input/output files.

==Monitoring Jobs in Open Composer==

To monitor your submitted jobs in Open Composer, navigate to the '''History''' tab. This will display a list of all your submitted jobs, along with their status: Queued, Running, Completed, Failed. You can filter the jobs by using the '''Filter''' text box at the top right or by using the checkboxes below. Clicking on different column fields will give different information about the job:

* Job ID: displays detailed Slurm information about the job
* Application: opens the job script editor of the template you used
* Script Location: opens an OOD file browser window at the location of the job script
* Script Name: displays the job script that was submitted to the scheduler

[[Image:ood-oc-history.png|thumb|center|600px|Figure 10: Open Composer job monitoring.]]

==Installed Applications==

We currently support the following applications:

* [https://jupyter.org Jupyter Lab/Notebook]
* [https://posit.co/products/open-source/rstudio/?sid=1 Rstudio]
* [https://code.visualstudio.com VSCode]
* Desktop
* [https://www.paraview.org ParaView]
* [https://www.linaroforge.com Forge DDT/MAP]
* [https://www.sas.com/en_ca/home.html SAS]4
* [https://www.stata.com Stata]4
* [https://github.com/RIKEN-RCCS/OpenComposer Open Composer]

If you would like an application installed please email us at: [mailto:support@scinet.utoronto.ca support@scinet.utoronto.ca].

=Terminal access=

[[Image:ood-terminal.png|thumb|right|600px|Figure 11: Terminal]]

Sometimes you might prefer to use a terminal to interact with Trillium, Open OnDemand provides a web-based terminal that you can use to access the command line interface. To access the terminal, navigate to the '''Clusters''' tab and select '''Trillium Shell Access'''. This will open a new tab in your browser with a terminal window where you can run commands as you would in a regular terminal session.

= Differences compared to the Jupyter Hub=

{| class="wikitable"
!feature !! Jupyter Hub (decommissioned) !! Open OnDemand
|-
| ''authentication'' || password || password + MFA
|-
| ''first installed'' || 2017 || 2025
|-
| ''last update'' || 2021 || 2025
|-
| ''supports''
| Jupyter Notebook, JupyterLab (R, Python, Julia)
| Jupyter Notebook, JupyterLab (R, Python), Rstudio, VSCode, Desktop, SAS4, Stata4, ParaView, Forge DDT/MAP
|-
| ''start and continue later'' || Yes || Yes1
|-
| ''command terminal'' || No || Yes
|-
| ''file management'' || Yes (limited) || Yes
|-
| ''monitor jobs'' || No || Yes
|-
| ''submit jobs'' || No || Yes
|-
| ''core limit'' || 8 cores2 || 20 cores (8 for high memory)3
|-
| ''memory limit'' || 48 GB2 || 85 GB (500 GB for high memory)3
|-
| ''time limits'' || 3 days2 || 3 days3
|-
| ''operating system'' || CentOS 7 || RockyLinux 9
|-
| ''software stack'' || NiaEnv, CCEnv || CCEnv
|-
| ''system issue alerts'' || No || Yes
|-
| ''user quota alerts'' || No || Yes
|-
| ''error logs'' || No || Yes
|-
| ''hardware'' || 1 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM || 62 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 180GB RAM (default) 3 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM (high memory)
|}

1 Within the requested limits.

2 Limits on JupyterHub were not implementated very strictly, so you could temporarily exceed these.

3 Limits need to be requested before starting an application.

4 Only for users with a license for these products.

= Debugging Errors =

[[Image:ood-session-id.png|thumb|right|600px|Figure 12: Accessing error logs via the session card]]

If you encounter any errors while using an interactive Open OnDemand job, you can check the logs for more information. To access the logs, navigate to the '''My Interactive Sessions''' tab and find your active session. Click on the <code>output.log</code> link (see Figure. 8) to open a separate tab which displays the output of your job. This file contains the standard output and error messages generated by the job, which can help you identify any issues that may have occurred during the session. When submitting a ticket to SciNet support, please include the <code>output.log</code> file, your '''Session ID''', which is displayed as a long string of characters, e.g. ''' 8feb45fa-bc65-4846-8398-2a73c1bf8e5a''', and any other relevant information to help us assist you more effectively.

File:Ood-oc-history.png

2025-11-26T21:32:22Z

Willis2:

Open OnDemand Quickstart

2025-11-26T21:30:50Z

Willis2: /* Open Composer */

{|align=right
|-
|[[Image:ood-logo.png|480px]]
|-
|}

= Porting existing virtual environments to Open OnDemand =

'''IMPORTANT: Because of the change of operating system and software stack, your exisiting virtual environment kernels for Python may not work right away in the OnDemand site. You should be able to activate your python environments in a Trillium terminal (see [[Open_OnDemand_Quickstart#Terminal access|Terminal access]]), with all required Trillium modules loaded, and then issue the command <code>venv2jup</code> to get them working correctly.'''

=Introduction=

This guide will walk you through the basic steps to get started with the SciNet Open OnDemand portal.
Open OnDemand (OOD) is a web-based platform that provides access to a wide range of scientific applications and computing resources, such as Jupyter Lab, R Studio, and VS Code. It allows you to interact with Trillium through a web browser instead of via a terminal, without the need to install any software on your local machine. You will be able to perform file management, submit/monitor jobs and run applications interactively. More information on this project can be found at [https://openondemand.org https://openondemand.org].

=Logging into the Open OnDemand portal=

[[Image:ood-dashboard.png|thumb|right|600px|Figure 1: Dashboard.]]

To access the Open OnDemand portal, open a web browser and navigate to the following page: https://ondemand.scinet.utoronto.ca. You will be prompted to enter your Alliance username and password, followed by a second factor authentication via Duo or Yubikey. Once you have logged in, you will be taken to the Open OnDemand dashboard. From here you can access the various tools and applications available on the platform.

=File management=

[[Image:ood-file-browser.png|thumb|right|600px|Figure 2: File browser.]]

The Open OnDemand platform provides a file browser that allows you to manage your files and directories on the filesystem. To access the file browser, click on the '''Files''' tab and select which directory you want to manage from the drop-down (<code>HOME</code>, <code>SCRATCH</code> or <code>PROJECT</code>). You will be taken to the file browser interface, where you can:

* Navigate through your directories
* Upload/download files
* Create new files/directories
* Delete files/directories
* Edit existing files

==Uploading Files==

The current file size upload limit is 10GB, if you need to upload a file larger than this or are facing upload issues due to a bad internet connection for example please try using [https://docs.scinet.utoronto.ca/index.php/Globus Globus]. There is a Globus button in the file browser at the top right, [[File:Globus_button.png | 300px]], which will take you to the Globus web interface where you can login with your Alliance username and password. The path navigated to in the Open OnDemand file browser will be the same path opened in Globus.

=Job submission=

[[Image:ood-job-composer.png|thumb|right|600px|Figure 3: Job Composer.]]

Open OnDemand also provides a job submission interface that allows you to submit batch jobs to Trillium. Navigate to the '''Jobs''' tab and select '''Job Composer''', this will take you to the job submission form. From here click on the '''New Job''' button which will offer you the following options:

* '''From Default Template''' - allows you to create a job from scratch
* '''From Template''' - allows you to select from some example jobs, e.g. MPI and OpenMP
* '''From Specified Path''' - allows you to use an existing job that you already have on the file system
* '''From Selected Job''' - copies the current job for you.

You can specify job parameters such as the job script and account name using the '''Job Options''' button. The remaining parameters such as the number of nodes, number of cores, wall clock time, etc. can be modified by editing the job script directly with the '''Open Editor''' button. Once you have filled in the required fields, click on the '''Submit''' button to submit the job.

The page also shows the status of your job so you can see whether it is queued, running or completed. You can also view the output and error logs of the job once it is finished by clicking on the relevant files under the '''Folder Contents''' section of the '''Job Details''' panel to the right.

=Job monitoring=

To get an overview of all your jobs in the queue you can use the job monitoring interface. Navigate to the '''Jobs''' tab and select '''Active Jobs'''. You can filter the jobs by using the '''Filter''' text box at the top right. Columns can also be sorted by clicking on the column headers, for example you can sort by job status (running, completed, failed, etc.). Clicking on <code>></code> to the left of a job will show you more details about the job, such as the start/end time, node list and account charged etc. You might also want to show all jobs in the queue, you can do this by clicking on the drop-down menu at the top right and selecting '''All Jobs'''. A more detailed view of your jobs can still be found using the [https://my.scinet.utoronto.ca myscinet portal].

[[Image:ood-active-jobs.png|thumb|center|600px|Figure 4: Active Jobs.]]

=Interactive applications=

Open OnDemand also features interactive applications that can be run directly from your web browser. To access the applications, navigate to the '''Interactive Apps''' tab and select the application you want to run from the drop-down. This will then bring you to the job submission page where you can choose job parameters such as:

* Length of job in hours
* Number of cores
* Amount of memory to allocate (GB)
* Notify me by email when the job starts

When you have chosen your job parameters click on the '''Launch''' button to submit your job to the queue. You will be taken to the '''My Interactive Sessions''' page where you can see the status of your job, i.e. queued, running or completed. Once the job has been assigned a node and is running, you can click on the '''Connect to ...''' button to launch the application. The application will open in a new tab in your browser, and you can interact with it as if it was running locally.

If you would like terminal access to the node where the application is running, to monitor the performance for example you can click on the button beside '''Host''' starting with <code>>_</code>. This will open a terminal window in your browser where you can run commands on the node directly.

If for whatever reason you would like to kill the job, you can do so by clicking on the red '''Delete''' button in the job panel in the '''My Interactive Sessions''' page.

<div style="margin: 0 auto; display: table;">
{| class="wikitable"
|-
| <div style="text-align: center;">
[[Image:jupyter-submit.png|600px]]
 Figure 5: Interactive app submission form.
</div>
| <div style="text-align: center;">
[[Image:ood_session_tab.png|600px]]
 Figure 6: Interactive sessions page.
[[Image:jupyter-session.png|600px]]
 Figure 7: Interactive app session.
</div>
|}
</div>

=Open Composer=

The [https://github.com/RIKEN-RCCS/OpenComposer Open Composer] app provides a suite of Slurm job template scripts that can be submitted directly to the Trillium scheduler. It also provides an interface to monitor your submitted jobs, via the '''History''' tab. You can access Open Composer by navigating to the '''Jobs''' drop-down menu and selecting '''Open Composer''' or by clicking on one of the Slurm job templates e.g. '''MPI Slurm Job''', '''OpenMP Slurm Job''' and '''Hybrid MPI/OpenMP Slurm Job'''.

[[Image:ood-oc-shortcuts.png|thumb|right|600px|Figure 8: Open Composer shortcuts.]]

Once you have selected a job template, you will be taken to the job submission page. This is split between the job parameters on the left and the job script itself on the right. The job parameters let you control how many resources your job will use, such as the number of nodes, number of tasks per node, wall clock time and output file name. The job script section displays the script that will be submitted to the scheduler. Any changes made to the job parameters will be reflected in the job script automatically. You may also edit the job script directly if you wish.

The extra fields at the top of the page allow you to change how your job is submitted:

* Script Location: specifies the directory where the job script will be saved and where your job will be run from.
* Script Name: specifies the name of the job script file.
* Job Name: specifies the name of the job that will appear in the job queue.

Once you are happy with your job script, click on the '''Submit''' button to submit the job to the scheduler. If your job was submitted successfully, you will see a confirmation message at the top of the page with your job ID [[File:ood-oc-job-submit.png | 300px]].

[[Image:ood-oc-job.png|thumb|center|600px|Figure 9: Open Composer job script editor.]]

Note: The template scripts provided in Open Composer are basic examples to get you started. You will need to modify the job script further to suit your specific needs, such as loading your required modules and specifying input/output files.

==Monitoring Jobs in Open Composer==

To monitor your submitted jobs in Open Composer, navigate to the '''History''' tab. This will display a list of all your submitted jobs, along with their status: Queued, Running, Completed, Failed. You can filter the jobs by using the '''Filter''' text box at the top right or by using the checkboxes below. Clicking on different column fields will give different information about the job:

* Job ID: displays detailed Slurm information about the job
* Application: opens the job script editor of the template you used
* Script Location: opens an OOD file browser window at the location of the job script
* Script Name: displays the job script that was submitted to the scheduler

[[Image:ood-oc-history.png|thumb|right|600px|Figure 10: Open Composer job monitoring.]]

==Installed Applications==

We currently support the following applications:

* [https://jupyter.org Jupyter Lab/Notebook]
* [https://posit.co/products/open-source/rstudio/?sid=1 Rstudio]
* [https://code.visualstudio.com VSCode]
* Desktop
* [https://www.paraview.org ParaView]
* [https://www.linaroforge.com Forge DDT/MAP]
* [https://www.sas.com/en_ca/home.html SAS]4
* [https://www.stata.com Stata]4
* [https://github.com/RIKEN-RCCS/OpenComposer Open Composer]

If you would like an application installed please email us at: [mailto:support@scinet.utoronto.ca support@scinet.utoronto.ca].

=Terminal access=

[[Image:ood-terminal.png|thumb|right|600px|Figure 11: Terminal]]

Sometimes you might prefer to use a terminal to interact with Trillium, Open OnDemand provides a web-based terminal that you can use to access the command line interface. To access the terminal, navigate to the '''Clusters''' tab and select '''Trillium Shell Access'''. This will open a new tab in your browser with a terminal window where you can run commands as you would in a regular terminal session.

= Differences compared to the Jupyter Hub=

{| class="wikitable"
!feature !! Jupyter Hub (decommissioned) !! Open OnDemand
|-
| ''authentication'' || password || password + MFA
|-
| ''first installed'' || 2017 || 2025
|-
| ''last update'' || 2021 || 2025
|-
| ''supports''
| Jupyter Notebook, JupyterLab (R, Python, Julia)
| Jupyter Notebook, JupyterLab (R, Python), Rstudio, VSCode, Desktop, SAS4, Stata4, ParaView, Forge DDT/MAP
|-
| ''start and continue later'' || Yes || Yes1
|-
| ''command terminal'' || No || Yes
|-
| ''file management'' || Yes (limited) || Yes
|-
| ''monitor jobs'' || No || Yes
|-
| ''submit jobs'' || No || Yes
|-
| ''core limit'' || 8 cores2 || 20 cores (8 for high memory)3
|-
| ''memory limit'' || 48 GB2 || 85 GB (500 GB for high memory)3
|-
| ''time limits'' || 3 days2 || 3 days3
|-
| ''operating system'' || CentOS 7 || RockyLinux 9
|-
| ''software stack'' || NiaEnv, CCEnv || CCEnv
|-
| ''system issue alerts'' || No || Yes
|-
| ''user quota alerts'' || No || Yes
|-
| ''error logs'' || No || Yes
|-
| ''hardware'' || 1 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM || 62 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 180GB RAM (default) 3 x CPU with 40 Intel "CascadeLake" cores at 2.5 GHz, 1TB RAM (high memory)
|}

1 Within the requested limits.

2 Limits on JupyterHub were not implementated very strictly, so you could temporarily exceed these.

3 Limits need to be requested before starting an application.

4 Only for users with a license for these products.

= Debugging Errors =

[[Image:ood-session-id.png|thumb|right|600px|Figure 12: Accessing error logs via the session card]]

If you encounter any errors while using an interactive Open OnDemand job, you can check the logs for more information. To access the logs, navigate to the '''My Interactive Sessions''' tab and find your active session. Click on the <code>output.log</code> link (see Figure. 8) to open a separate tab which displays the output of your job. This file contains the standard output and error messages generated by the job, which can help you identify any issues that may have occurred during the session. When submitting a ticket to SciNet support, please include the <code>output.log</code> file, your '''Session ID''', which is displayed as a long string of characters, e.g. ''' 8feb45fa-bc65-4846-8398-2a73c1bf8e5a''', and any other relevant information to help us assist you more effectively.

Open OnDemand Quickstart

2025-11-26T21:30:33Z

Main Page

2025-11-05T15:02:07Z

Willis2: /* System Status */

__NOTOC__
{| style="border-spacing:10px; width: 95%"
| style="padding:1em; padding-top:.1em; border:2px solid #0645ad; background-color:#f6f6f6; border-radius:7px"|

==System Status==


{|style="width:100%"
|{{Up3 | Trillium|https://docs.alliancecan.ca/wiki/Trillium_Quickstart}}
|{{Down | Niagara|Niagara_Quickstart}}
|{{Down | Teach|Teach}}
|{{Down | Rouge|Rouge}}
|-
|{{Up | OnDemand|Open_OnDemand_Quickstart}}
|{{Up3 | Scheduler|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Submitting_jobs_to_the_scheduler}}
|{{Up3 | File system|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Storage}}
|{{Down | Burst Buffer|Burst_Buffer}}
|-
|{{Up | HPSS|HPSS}}
|{{Up3 | Login Nodes|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Logging_in}}
|{{Up3 | External Network|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Logging_in}}
|{{Up | Globus |Globus}}
|-
|{{Down | Balam|Balam}}
|{{Up3 | Cvmfs|https://docs.alliancecan.ca/wiki/Standard_software_environments}}
|}

'''Tue Nov 4, 2025, 11:00 pm:''' Most of the work is done, data movers, Globus, and HPSS are back online. Remaining services will be worked on tomorrow.

'''Tue Nov 4, 2025, 8:30 am:''' Scheduled network maintenance. Trillium cluster is *not* affected.

'''Tue Oct 21, 2025, 17:30 am:''' Balam maintenance finished.

'''Tue Oct 21, 2025, 7:00 am:''' Balam maintenance day.

'''Thu Oct 15, 2025, 3:55 pm:''' Trillium inbound connections through trillium.alliancecan.ca or trillium.scinet.utoronto.ca are working again.

'''Thu Oct 15, 2025, 3:05 pm:''' Trillium is experiencing external network issues for both incoming traffic. Please try: ssh USERNAME@tri-login01.scinet.utoronto.ca in the meantime.

'''Thu Oct 06, 2025, 8:00 pm:''' HPSS is fully functional. You may submit archive jobs from trillium login nodes, datamovers and robots.

'''Thu Oct 03, 2025, 6:30 pm:''' HPSS is back online, and already accessible via alliancecan#hpss Globus endpoint. Directory tree now follows the other Alliance clusters. We're still working on job submission via Slurm

'''Thu Oct 01, 2025, 0:00 am:''' Niagara compute nodes are now unavailable for regular users. The login nodes will remain available for a while to allow a few last data transfers, although transfers from the Niagara file systems to Trillium are best done on nia-dm1.scinet.utoronto.ca.

'''Thu Oct 01, 2025, 9:30 am:''' HPSS is down for scheduled maintenance, including alliancecan#hpss Globus endpoint


[[Previous messages]]

{|style="border-spacing: 10px;width: 100%"
|valign="top" style="margin: 1em; padding:1em; padding-top:.1em; border:2px solid #000; background-color:#fff; border-radius:7px; width: 49.5%" |

== QuickStart Guides ==
* [https://docs.alliancecan.ca/wiki/Trillium_Quickstart Trillium Quickstart]
* [[Niagara Quickstart]]
* [[HPSS | HPSS archival storage]]
* [[Teach|Teach cluster]]
* [[FAQ | FAQ (frequently asked questions)]]
* [[Acknowledging SciNet]]
| valign="top" style="margin: 1em; padding:1em; padding-top:.1em; border:2px solid #000; background-color:#fff; border-radius:7px; width: 49.5%" |

== Tutorials, Manuals, etc. ==
* [https://education.scinet.utoronto.ca SciNet education material]
* [https://www.youtube.com/c/SciNetHPCattheUniversityofToronto SciNet's YouTube channel]
* [[Modules specific to Niagara|Software Modules specific to Niagara]]
* [[Modules for Mist]]
* [[Commercial software]]
* [[Burst Buffer]]
* [[SSH#SSH Keys|SSH keys]]
* [[SSH Tunneling]]
* [[Visualization]]
* [[Running Serial Jobs on Niagara]]
* [[Jupyter Hub]]
|}

Main Page

2025-11-05T15:01:57Z

Willis2: /* System Status */

__NOTOC__
{| style="border-spacing:10px; width: 95%"
| style="padding:1em; padding-top:.1em; border:2px solid #0645ad; background-color:#f6f6f6; border-radius:7px"|

==System Status==


{|style="width:100%"
|{{Up3 | Trillium|https://docs.alliancecan.ca/wiki/Trillium_Quickstart}}
|{{Down | Niagara|Niagara_Quickstart}}
|{{Down | Teach|Teach}}
|{{Down | Rouge|Rouge}}
|-
|{{Up3 | OnDemand|Open_OnDemand_Quickstart}}
|{{Up3 | Scheduler|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Submitting_jobs_to_the_scheduler}}
|{{Up3 | File system|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Storage}}
|{{Down | Burst Buffer|Burst_Buffer}}
|-
|{{Up | HPSS|HPSS}}
|{{Up3 | Login Nodes|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Logging_in}}
|{{Up3 | External Network|https://docs.alliancecan.ca/wiki/Trillium_Quickstart#Logging_in}}
|{{Up | Globus |Globus}}
|-
|{{Down | Balam|Balam}}
|{{Up3 | Cvmfs|https://docs.alliancecan.ca/wiki/Standard_software_environments}}
|}

'''Tue Nov 4, 2025, 11:00 pm:''' Most of the work is done, data movers, Globus, and HPSS are back online. Remaining services will be worked on tomorrow.

'''Tue Nov 4, 2025, 8:30 am:''' Scheduled network maintenance. Trillium cluster is *not* affected.

'''Tue Oct 21, 2025, 17:30 am:''' Balam maintenance finished.

'''Tue Oct 21, 2025, 7:00 am:''' Balam maintenance day.

'''Thu Oct 15, 2025, 3:55 pm:''' Trillium inbound connections through trillium.alliancecan.ca or trillium.scinet.utoronto.ca are working again.

'''Thu Oct 15, 2025, 3:05 pm:''' Trillium is experiencing external network issues for both incoming traffic. Please try: ssh USERNAME@tri-login01.scinet.utoronto.ca in the meantime.

'''Thu Oct 06, 2025, 8:00 pm:''' HPSS is fully functional. You may submit archive jobs from trillium login nodes, datamovers and robots.

'''Thu Oct 03, 2025, 6:30 pm:''' HPSS is back online, and already accessible via alliancecan#hpss Globus endpoint. Directory tree now follows the other Alliance clusters. We're still working on job submission via Slurm

'''Thu Oct 01, 2025, 0:00 am:''' Niagara compute nodes are now unavailable for regular users. The login nodes will remain available for a while to allow a few last data transfers, although transfers from the Niagara file systems to Trillium are best done on nia-dm1.scinet.utoronto.ca.

'''Thu Oct 01, 2025, 9:30 am:''' HPSS is down for scheduled maintenance, including alliancecan#hpss Globus endpoint


[[Previous messages]]

{|style="border-spacing: 10px;width: 100%"
|valign="top" style="margin: 1em; padding:1em; padding-top:.1em; border:2px solid #000; background-color:#fff; border-radius:7px; width: 49.5%" |

== QuickStart Guides ==
* [https://docs.alliancecan.ca/wiki/Trillium_Quickstart Trillium Quickstart]
* [[Niagara Quickstart]]
* [[HPSS | HPSS archival storage]]
* [[Teach|Teach cluster]]
* [[FAQ | FAQ (frequently asked questions)]]
* [[Acknowledging SciNet]]
| valign="top" style="margin: 1em; padding:1em; padding-top:.1em; border:2px solid #000; background-color:#fff; border-radius:7px; width: 49.5%" |

== Tutorials, Manuals, etc. ==
* [https://education.scinet.utoronto.ca SciNet education material]
* [https://www.youtube.com/c/SciNetHPCattheUniversityofToronto SciNet's YouTube channel]
* [[Modules specific to Niagara|Software Modules specific to Niagara]]
* [[Modules for Mist]]
* [[Commercial software]]
* [[Burst Buffer]]
* [[SSH#SSH Keys|SSH keys]]
* [[SSH Tunneling]]
* [[Visualization]]
* [[Running Serial Jobs on Niagara]]
* [[Jupyter Hub]]
|}

Open OnDemand Quickstart

2025-11-04T16:30:27Z

Willis2: /* Differences compared to the Jupyter Hub */

Open OnDemand Quickstart

2025-10-31T13:54:46Z

Willis2: /* Installed Applications */

Open OnDemand Quickstart

2025-10-31T13:52:34Z

Willis2: /* Installed Applications */