Pushing NorESM land code changes back to ESCOMP & NGEET repos

[rosiealice]

We had a discussion on the FATES SE call last night about the plans for the CTSM6 release/code freeze (which is planned for the end of December and in ESCOMP#3104).

We discussed what we thought should be on there from the NorESM code. Most of our changes on FATES fall into the categories of:

• MEGAN
• Dry Deposition
• FCO2 flux calculation

All of these are there to get the NorESM coupled simulations working and so do not necessarily need to also be present in a release which is mostly targeted at supporting offline simulations with FATES (and coupled with CLM6). We all felt that, given this, the timeline was a bit short and already busy to push these changes back for the release. So we tentatively agreed to not include these things in the CTSM6 release.

We should nonetheless take a look at and other differences not related to these coupled model issues that need to or could go back into the release code. Probably this needs a systematic look through the diffs. I did not find any except for the plant hydraulic mortality change in NorESMhub/fates#28 but this is someting that we should maybe discuss in the next friday meeting.

@mvdebolskiy I did not have a very good handle on what else was different in our CTSM-side code. Perhaps that needs to be a topic at a different meeting?

Does anyone (@mvdebolskiy @mvertens @kjetilaas @JessicaNeedham @maritsandstad) not agree with this strategy (of leaving the chemistry coupling developments out of the official CTSM6 release)? We will of course release these with the NorESM code in the end.

[kjetilaas]

I think it makes sense not to prioritize to get these changes into the ctsm6 release but rather focus on getting NorESM ready.