noresm2_5_alpha09: Next tag

[gold2718]

Add items for this tag here

• BLOM:
  latest tag: dev1.6.1.10
  See plans for BLOM/iHAMOCC for NorESM2.5 for overview

• CTSM:
  new FATES/DRYDEP capability
  Drydeposition  CTSM#88
  Dry deposition working with FATES-NOCOMP fates#11

• ccs_config
  add new build for esmf/6.0.1 on betzy

• CIME
  update to ESMCI cime6.1.46

• share
  update to ESCOMP share1.1.5 (update to ESCOMP share1.1.5 NorESM_share#6)

• CDEPS:
  fix DLND to be able to read CMEPS yearly auxiliary files to force CISM ESCOMP Changes to dlnd to enable dlnd to work with mediator auxiliary file output for glc forcing CDEPS#10
  update CDEPS to ESCOMP (update to escomp cdeps1.0.58 CDEPS#11)

• CMEPS
  update to ESMCOMP cmeps1.0.24 (update to ESMCOMP cmeps1.0.24 CMEPS#25)
  add new capability to have mediator auxiliary file for year multi-level ocean data from docn (parallel to what is obtained from lnd) for glc forcing

• WW3
  add new netcdf output for restarts and history using PIO and unstructured grid updates

[rosiealice]

So far, we hope that this tag will incude the updates that allow FATES to run with both MEGAN and dry deposition in coupled and NOCOMP modes.

DRYDEP
NorESMhub/CTSM#88
NorESMhub/fates#11

MEGAN
NorESMhub/fates#10
NorESMhub/CTSM#74

As well as also a change to the parameter file for SP mode.

n.b. that we won't switch to NOCOMP as the default for this to allow a) time to spin up and b) a cleaner test of the impacts of FATES-SP in coupled mode.

Should I write this list in a more formal way or does this suffice?
This is a nice organizational feature too...

[gold2718]

@rosiealice, This is okay but what I think would be the best is if there was a companion issue on NorESMhub/CTSM with a planned tag name that we could include in the issue description at the top. That way, we can summarize changes in one place with a link to the details.

[mvertens]

@rosiealice - noresm2.5.alpha08 brought in the MEGAN changes listed above. Is it feasible to bring in the dry dep changes in noresm2_5_alpha09?

[rosiealice]

Yes, that was for sure the next thing on the list :)

[mvertens]

@rosiealice - Great! Thanks for confirming.

[matsbn]

I suggest to create a new BLOM tag that includes the merged NorESMhub/BLOM#384. This allows for the BLOM vertical coordinate to be selectable as a compset option. Along with that I would suggest to make hybrid BLOM default in noresm2_5_alpha09 by replacing *_BLOM%ECO_* with *_BLOM%HYB%ECO_* in cime_config/config_compset.xml.

[jmaerz]

See also discussion: NorESMhub/BLOM#438 on a new BLOM tag.

[TomasTorsvik]

@matsbn - I created a dev1.6.1.10 tag on BLOM master now. Will make a PR to update the BLOM target for noresm2_5_alpha09.