-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update WM docs for SRW v3.0.0 release #2645
Open
gspetro-NOAA
wants to merge
9
commits into
ufs-community:release/public-v3.0.0
Choose a base branch
from
gspetro-NOAA:release/public-v3.0.0
base: release/public-v3.0.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update WM docs for SRW v3.0.0 release #2645
gspetro-NOAA
wants to merge
9
commits into
ufs-community:release/public-v3.0.0
from
gspetro-NOAA:release/public-v3.0.0
Conversation
This file contains 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
gspetro-NOAA
commented
Mar 12, 2025
The interval at which output (history) files are written is controlled in two | ||
places, and depends on whether you are using the write component to generate your output files. | ||
:numref:`Table %s <OutputControl>` describes the relevant variables. If the write_component is used, then the variables listed as ``model_configure`` are required. It is however, also required that the settings in ``input.nml`` match those same settings in ``model_configure``. If these settings are inconsistent, then unpredictable output files and intervals may occur! | ||
The interval at which output (history) files are written is controlled via the ``model_configure*`` files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mkavulich Here is the FAQ update you requested; we'd like to add it to the WM release docs. Please let me know if there are any issues/corrections.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Commit Queue Requirements:
Description:
This PR updates UFS WM documentation ahead of the SRW v3.0.0 release. It:
RTs ran successfully on Hercules.
Commit Message:
Priority:
Git Tracking
UFSWM:
Sub component Pull Requests:
UFSWM Blocking Dependencies:
Changes
Regression Test Changes (Please commit test_changes.list):
Input data Changes:
Library Changes/Upgrades:
Testing Log: