Skip to content
Snippets Groups Projects
Commit 903f97c0 authored by Natalie Breidenbach's avatar Natalie Breidenbach
Browse files

Update custom_easy_build_environment.md

parent 3d647f71
No related branches found
No related tags found
2 merge requests!938Automated merge from preview to main,!936Update to Five-Cluster-Operation
......@@ -54,16 +54,17 @@ once:
```console
marie@login$ ws_allocate EasyBuild 50
marie@login$ ws_list | grep 'directory.*EasyBuild'
workspace directory : /horse/ws/1/marie-EasyBuild
workspace directory : /data/horse/ws/1/marie-EasyBuild
```
**Step 2:** Allocate nodes. You can do this with interactive jobs (see the example below) and/or
put commands in a batch file and source it. The latter is recommended for non-interactive jobs,
using the command `sbatch` instead of `srun`. For the sake of illustration, we use an
interactive job as an example. Depending on the partitions that you want the module to be usable on
later, you need to select nodes with the same architecture. Thus, use nodes from partition `ml` for
building, if you want to use the module on nodes of that partition. In this example, we assume
that we want to use the module on nodes with x86 architecture and thus, we use Haswell nodes.
later, you need to select nodes with the same architecture. Thus, use nodes from cluster `power` for
building, if you want to use the module on nodes of that cluster. ~~In this example, we assume
that we want to use the module on nodes with x86 architecture and thus, we use Haswell nodes.~~
```console
marie@login$ srun --nodes=1 --cpus-per-task=4 --time=08:00:00 --pty /bin/bash -l
......@@ -76,8 +77,11 @@ marie@login$ srun --nodes=1 --cpus-per-task=4 --time=08:00:00 --pty /bin/bash -l
**Step 3:** Specify the workspace. The rest of the guide is based on it. Please create an
environment variable called `WORKSPACE` with the path to your workspace:
_The module environments /hiera, /scs5, /classic and /ml originated from the taurus system are momentarily under construction. The script will be updated after completion of the redesign accordingly_
```console
marie@compute$ export WORKSPACE=/horse/ws/1/marie-EasyBuild #see output of ws_list above
marie@compute$ export WORKSPACE=/data/horse/ws/1/marie-EasyBuild #see output of ws_list above
```
**Step 4:** Load the correct module environment `modenv` according to your current or target
......@@ -188,7 +192,7 @@ marie@compute$ export LMOD_IGNORE_CACHE=1
**OR** directly the path from step 1:
```console
marie@compute$ module use "/horse/ws/1/marie-EasyBuild/easybuild/modules/all"
marie@compute$ module use "/data/horse/ws/1/marie-EasyBuild/easybuild/modules/all"
marie@compute$ export LMOD_IGNORE_CACHE=1
```
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment