noresm parameter file

[rgknox]

Description:

This is a major update to the FATES parameter file. This includes:

1. parameter calibrations that targeted SP and no-comp fixed biogeo configurations
2. new parameters that were used only in the noresm version of FATES, that are likely to be introduced to NGEET/ at a later date (voc parameters)
3. a crop PFT (index 15) that is seemingly based off of the cool c3 grass

Collaborators:

@rosiealice @JessicaNeedham @adrifoster performed most of the calibrations (if I'm not mistaken), with technical and science support from @mvdebolskiy @maritsandstad @kjetilaas @mvertens

Expectation of Answer Changes:

This will change answers extensively in almost all tests.

Description of generative AI usage (as necessary)

No generative AI use as far as I understand

Checklist

If this is your first time contributing, please read the CONTRIBUTING document.

All checklist items must be checked to enable merging this pull request:

Contributor

• The in-code documentation has been updated with descriptive comments
• The documentation has been assessed to determine if updates are necessary
• Describe use of generative AI (if necessary)

Integrator

• FATES PASS/FAIL regression tests were run
• Evaluation of test results for answer changes was performed and results provided
• FATES-CLM6 Code Freeze: satellite phenology regression tests are b4b

If satellite phenology regressions are not b4b, please hold merge and notify the FATES development team.

Documentation

• Technical Note update:
• User's Guide update:

Test Results:

CTSM (or) E3SM (specify which) test hash-tag:

CTSM (or) E3SM (specify which) baseline hash-tag:

FATES baseline hash-tag:

Test Output:

[JessicaNeedham]

Thanks @rgknox ! Confirming from the Norway side that this has our latest changes and matches our current parameter file. Only difference is this file is missing the fates_init_seed parameter. @rgknox was that omitted deliberately? Can't remember if seed initialisation was implemented on the ngeet side.

[glemieux]

fates_init_seed

@JessicaNeedham was fates_init_seed in the file previously or did you mean fates_recruit_init_seed?

[JessicaNeedham]

fates_init_seed

@JessicaNeedham was fates_init_seed in the file previously or did you mean fates_recruit_init_seed?

I think we have a parameter that isn't implemented on the NGEET side - see this PR NorESMhub#33

This is in addition to fates_recruit_init_seed and allows one to initialize a seed bank as well as recuits.

EDIT: actually looking at it again, I'm not sure how it differs from fates_recruit_init_seed. @rosiealice do you remember?