Skip to content
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

Can't handle interpolating from a fates restart file because of the cohort dimension #211

Open
ekluzek opened this issue Jan 16, 2018 · 4 comments
Assignees
Labels
enhancement new capability or improved behavior of existing capability FATES A change needed for FATES that doesn't require a FATES API update. test: fates Pass fates test suite before merging

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Jan 16, 2018

You can't run use_init_interp=.true. on a fates restart file, because it doesn't know what to do with the cohort dimension, which is on over a dozen variables in the restart file from a simulation with fates.

This is what the error looks like when you try to do that:

Interpolating: fates_to_bgc_last_edts_col => fates_to_bgc_last_edts_col
Interpolating: fates_seed_rain_flux_site => fates_seed_rain_flux_site
Interpolating: fates_trunk_product_site => fates_trunk_product_site
ENDRUN:get_beg ERROR: Unknown subgrid level: cohortERROR in /glade/p/work/erik/clm_fates/components/clm/src/init_interp/initInterpBounds.F90 at line 159

@ekluzek ekluzek added the enhancement new capability or improved behavior of existing capability label Jan 16, 2018
@ekluzek ekluzek self-assigned this Jan 16, 2018
@billsacks
Copy link
Member

See also #76 for some more fundamental problems with using init_interp with FATES

@samsrabin
Copy link
Collaborator

Closing as duplicate of #76.

@samsrabin samsrabin added the closed: duplicate Issue already reported, or changes included in a different PR label Nov 7, 2024
@billsacks
Copy link
Member

If you find it easier to track this as part of #76 that's fine, but I wanted to point out that this is really a separate issue from #76. This issue is a very specific one related to the cohort dimension, which should be relatively easy to resolve. #76 (if I remember correctly) is a more fundamental issue that could take some more thought and rework. Both prevent correct operation of init_interp with FATES, but for different reasons.

@samsrabin
Copy link
Collaborator

Fair enough! Reopening.

@samsrabin samsrabin reopened this Nov 8, 2024
@samsrabin samsrabin added FATES A change needed for FATES that doesn't require a FATES API update. test: fates Pass fates test suite before merging and removed closed: duplicate Issue already reported, or changes included in a different PR labels Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability FATES A change needed for FATES that doesn't require a FATES API update. test: fates Pass fates test suite before merging
Projects
Status: Done
Development

No branches or pull requests

3 participants