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

Create a non cold-start FATES test #1277

Open
rgknox opened this issue Feb 8, 2021 · 1 comment
Open

Create a non cold-start FATES test #1277

rgknox opened this issue Feb 8, 2021 · 1 comment
Labels
blocker another issue/PR depends on this one enhancement new capability or improved behavior of existing capability FATES A change needed for FATES that doesn't require a FATES API update. testing additions or changes to tests

Comments

@rgknox
Copy link
Collaborator

rgknox commented Feb 8, 2021

FATES currently has a method of initializing plant structure via reading in from a text based inventory file.

Here is documentation on how it is done:
https://github.com/NGEET/fates/wiki/Model-Initialization-Modes#Guide_for_a_Cold_Start_Simulation_with_Inventory_Case_3

We have mostly used this method to intiailize simulations at model testbed sites, like Barro Colorado Island Panama, and Sierra Nevada US.

However, this method could also be used to store stand structure data at the end of a simulation (gridded), which could be used to initialize another simulation, along with a finidat file (if desired, which it would in this case).

The proposal is that we create one of these inventory datasets, on a very coarse grid (f10 x f10), and use this to initialize FATE vegetation for some tests.

Pros: FATES tests need to be STRESS tested, and without several hundred years of simulation behind it, we are only testing saplings, not fully developed canopies. This would go towards rectifying that.

Cons: The files are TEXT. Not ideal, but a worthy stop-gap to be used until we save this stuff as a self-describing format.

@rgknox rgknox added FATES A change needed for FATES that doesn't require a FATES API update. enhancement new capability or improved behavior of existing capability testing additions or changes to tests labels Feb 8, 2021
@ekluzek ekluzek added the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Mar 27, 2024
@samsrabin samsrabin removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Mar 28, 2024
@samsrabin samsrabin added this to the cesm3.0.0 release branch tag milestone Sep 9, 2024
@samsrabin
Copy link
Collaborator

samsrabin commented Sep 9, 2024

Blocks #2722.

@samsrabin samsrabin added the blocker another issue/PR depends on this one label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker another issue/PR depends on this one enhancement new capability or improved behavior of existing capability FATES A change needed for FATES that doesn't require a FATES API update. testing additions or changes to tests
Projects
None yet
Development

No branches or pull requests

3 participants