Work with regional surface datasets (v2) #24
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.
Supersedes #22, which was based on a very out-of-date version of
main
.This PR makes it so that the FATES land-use tool is compatible with
regrid_target_file
being a surface dataset generated by the CTSMsubset_data
script. These are different from the usual surface datasets because:lat
andlon
variables, although the associated dimensions are stilllsmlat
andlsmlon
.lsmlat
andlsmlon
, there are also coordinates with those names.Needs to be tested for compatibility with the usual kind of surface dataset. But as far as regional surface datasets, it works for my South America domain (cutoff at southern edge is intentional):
luh2
file:lupft
file :Remaining tasks
luh2
file looks okay.luh2
andlupft
) are unchanged when using normal surface datasets asregrid_target_file
.