Replace cheyenne references with derecho throughout#3838
Open
slevis-lmwg wants to merge 6 commits intoESCOMP:b4b-devfrom
Open
Replace cheyenne references with derecho throughout#3838slevis-lmwg wants to merge 6 commits intoESCOMP:b4b-devfrom
slevis-lmwg wants to merge 6 commits intoESCOMP:b4b-devfrom
Conversation
slevis-lmwg
changed the title
slevis-lmwg
added
documentation
slevis-lmwg
added this to
CTSM: Upcoming tags, CLM documentation and LMWG: Sprint Planning Board
github-project-automation
bot
moved this to Ready to start (or start again)
in CTSM: Upcoming tags
slevis-lmwg
moved this from Ready to start (or start again)
to In progress - b4b-dev
in CTSM: Upcoming tags
slevis-lmwg
commented
Mar 24, 2026
| Note, that when running with ``PTS_MODE`` the number of processors is automatically set to one. When running a single grid point you can only use a single processor. You might also want to set the ``env_build.xml`` variable: ``MPILIB=mpi-serial`` to ``TRUE`` so that you can also run interactively without having to use MPI to start up your job. | ||
|
|
||
| On many machines, batch queues have a minimum number of nodes or processors that can be used. On these machines you may have to change the queue and possibly the time-limits of the job, to get it to run in the batch queue. On the NCAR machine, cheyenne, this is done for you automatically, and the "share" or "caldera" queue is used for such single-processor simulations. For single point mode you also may want to consider using a smaller workstation or cluster, rather than a super-computer, because you can't take advantage of the multi-processing power of the super-computer anyway. | ||
| On many machines, batch queues have a minimum number of nodes or processors that can be used. On these machines you may have to change the queue and possibly the time-limits of the job, to get it to run in the batch queue. On the NCAR machine, derecho, this is done for you automatically, and the "xxx" queue is used for such single-processor simulations. For single point mode you also may want to consider using a smaller workstation or cluster, rather than a super-computer, because you can't take advantage of the multi-processing power of the super-computer anyway. |
Contributor
Author
There was a problem hiding this comment.
@ekluzek here I changed cheyenne to derecho, but what should I put in place of "xxx" and/or should parts of this be removed altogether?
slevis-lmwg
commented
Mar 24, 2026
| mpiexec_mpt ./wrf.exe | ||
|
|
||
| (See :numref:`runtime-environment-variables` for a description of the need to set ``MPI_TYPE_DEPTH`` on ``Cheyenne``.) | ||
| (See :numref:`runtime-environment-variables` for a description of the need to set ``MPI_TYPE_DEPTH`` on ``derecho``.) |
Contributor
Author
There was a problem hiding this comment.
@ekluzek here I changed cheyenne to derecho, but does the comment still apply?
slevis-lmwg
commented
Mar 24, 2026
| ======================================================== | ||
|
|
||
| With the MPT MPI library (which is the default MPI library on NCAR's cheyenne machine), it is important to set the environment variable ``MPI_TYPE_DEPTH`` to 16 when running CTSM (this setting is required by the Parallel IO library). Typically you should set this variable in your job submission script, using either: | ||
| With the MPT MPI library (which is the default MPI library on NCAR's derecho machine), it is important to set the environment variable ``MPI_TYPE_DEPTH`` to 16 when running CTSM (this setting is required by the Parallel IO library). Typically you should set this variable in your job submission script, using either: |
slevis-lmwg
commented
Mar 24, 2026
| }, | ||
| ), | ||
| "hobart": MachineDefaults( | ||
| "thorodin": MachineDefaults( |
Contributor
Author
There was a problem hiding this comment.
@ekluzek as far as I know, hobart is unavailable and thorodin is available, but does it make sense that I replaced the former with the latter here?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of changes
Specific notes
Contributors other than yourself, if any:
CTSM Issues Fixed (include github issue #):
Fixes #2223
Are answers expected to change (and if so in what way)?
No
Any User Interface Changes (namelist or namelist defaults changes)?
No
Does this create a need to change or add documentation? Did you do so?
That's the main focus of this PR
Testing performed, if any:
Changes here affect python files, so I ran these tests before opening the PR (see #2223) and will likely rerun before merging to b4b-dev: