Fix inline initial condition interpolation - #8664
Open
jinyuntang wants to merge 2 commits into
Open
Conversation
Just for testing auto blesser For testing purposes only. [BFB]
By avoiding some topo variables, it ensures the initial condition interpolation can move on. [BFB]
bishtgautam
reviewed
Aug 28, 2026
bishtgautam
left a comment
bishtgautam
left a comment
Contributor
There was a problem hiding this comment.
@jinyuntang, If you skip a variable that has topounit dimension, wouldn't the interpolated field be garbage?
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
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.
When applying initInterp.F90 to interpolate initial condition from one coarse grid to fine grid, 0.5 degrees to 0.25 degrees in my case, the model crashed without knowing to dealing with some accumulative variables related topo unit.
By skipping "topounit" variables, the inline interpolation is able to be done smoothly.
The fix is not expected to cause non BFB change, and the e3sm_land_debug test indicated so.
It fixed issue #8631.