further vibing #2
This commit is contained in:
@@ -14,7 +14,7 @@ All PSI users can ask for access to the Merlin7 cluster. Access to Merlin7 is re
|
||||
|
||||
Requesting **Merlin7** access *has to be done* using the **[Request Linux Group Membership](https://psi.service-now.com/psisp?id=psi_new_sc_cat_item&sys_id=84f2c0c81b04f110679febd9bb4bcbb1)** form, available in [PSI's central Service Catalog](https://psi.service-now.com/psisp) on Service Now.
|
||||
|
||||
![Example: Requesting access to Merlin7]({{ "/images/Access/01-request-merlin7-membership.png" }})
|
||||
|
||||
|
||||
Mandatory fields you need to fill:
|
||||
* **`Order Access for user:`** Defaults to the logged in user. However, requesting access for another user it's also possible.
|
||||
|
||||
@@ -70,7 +70,7 @@ Supervisors should inform new users which extra groups are needed for their proj
|
||||
|
||||
Requesting membership for a specific Unix group *has to be done* with the corresponding **[Request Linux Group Membership](https://psi.service-now.com/psisp?id=psi_new_sc_cat_item&sys_id=84f2c0c81b04f110679febd9bb4bcbb1)** form, available in the [PSI Service Now Service Catalog](https://psi.service-now.com/psisp).
|
||||
|
||||
![Example: Requesting Unix Group membership]({{ "/images/Access/01-request-unx-group-membership.png" }})
|
||||
|
||||
|
||||
Once submitted, the responsible of the Unix group has to approve the request.
|
||||
|
||||
|
||||
@@ -15,11 +15,11 @@ If they are missing, you can install them using the Software Kiosk icon on the D
|
||||
|
||||
2. *[Optional]* Enable ``xterm`` to have similar mouse behavour as in Linux:
|
||||
|
||||
![Enable 'xterm']({{ "/images/PuTTY/Putty_Mouse_XTerm.png" }})
|
||||
|
||||
|
||||
3. Create session to a Merlin login node and *Open*:
|
||||
|
||||
![Create Merlin Session]({{ "/images/PuTTY/Putty_Session.png" }})
|
||||
|
||||
|
||||
|
||||
## SSH with PuTTY with X11 Forwarding
|
||||
@@ -37,4 +37,4 @@ using the Software Kiosk icon (should be located on the Desktop).
|
||||
|
||||
2. Enable X11 Forwarding in your SSH client. In example, for Putty:
|
||||
|
||||
![Enable X11 Forwarding in Putty]({{ "/images/PuTTY/Putty_X11_Forwarding.png" }})
|
||||
|
||||
|
||||
@@ -83,12 +83,12 @@ The NoMachine client can be downloaded from [NoMachine's download page](https://
|
||||
- **Port**: Enter `4000`.
|
||||
- **Protocol**: Select `NX`.
|
||||
|
||||
![Create New NoMachine Connection]({{ "/images/NoMachine/screen_nx_address.png" }})
|
||||
|
||||
|
||||
- On the **Configuration** tab ensure:
|
||||
- **Authentication**: Select `Use password authentication`.
|
||||
|
||||
![Create New NoMachine Connection]({{ "/images/NoMachine/screen_nx_configuration.png" }})
|
||||
|
||||
|
||||
- Click the **Add** button to finish creating the new connection.
|
||||
|
||||
@@ -96,7 +96,7 @@ The NoMachine client can be downloaded from [NoMachine's download page](https://
|
||||
|
||||
When prompted, use your PSI credentials to authenticate.
|
||||
|
||||
![Create New NoMachine Connection]({{ "/images/NoMachine/screen_nx_auth.png" }})
|
||||
|
||||
|
||||
## Managing Sessions
|
||||
|
||||
@@ -120,7 +120,7 @@ Access to the login node desktops must be initiated through the `merlin7-nx.psi.
|
||||
When connecting to the `merlin7-nx.psi.ch` front-end, a new session automatically opens if no existing session is found. Users can manage their sessions as follows:
|
||||
|
||||
- **Reconnect to an Existing Session**: If you have an active session, you can reconnect to it by selecting the appropriate icon in the NoMachine client interface. This allows you to resume work without losing any progress.
|
||||
![Open an existing Session]({{ "/images/NoMachine/screen_nx_single_session.png" }})
|
||||
|
||||
- **Create a Second Session**: If you require a separate session, you can select the **`New Desktop`** button. This option creates a second session on another login node, provided the node is available and operational.
|
||||
|
||||
### Session Management Considerations
|
||||
|
||||
@@ -30,9 +30,9 @@ The different steps and settings required to make it work are that following:
|
||||
|
||||
1. Open the RSM Configuration service in Windows for the ANSYS release you want to configure.
|
||||
2. Right-click the **HPC Resources** icon followed by **Add HPC Resource...**
|
||||
![Adding a new HPC Resource]({{ "/images/ANSYS/merlin7/rsm-1-add_hpc_resource.png" }})
|
||||
|
||||
3. In the **HPC Resource** tab, fill up the corresponding fields as follows:
|
||||
![HPC Resource]({{"/images/ANSYS/merlin7/rsm-2-add_cluster.png"}})
|
||||
|
||||
* **"Name"**: Add here the preffered name for the cluster. For example: `Merlin7 cluster`
|
||||
* **"HPC Type"**: Select `SLURM`
|
||||
* **"Submit host"**: `service03.merlin7.psi.ch`
|
||||
@@ -43,22 +43,22 @@ The different steps and settings required to make it work are that following:
|
||||
* Select **"Able to directly submit and monitor HPC jobs"**.
|
||||
* **"Apply"** changes.
|
||||
4. In the **"File Management"** tab, fill up the corresponding fields as follows:
|
||||
![File Management]({{"/images/ANSYS/merlin7/rsm-3-add_scratch_info.png"}})
|
||||
|
||||
* Select **"RSM internal file transfer mechanism"** and add **`/data/scratch/shared`** as the **"Staging directory path on Cluster"**
|
||||
* Select **"Scratch directory local to the execution node(s)"** and add **`/scratch`** as the **HPC scratch directory**.
|
||||
* **Never check** the option "Keep job files in the staging directory when job is complete" if the previous
|
||||
option "Scratch directory local to the execution node(s)" was set.
|
||||
* **"Apply"** changes.
|
||||
5. In the **"Queues"** tab, use the left button to auto-discover partitions
|
||||
![Queues]({{"/images/ANSYS/merlin7/rsm-4-get_slurm_queues.png"}})
|
||||
|
||||
* If no authentication method was configured before, an authentication window will appear. Use your
|
||||
PSI account to authenticate. Notice that the **`PSICH\`** prefix **must not be added**.
|
||||
![Authenticating]({{"/images/ANSYS/merlin7/rsm-5-authenticating.png"}})
|
||||
|
||||
* From the partition list, select the ones you want to typically use.
|
||||
* In general, standard Merlin users must use **`hourly`**, **`daily`** and **`general`** only.
|
||||
* Other partitions are reserved for allowed users only.
|
||||
* **"Apply"** changes.
|
||||
![Select partitions]({{"/images/ANSYS/merlin7/rsm-6-selected-partitions.png"}})
|
||||
|
||||
6. *[Optional]* You can perform a test by submitting a test job on each partition by clicking on the **Submit** button
|
||||
for each selected partition.
|
||||
|
||||
|
||||
@@ -84,12 +84,12 @@ For further information, please visit the **[ANSYS RSM](ansys-rsm.md)** section.
|
||||
|
||||
### ANSYS Fluent
|
||||
|
||||
For further information, please visit the **[ANSYS RSM](ansys-fluent.md)** section.
|
||||
ANSYS Fluent is not currently documented for Merlin7. Please refer to the [Merlin6 documentation](../merlin6/software-support/ansys-fluent.md) for information about ANSYS Fluent on Merlin6.
|
||||
|
||||
### ANSYS CFX
|
||||
|
||||
For further information, please visit the **[ANSYS RSM](ansys-cfx.md)** section.
|
||||
ANSYS CFX is not currently documented for Merlin7. Please refer to the [Merlin6 documentation](../merlin6/software-support/ansys-cfx.md) for information about ANSYS CFX on Merlin6.
|
||||
|
||||
### ANSYS MAPDL
|
||||
|
||||
For further information, please visit the **[ANSYS RSM](ansys-mapdl.md)** section.
|
||||
ANSYS MAPDL is not currently documented for Merlin7. Please refer to the [Merlin6 documentation](../merlin6/software-support/ansys-mapdl.md) for information about ANSYS MAPDL on Merlin6.
|
||||
|
||||
@@ -70,7 +70,7 @@ Before starting the migration, make sure you:
|
||||
|
||||
* are **registered on Merlin7**.
|
||||
|
||||
* If not yet registered, please do so following [these instructions](../merlin7/request-account.html)
|
||||
* If not yet registered, please do so following [these instructions](../01-Quick-Start-Guide/requesting-accounts.md)
|
||||
|
||||
* **have cleaned up your data to reduce migration time and space usage**.
|
||||
* **For the user data migration**, ensure your total usage on Merlin6 (`/psi/home`+`/data/user`) is **well below the 1 TB quota** (use the `merlin_quotas` command). Remember:
|
||||
|
||||
Reference in New Issue
Block a user