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.
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
move rad calls docs from tech to user, update nudging and aerocom docs #2796
move rad calls docs from tech to user, update nudging and aerocom docs #2796
Changes from all commits
b25a0e1
d1d8e3f
0b6d21c
3dfee22
c45c6f0
0a756b6
7fe672e
9c7d36f
ed8859a
a3d251d
7a53ecc
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
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.
@PeterCaldwell @AaronDonahue @whannah1 @jsbamboo @bartgol: tagging you because you contributed to nudging code/convo/etc.
Peter suggested we write a general nudging document in this PR instead of what I had before (for background, in the two substantial PRs I submitted previously --- one related to aerocom cloud top and one coarse nudging --- I included docs with the PRs, but I only covered what I was adding). Now, that we are having a docs push, I think it is a good time to make this slightly more comprehensive. I edited my coarse-focused docs to be more generic (but austere, because I don't know what's best to include/exclude). Please feel free to suggest edits as you see fit or push to the branch. Thanks!!!
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.
Some things we might want to add (in this PR or another):
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.
Sounds good! I will do another sweep (likely tomorrow) with bits and pieces that will address all five items.
We assume the user gets the data in order before trying to nudge with it (i.e., converts everything to comply with EAMxx; this actually means several things --- some are critical and obvious, some are just straight annoying and hard to debug, so we definitely want to mention them if we are trying to be helpful 😉)
It's actually a little more involved. I will also include something about this in the revision. Internal remappers in EAMxx come in three flavors (two are obvious: from fine to coarse and vice versa; one is a nothingburger remapper that does nothing, but is helpful to have around). In nudging we only implement the nothingburger remapper and the coarse-to-fine remapper. So, we will need to add the third one of if we are to support complete flexibility. So... it is not just the mapping file that will need to be modified. It will require code edits. Also, we have a strict runtime error if a user is trying to do weighted nudging (e.g., for RRM) and nudging-to-coarse data simultaneously. There's like a bug (not too hard to fix) when they're combined, but it will need to be fixed. (Also, kind of related... but only insofar that weighted nudging can be used to do qbo and strato stuff... there's a potentially useful little feature, but kind of inactive and maybe need more testing, that allows users to set a height above/under which to nudge or not.)
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.
i'm definitely not good at fully thinking through a wide range of user needs ahead of time.. you guys have very cool suggestions
just two questions - i thought the weighted nudging && nudging-to-coarse data simultaneously has been addressed since Luca's PR (the one changed the order of horizontal and vertical mapping)? as long as the weight file is on the model grid (horz+vert)
another thing is Aaron's PR to change the startdate in TimeInterpolation (#2635) - it's very helpful for my own tests, just curious about its progress
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.
We still have a runtime check to forbid this: https://github.com/E3SM-Project/scream/blob/305bde73db9d3c641e8808caa8371ad399256d9d/components/eamxx/src/physics/nudging/eamxx_nudging_process_interface.cpp#L138C1-L142C60
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.
Got my threads mixed up (posted a separate comment on bib stuff here: #2796 (comment)). Addressed all comments I could and now back to the folks 😸
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.
oh i see, thanks! i feel this check may can be removed after #2701 (it seems like the interpolation order caused the previous failure, since in the previous interface perform_vertical_interpolation needs to be on the same horiz grid)