NorESM3_0_alpha01

[TomasTorsvik]

Planned for 3.0.alpha01

Each tag should preferably only include major updates from one component (e.g. include large code
changes from upstream repositories, large structural changes, new (default) model capability).
Minor component updates can be included in addition, if they do not change model output substantially.

Main objective: Bring in latest developments from CAM, update all components with new rpointers format

Components:

• CAM:
  • Update CAM to cam6_4_070 CAM#196
  • noresm3_0_001_cam6_4_070: Update noresm branch from ESCOMP CAM#197
• CIME:
  • Update all components to use rpointer files with timestamps #631
  • Rpointers update cime cime#97
• CCS_CONFIG:
  • Add Univ. Tronto server ccs_config_noresm#57
  • tag: ccs_config_noresm0.0.44
• CTSM:
  • Rpointers update ctsm CTSM#121
  • tag:
  • Rpointers update fates fates#15
• MOSART:
  • No PR needed.
  • ESCOMP-tag: mosart1.1.08
• BLOM:
  • Bring rpointer changes to BLOM BLOM#513
  • BASELINE DIFF (noresm2_5_alpha09a) expected in ocean BGC fields due to Fix sediment diagnostics and sediment quality BLOM#511
  • tag: v1.8.0
• WW3
  • Add ability for netcdf restarts WW3_interface#20
  • new capability for netcdf restarts WW3#17
• CMEPS:
  • Rpointers update cmeps CMEPS#29
• CDEPS:
  • Rpointers update cdeps CDEPS#12
• CICE:
  • Rpointer update cice NorESM_CICE#8
  • Rpointers update cice CICE#4
• CISM:
  • Rpointers update cism wrap CISM-wrapper#9
  • Rpointers update source cism CISM#2
• SHARE:
  • Rpointers update NorESM_share#7

closes #631

[mvdebolskiy]

PR merging order and standalone testing (checks):

• ccs_config
• share
• cime
• cmeps
• cdeps
• These depend on each other for stand-alone checkouts.
  • fates (ctsm dep)
  • ctsm
  • cism (cism dep)
  • cism-wrapper
  • cam
  • cice (noresm-cice dep)
  • noresm-cice
  • WW3
  • blom

[gold2718]

@mvdebolskiy, I don't understand all the dependencies. I know that standalone CTSM checks out CISM and FATES but what does FATES depend on?
Also, standalone CISM-wrapper checks out CTSM so that dependency is a bit circular.
But what does CISM checkout?
Can FATES and CISM (not wrapper) be moved outside that list and merged independently?

[mvdebolskiy]

@gold2718 fates technically doesn't depend on anything, same as source_cism, they are there, just so I do not forget them before making ctsm and cism-wrapper tags, since those will check them out.

[TomasTorsvik]

@mvdebolskiy - I have created a v1.8.0 tag on BLOM now, to be used for the noresm3_0_alpha01 tag.

[TomasTorsvik]

Thanks @mvdebolskiy for creating the noresm3_0_alpha01 tag!