noresm2_5_alpha09: Next tag

[gold2718]

Check-mark list of items planned for NorESM2_5_alpha09. Check-mark components after new items are made available in the noresm_develop branch.

• BLOM: (Update BLOM tag to v1.7.0 #627)
  tag created: v1.7.0
  See plans for BLOM/iHAMOCC for NorESM2.5 for overview

• CTSM:
  new FATES/MEGAN refactor
  ctsm5.3.11-noresm_v2

[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.

[TomasTorsvik]

Closing this issue as noresm2_5_alpha09 has been created. Next tag will be noresm3_0_alpha01.