| Both sides previous revision Previous revision Next revision | Previous revision |
| technical:recipes:telemac [2021-01-29 09:37] – [Build TELEMAC] frey | technical:recipes:telemac [2021-04-11 10:29] (current) – [Compilation] anita |
|---|
| |
| <WRAP center round important 80%> | <WRAP center round important 80%> |
| If the installation is not meant to be available to all workgroup users (e.g. installed to ''$HOME'' rather than ''$WORKDIR'') the package definition should be in ''~/.valet/telemac.vpkg_yaml''. | If the installation is not meant to be available to all workgroup users (e.g. installed to ''$HOME'' rather than ''$WORKDIR'') the VALET package definition should be in ''~/.valet/telemac.vpkg_yaml''. |
| </WRAP> | </WRAP> |
| |
| * Same MPI parameters as in step 1 | * Same MPI parameters as in step 1 |
| |
| We set up a test job directory called ''$WORKDIR/sw/telemac/example'' and our the steering file, input files, and source code in this directory. The job will use a working directory //inside// our test job directory for all of the intermediate files during the run. Also the ''standard'' partition is specified as the queue for the batch steps (those that can run on compute nodes). Remember jobs can be preempted when using the ''standard'' partition, so you may want to use your workgroup partition for longer running jobs. | We set up a test job directory called ''$WORKDIR/sw/telemac/example'' with our steering file, input files, and source code in this directory. The job will use a working directory //inside// our test job directory for all of the intermediate files during the run. Also the ''standard'' partition is specified as the queue for the batch steps (those that can run on compute nodes). Remember jobs can be preempted when using the ''standard'' partition, so you may want to use your workgroup partition for longer running jobs. |
| |
| ===== Partitioning ===== | ===== Partitioning ===== |
| ===== Compilation ===== | ===== Compilation ===== |
| |
| Once the problem is partitioned, the executable can be built. This step should not be run on compute nodes since they lack a base development environment in the OS((This step could be run on a node in the **devel** partition on Caviness. DARWIN nodes all have a full base development environment in the OS, so the jobs can be run in a single step -- see the "Single-step runs" section detailing that mode of operation.)). | Once the problem is partitioned, the executable can be built. This step should not be run on compute nodes since they lack a base development environment in the OS((This step could be run on a node in the **devel** partition on Caviness. DARWIN nodes all have a full base development environment in the OS, so the jobs can be run in a single step -- see the "[[technical:recipes:telemac#single-step-runs|Single-step runs]]" section detailing that mode of operation.)). |
| |
| <code bash> | <code bash> |
| $ vpkg_require telemac/v8p2r0:batch | $ vpkg_require telemac/v8p2r0:batch |
| (/work/workgroup/sw/telemac/v8p2r0) $ runcode.py \ | (/work/workgroup/sw/telemac/v8p2r0) $ runcode.py \ |
| --use-link --run --workdirectory $(pwd)/test_run \ | --use-link --merge --workdirectory $(pwd)/test_run \ |
| --jobname telemac_test-merge \ | --jobname telemac_test-merge \ |
| --ncsize 2 \ | --ncsize 2 \ |