more information regarding PLUMBER 2 simulations using the ./runtower… #3305
Conversation
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
TeaganKing
reviewed
Jul 7, 2025
There was a problem hiding this comment.
Thanks so much for putting this together, @ijaguirre !
I have a few clarifying questions for you, and am happy to address the other changes myself if they seem reasonable to you! If you could just answer a few of the questions and thumbs up the comments if you agree with them, or of course share other thoughts, I'm happy to wrap this up!
| Currently, the ``run_tower`` tool supports running CTSM at PLUMBER 2 sites using forcing data from the PLUMBER2 projects. Detailed site information is provided in `Ukkola et al. 2022 <https://doi.org/10.5194/essd-14-449-2022>`_ , and the description of the experiment and its results is provided in `Abramowitz et al. 2024 <https://doi.org/10.5194/bg-21-5517-2024>`_. | ||
| Information on the specific sites can be found `here <https://researchdata.edu.au/plumber2-forcing-evaluation-surface-models/1656048>`_. | ||
|
|
||
| Currently supported PLUMBER Sites can be found by running ``run_tower --help``. Keep in mind that the experiment was designed to run 170 sites; however, they identified different issues with the sites, and most of the article only uses 156 sites. |
There was a problem hiding this comment.
Thanks for including this information and the citations!
| A few notes regarding the PLUMBER 2 simulations using the ``run_tower`` tool: | ||
|
|
||
|
|
||
| 1) By default, all simulations (e.g., ad, post-ad, transient) are designed to run for 1 hour of wall clock time. For the spin-up simulations, it is recommended to extend the time to match the length of the simulations. |
There was a problem hiding this comment.
Can we make just one recommended spin-up configurations section? Eg, this could look like the section below & replace 1 and 2.
Recommended spin-up configurations
- By default, all simulations (e.g., ad, post-ad, transient) are designed to run for 1 hour of wall clock time. For the spin-up simulations, we recommend extending the time to match the length of the simulations.
- By default, the initial period of the simulations differs for the spin-up (e.g., ad and post-ad) and transient simulations. It is important to revisit for each site the best period to use for the spin-up simulations.
- Additionally, we recommend spinning up with the
no_leapcalendar to avoid issues with Feb 28th and 29th on leap years. - Lastly, we recommend setting
dtlimit=50in the spin-up simulation of the user_nl_datm_strems files.
|
|
||
| 1) By default, all simulations (e.g., ad, post-ad, transient) are designed to run for 1 hour of wall clock time. For the spin-up simulations, it is recommended to extend the time to match the length of the simulations. | ||
| 2) By default, the initial period of the simulations differs for the spin-up (e.g., ad and post-ad) and transient simulations. It is important to revisit for each site the best period to use for the spin-up simulations. It is suggested to run the spin-up simulations using the no_leap calendar to avoid issues with Feb 28/29 on leap years. It is also recommended to set a dtlimit value of 50 in the spin-up simulation of the user_nl_datm_strems files. | ||
| 3) By default, the tools call for surfdata files in a default location. These might not be available for all sites. Users can create their own surfdata files, using tools/site_and_regional/plumber2_usermods. |
There was a problem hiding this comment.
tools/site_and_regional/plumber2_usermods and other files should be formatted to look like code
| 1) By default, all simulations (e.g., ad, post-ad, transient) are designed to run for 1 hour of wall clock time. For the spin-up simulations, it is recommended to extend the time to match the length of the simulations. | ||
| 2) By default, the initial period of the simulations differs for the spin-up (e.g., ad and post-ad) and transient simulations. It is important to revisit for each site the best period to use for the spin-up simulations. It is suggested to run the spin-up simulations using the no_leap calendar to avoid issues with Feb 28/29 on leap years. It is also recommended to set a dtlimit value of 50 in the spin-up simulation of the user_nl_datm_strems files. | ||
| 3) By default, the tools call for surfdata files in a default location. These might not be available for all sites. Users can create their own surfdata files, using tools/site_and_regional/plumber2_usermods. | ||
| 4) It is suggested to use the flags-- setup-only to examine how the site files are being configured before running the simulations. |
| 3) By default, the tools call for surfdata files in a default location. These might not be available for all sites. Users can create their own surfdata files, using tools/site_and_regional/plumber2_usermods. | ||
| 4) It is suggested to use the flags-- setup-only to examine how the site files are being configured before running the simulations. | ||
| 5) It is suggested to add ``echo "baseflow_scalar = 0" >> user_nl_clm`` to the user_nl_clm file to avoid issues with the baseflow in the wetland sites. | ||
| 6) Currently, the tool is designed only for cases with active biochemistry. For SP simulations, it is recommended to use the user mods directory ``/CTSM/cime_config/usermods_dirs/clm/PLUMBER2/${site}``, which contains the necessary modifications to run the simulations in SP mode. |
There was a problem hiding this comment.
Did you mean to specify a different directory here? I think this is the default directory?
| 2) By default, the initial period of the simulations differs for the spin-up (e.g., ad and post-ad) and transient simulations. It is important to revisit for each site the best period to use for the spin-up simulations. It is suggested to run the spin-up simulations using the no_leap calendar to avoid issues with Feb 28/29 on leap years. It is also recommended to set a dtlimit value of 50 in the spin-up simulation of the user_nl_datm_strems files. | ||
| 3) By default, the tools call for surfdata files in a default location. These might not be available for all sites. Users can create their own surfdata files, using tools/site_and_regional/plumber2_usermods. | ||
| 4) It is suggested to use the flags-- setup-only to examine how the site files are being configured before running the simulations. | ||
| 5) It is suggested to add ``echo "baseflow_scalar = 0" >> user_nl_clm`` to the user_nl_clm file to avoid issues with the baseflow in the wetland sites. |
There was a problem hiding this comment.
Can you clarify what 'issues' means here and in 2?
ekluzek
added
the
documentation
|
I'm rebasing the PR to come to b4b-dev. We may also need to rebase the branch itself, depending on where it's at. |
ekluzek
added
next
Thanks @ekluzek ! I think that the branch itself should be fine, at least with regards to this documentation file. I don't think the file has been otherwise updated recently. |
ekluzek
removed
the
next
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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
More documentation for the PLUMBER 2 option using the newly developed ./run_tower tool created by @TeaganKing
Specific notes
Contributors other than yourself, if any:
CTSM Issues Fixed (include github issue #):
Related to #2997
Are answers expected to change (and if so in what way)?
No. Documentation only.
Any User Interface Changes (namelist or namelist defaults changes)? No
Does this create a need to change or add documentation? Did you do so? No
Testing performed, if any: None