Document layer_ref COORD_CONFIG #174
Merged
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
This adds a line to the parameter documentation of COORD_CONFIG highlighting the difference between layer_ref and linear (setting densities for layers and interfaces, respectively). The parameter documentation for LIGHTEST_DENSITY and DENSITY_RANGE are also changed to reflect the behaviour when the densities are specified for interfaces.
|
Thanks @angus-g . |
jskenigson
pushed a commit
to jskenigson/MOM6
that referenced
this pull request
Jan 25, 2021
* Fixes latent heat contribution from fprec and frunoff (MCT and NUOPC)
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.
This adds a line to the parameter documentation of
COORD_CONFIGhighlighting the difference betweenlayer_refandlinear(setting densities for layers and interfaces, respectively).The parameter documentation for
LIGHTEST_DENSITYandDENSITY_RANGEare also changed toreflect the behaviour when the densities are specified for interfaces. Is this best practice? Or should parameter documentations be the same for any
get_param()call for a given parameter?