Skip to content

Commit

Permalink
Replace old "trd-project" references with "/nird/projects" (#22)
Browse files Browse the repository at this point in the history
  • Loading branch information
TomasTorsvik committed Jan 4, 2024
1 parent 8eeb0c3 commit 78957dc
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 11 deletions.
4 changes: 2 additions & 2 deletions access/download_input.rst
Expand Up @@ -52,14 +52,14 @@ Advanced: Updating NorESM source inputdata

The input data is currently physically stored on NIRD under ::

/trd-project3/NS9560K/www/inputdata
/nird/projects/NS9560K/www/inputdata

Project group members can create new folders and files, also inside existing subfolders.
However, most existing files are write protected.

If existing files need to be updated, please contact the owners to update them,
or they can make the files temporarily writable by executing the script ::

/trd-project3/NS9560K/www/inputdata_permissions.sh
/nird/projects/NS9560K/www/inputdata_permissions.sh

after commenting in/out the first or second line.
6 changes: 3 additions & 3 deletions configurations/cmip6_compsets.rst
Expand Up @@ -155,7 +155,7 @@ and the long name for ``N1850frc2`` is ::
Restart files for piControl
Before submitting the job, please remeber to copy the restart and rpointer files to the run directory, e.g. for TEST_NorESM2-MM_piControl on BETZY ::

cp /trd-project3/NS9560K/noresm/cases/N1850_f09_tn14_20190913/rest/1200-01-01-00000/* /cluster/projects/<project>/<username>/noresm/TEST_NorESM2-MM_piControl/run/
cp /nird/projects/NS9560K/noresm/cases/N1850_f09_tn14_20190913/rest/1200-01-01-00000/* /cluster/projects/<project>/<username>/noresm/TEST_NorESM2-MM_piControl/run/
gunzip /cluster/projects/<project>/<username>/noresm/TEST_NorESM2-MM_piControl/run/*.gz
Overview of piControl case names, detailed setup (machine settings, node settings etc.), raw output and restart files:
Expand Down Expand Up @@ -216,7 +216,7 @@ and for ``NHISTfrc2`` is ::
Restart files for historical experiments
Before submitting the job, please remeber to copy the restart and rpointer files to the run directory, e.g. for TEST_NorESM2-LM_historical on BETZY ::
cp /trd-project3/NS9560K/noresm/cases/N1850_f19_tn14_11062019/rest/1600-01-01-00000/* /cluster/projects/<project>/<username>/noresm/TEST_NorESM2-LM_historical/run/
cp /nird/projects/NS9560K/noresm/cases/N1850_f19_tn14_11062019/rest/1600-01-01-00000/* /cluster/projects/<project>/<username>/noresm/TEST_NorESM2-LM_historical/run/
gunzip /cluster/projects/<project>/<username>/noresm/TEST_NorESM2-LM_historical/run/*.gz

Overview of historical case names, members, detailed setup (machine settings, node settings etc.), raw output and restart files:
Expand Down Expand Up @@ -279,7 +279,7 @@ and for ``NSSP585frc2`` is ::
Restart files for NSSP585 experiments
Before submitting the job, please remeber to copy the restart and rpointer files to the run directory, e.g. for TEST_NorESM2-LM_ssp585 on BETZY ::

cp /trd-project3/NS9560K/noresm/cases/NHIST_f19_tn14_20190710/rest/2015-01-01-00000/* /cluster/projects/<project>/<username>/noresm/TEST_NorESM2-LM_ssp585/run/
cp /nird/projects/NS9560K/noresm/cases/NHIST_f19_tn14_20190710/rest/2015-01-01-00000/* /cluster/projects/<project>/<username>/noresm/TEST_NorESM2-LM_ssp585/run/
gunzip /cluster/projects/<project>/<username>/noresm/TEST_NorESM2-LM_ssp585/run/*.gz

Overview of scenario experiment case names, members, detailed setup (machine settings, node settings etc.), raw output and restart files:
Expand Down
12 changes: 6 additions & 6 deletions diagnostics/diag_run.rst
Expand Up @@ -485,7 +485,7 @@ There are two alternatives to run the tool on Betzy, either as an interactive (f

The main purpose to run the tool on Betzy is to get a quick diagnostic of model output when the model is still on-the-fly, but already has some intermediate output been short-term archived to **/cluster/work/users/<username>/archive** (Refer to :ref:`archive_output`).

Since the mounted NIRD project disks ``/trd-project*/xx`` are not accessible from the compute nodes, the ``-i``, ``-o`` have to point to ``/cluster/work/users/<username>/xxx``, with an execption for the ``-w`` option. See explanations and examples in the following.
Since the mounted NIRD project disks ``/nird/projects/NSxxxxK`` are not accessible from the compute nodes, the ``-i``, ``-o`` have to point to ``/cluster/work/users/<username>/<workdir>``, with an execption for the ``-w`` option. See explanations and examples in the following.

As interactive job
------------------
Expand Down Expand Up @@ -530,27 +530,27 @@ The CPU account is set to default as nn2345k if not prescribed. The CPU hours is

$ ./diag_srun -m blom -c NOICPLHISTOC_f09_tn14_cpldiags -s 1 -e 20 -i /cluster/work/users/<username>/archive -o /cluster/work/users/<username>/diagnostics/out -w /cluster/work/users/<username>/diagnostics/www

The above settings for ``-i``, ``-o`` and ``-w`` are default values if they are not prescribed. As the mounted NIRD disks ``/trd-project**`` are not accessible from the compute nodes, the ``-i`` and ``-o`` options have to be set to ``/cluster**``. For the ``-w`` option, see the next example.
The above settings for ``-i``, ``-o`` and ``-w`` are default values if they are not prescribed. As the mounted NIRD disks ``/nird/projects`` are not accessible from the compute nodes, the ``-i`` and ``-o`` options have to be set to ``/cluster**``. For the ``-w`` option, see the next example.

4. Set input data, output data on Betzy, and webpage path on NIRD ::

$ ./diag_srun -m blom -c NOICPLHISTOC_f09_tn14_cpldiags -s 1 -e 20 -w /trd-project1/NS2345K/www/diagnostics/noresm/<username> --account=nn2345k --time=0-00:59:00
$ ./diag_srun -m blom -c NOICPLHISTOC_f09_tn14_cpldiags -s 1 -e 20 -w /nird/projects/NS2345K/www/diagnostics/noresm/<username> --account=nn2345k --time=0-00:59:00

The created webpage will saved to NIRD. The webpage path specificed by ``-w`` will temporary set to the defaut location under ``/cluster/work/users/<username>/diagnostics/www``, and will ``rsync`` to NIRD after the diagnostics job is finished.

5. Remove source webpage files from Betzy after transferred to NIRD ::

$ ./diag_srun -m blom -c NOICPLHISTOC_f09_tn14_cpldiags -s 1 -e 20 -w /trd-project1/NS2345K/www/diagnostics/noresm/<username>/ --remove-source-files-flag=true
$ ./diag_srun -m blom -c NOICPLHISTOC_f09_tn14_cpldiags -s 1 -e 20 -w /nird/projects/NS2345K/www/diagnostics/noresm/<username>/ --remove-source-files-flag=true

Options to set if temporary webpage under ``/cluster`` as described above will be removed after they are transferred to NIRD (only valid if ``-w`` option is set to ``/trd-project*`` area)
Options to set if temporary webpage under ``/cluster`` as described above will be removed after they are transferred to NIRD (only valid if ``-w`` option is set to ``/nird/projects`` area)

See more help: ::

/cluster/shared/noresm/diagnostics/noresm/bin/diag_run -h
/cluster/shared/noresm/diagnostics/noresm/bin/diag_srun -h

.. note::
The mounted NIRD project area ``/trd-project*`` are not available on the HPC computing nodes. Therefore, the ``-i``, ``-o`` can only be set to locations under /cluster/work/users/<username>. The ``-w`` option can be set to ``/trd-project*`` area to facility the browsing the webpage-based diagnostics. It is actually set to ``/cluster`` during runtime, but transfer the created webpages to NIRD automatically after the diagnostic is finished.
The mounted NIRD project area ``/nird/projects`` are not available on the HPC computing nodes. Therefore, the ``-i``, ``-o`` can only be set to locations under /cluster/work/users/<username>. The ``-w`` option can be set to ``/nird/projects`` area to facility the browsing the webpage-based diagnostics. It is actually set to ``/cluster`` during runtime, but transfer the created webpages to NIRD automatically after the diagnostic is finished.

--------------------------------------------------------------------------------

Expand Down

0 comments on commit 78957dc

Please sign in to comment.