Compare computation cost of CTSM5.1/FATES-nocomp with CTSM5.1

[mvertens]

No description provided.

[mvertens]

This should be done with a spun up version of CTSM/FATES.

[rosiealice]

On the topic of choosing a compset, it seems like there are no CLM51 compsets listed in the comfig_compsets file on the NorESM repo, but there are on the CTSM repo. I am probably behind the curve with why this is, but why is this? @mvdebolskiy @mvertens ?

https://github.com/ESCOMP/CTSM/blob/master/cime_config/config_compsets.xml

vs

https://github.com/NorESMhub/CTSM/blob/clm-Nor-dev/cime_config/config_compsets.xml

[mvertens]

@rosiealice - thanks for bringing this up. I'll talk to @mvdebolskiy about this since he has been merging to newer ESCOMP CTSM updates. We should definitely bring them in and add them to the testing.

[mvdebolskiy]

On the topic of choosing a compset, it seems like there are no CLM51 compsets listed in the comfig_compsets file on the NorESM repo, but there are on the CTSM repo. I am probably behind the curve with why this is, but why is this? @mvdebolskiy @mvertens ?

https://github.com/ESCOMP/CTSM/blob/master/cime_config/config_compsets.xml

vs

https://github.com/NorESMhub/CTSM/blob/clm-Nor-dev/cime_config/config_compsets.xml

This is because you are looking at the wrong branch. The branch that is up-to-date with ESCOMP/CTSM is noresm. The default branch on this repo is for release versions.

[mvertens]

@mvdebolskiy - thanks for noticing this and pointing it out!

[rosiealice]

Ah right. That's a useful thing to know! Thx

[mvertens]

@rosiealice - can you specify the compset and resolution that I should try?

[rosiealice]

OK, sorry for the delay. Proposals all done now.
On compsets, this one is probably best.
2000_DATM%GSWP3v1_CLM51%FATES_SICE_SOCN_SROF_SGLC_SWAV

I found two compsets that were CLM51, global and not FATES-SP. The other has MOSART active, and I don't think we need to worry about MOSART in this case (but obvs we should test against a CLM51 case with the same ROF configuration.

We do, however, want to turn on the NOCOMP flag. I remember that the whole discussion around the testing and restart issue began with you trying to make that compset @mvertens? Is is lurking somewhere else?

For the resolution, I guess there are reasons to run at a resolution near our target to do with load balancing that I mentioned in the last meeting, so maybe whatever is closest to 2 degrees might be best? Not sure where to find these listed for NorESM?

[mvertens]

@rosiealice - thanks!!! Great news about the proposals being done. Fingers crossed for positive news on all of them.
I need to go back and remember how to get the nocomp flag turned on. We should have a compset that does it out of the box.

[mvertens]

All of the nocomp flags are turn on in the testmods - see clm/cime_config/testdefs/testmods_dirs/clm and the following:
FatesColdNoComp/
FatesColdNoCompFixedBioGeo/
FatesColdNoCompNoFire/

I'm going to try the following test tonight to see if we can get a reasonable namelist for a longer run:
SMS.f19_f19_mtn14.2000_DATM%GSWP3v1_CLM51%FATES_SICE_SOCN_SROF_SGLC_SWAV.betzy_intel.clm-FatesColdNoCompFixedBioGeo

[rosiealice]

Link to Ryan's variable history PR
NGEET/fates#1119

[mvertens]

This is the current output in the test:
hist_fincl1 = 'FATES_NCOHORTS', 'FATES_TRIMMING', 'FATES_AREA_PLANTS',
'FATES_AREA_TREES', 'FATES_COLD_STATUS', 'FATES_GDD',
'FATES_NCHILLDAYS', 'FATES_NCOLDDAYS', 'FATES_DAYSINCE_COLDLEAFOFF','FATES_DAYSINCE_COLDLEAFON',
'FATES_CANOPY_SPREAD', 'FATES_NESTEROV_INDEX', 'FATES_IGNITIONS', 'FATES_FDI',
'FATES_ROS','FATES_EFFECT_WSPEED', 'FATES_FUELCONSUMED', 'FATES_FIRE_INTENSITY',
'FATES_FIRE_INTENSITY_BURNFRAC', 'FATES_BURNFRAC', 'FATES_FUEL_MEF',
'FATES_FUEL_BULKD', 'FATES_FUEL_EFF_MOIST', 'FATES_FUEL_SAV',
'FATES_FUEL_AMOUNT', 'FATES_LITTER_IN', 'FATES_LITTER_OUT',
'FATES_SEED_BANK', 'FATES_SEEDS_IN', 'FATES_STOREC', 'FATES_VEGC',
'FATES_SAPWOODC', 'FATES_LEAFC', 'FATES_FROOTC', 'FATES_REPROC',
'FATES_STRUCTC', 'FATES_NONSTRUCTC', 'FATES_VEGC_ABOVEGROUND',
'FATES_CANOPY_VEGC', 'FATES_USTORY_VEGC', 'FATES_PRIMARY_PATCHFUSION_ERR',
'FATES_DISTURBANCE_RATE_P2P', 'FATES_DISTURBANCE_RATE_P2S',
'FATES_DISTURBANCE_RATE_S2S', 'FATES_DISTURBANCE_RATE_FIRE',
'FATES_DISTURBANCE_RATE_LOGGING', 'FATES_DISTURBANCE_RATE_TREEFALL',
'FATES_DISTURBANCE_RATE_POTENTIAL', 'FATES_HARVEST_CARBON_FLUX',
'FATES_STOMATAL_COND', 'FATES_LBLAYER_COND', 'FATES_NPP', 'FATES_GPP',
'FATES_AUTORESP', 'FATES_GROWTH_RESP', 'FATES_MAINT_RESP', 'FATES_GPP_CANOPY',
'FATES_AUTORESP_CANOPY', 'FATES_GPP_USTORY', 'FATES_AUTORESP_USTORY',
'FATES_DEMOTION_CARBONFLUX', 'FATES_PROMOTION_CARBONFLUX',
'FATES_MORTALITY_CFLUX_CANOPY', 'FATES_MORTALITY_CFLUX_USTORY',
'FATES_NEP', 'FATES_HET_RESP', 'FATES_FIRE_CLOSS', 'FATES_FIRE_FLUX_EL',
'FATES_CBALANCE_ERROR', 'FATES_ERROR_EL', 'FATES_LEAF_ALLOC',
'FATES_SEED_ALLOC', 'FATES_STEM_ALLOC', 'FATES_FROOT_ALLOC',
'FATES_CROOT_ALLOC', 'FATES_STORE_ALLOC'

[mvertens]

@rosiealice - is the plan still to create a new set of hist_fincl1 fields that I will output? At some point we'll start leveraging Ryan's PR when it comes in?

[mvertens]

@rosiealice - should I just do the 50 year run with the above namelist settings? I don't see that as a problem for just getting a performance metric. I'm happy to set that up this week.

[rosiealice]

Hi Mariana. Apologies for the delay. I think the following would likely be a fine set of variables just to see if we have a sane simulation going on...

hist_fincl1 = 'FATES_NCOHORTS', 'FATES_TRIMMING', 'FATES_AREA_PLANTS',
'FATES_AREA_TREES', 'FATES_STOREC', 'FATES_VEGC', 'FATES_LEAFC', 'FATES_FROOTC',
'FATES_STRUCTC','FATES_VEGC_ABOVEGROUND',
'FATES_NPP', 'FATES_GPP','FATES_AUTORESP',
'FATES_NEP', 'FATES_HET_RESP', 'TLAI'