hpc:how_to_use_openondemand
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
hpc:how_to_use_openondemand [2023/12/12 13:35] – [FAQ] Adrien Albert | hpc:how_to_use_openondemand [2024/06/27 09:21] (current) – [How To connect] Yann Sagon | ||
---|---|---|---|
Line 33: | Line 33: | ||
First each cluster will have his own OpenOnDemand instance. To allow all users (unige, extern and outsider users) to connect to OpenOnDemand, | First each cluster will have his own OpenOnDemand instance. To allow all users (unige, extern and outsider users) to connect to OpenOnDemand, | ||
- | Ask to get access to the page: | + | You MUST use the same email bound to your HPC account. It means: |
- | https:// | + | |
- | + | ||
- | You MUST use the same bind email to the unige account. It means: | + | |
* Unige email (@unige.ch) for unige members (Student/ | * Unige email (@unige.ch) for unige members (Student/ | ||
Line 43: | Line 40: | ||
If not, you will not be able to connect through OpenOnDemand web Interface | If not, you will not be able to connect through OpenOnDemand web Interface | ||
- | To access | + | Access |
+ | |||
+ | Access to Bamboo OpenOnDemand web instance: https:// | ||
** :!: Yggdrasil OpenOndemand: | ** :!: Yggdrasil OpenOndemand: | ||
====== Tabs ====== | ====== Tabs ====== | ||
Line 114: | Line 114: | ||
+ | ===== Launching applications ===== | ||
+ | This documentation has been taken from https:// | ||
+ | |||
+ | After choosing from the available applications, | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | Typically, when requesting resources, you will be given the option to choose number of cores, maximum running time and memory per core. If multiple versions of the application are available, this may be offered too. | ||
+ | |||
+ | For many use-cases, including non-computational visualisation, | ||
+ | |||
+ | There is also the option to request an email to notify you when the job starts, in the case of sessions which require longer queueing time. | ||
+ | |||
+ | For graphical applications, | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | <WRAP center round info 60%> | ||
+ | Note also the **View only** link. OnDemand sessions are secure and confined only to you. However, you have the option to share a **read-only view** of your session for purposes of monitoring progress of a job with a collaborator or to demonstrate work to a colleague. | ||
+ | </ | ||
+ | |||
+ | |||
+ | ==== Session persistence ==== | ||
+ | A session remains active for the time period you have requested it for. If you have finished your work, then we recommend that you close the application cleanly, followed by clicking Delete next to your session on My Interactive Sessions page. This will release resources back to the cluster. | ||
+ | |||
+ | If you are running a graphical application which uses a desktop environment, | ||
+ | |||
+ | Closing a browser tab while running a web service session such as Jupyter | ||
+ | {{: |
hpc/how_to_use_openondemand.1702388133.txt.gz · Last modified: 2023/12/12 13:35 by Adrien Albert