update default to correct nuopc.runseq in NEMO coupled cases

[daniele-peano]

Description of changes

changed the CPL_SEQ_OPTION option in config_component_cesm.xml for NEMO compsets

Specific notes

Contributors other than yourself, if any:

CMEPS Issues Fixed (include github issue #):
Fixes issue #3

Are changes expected to change answers? (specify if bfb, different at roundoff, more substantial)

Any User Interface Changes (namelist or namelist defaults changes)?

Testing performed

2-days coupled simulation

Testing performed if application target is CESM:

• (recommended) CIME_DRIVER=nuopc scripts_regression_tests.py
  • machines:
  • details (e.g. failed tests):
• (recommended) CESM testlist_drv.xml
  • machines and compilers:
  • details (e.g. failed tests):
• (optional) CESM prealpha test
  • machines and compilers
  • details (e.g. failed tests):
• (other) please described in detail
  • machines and compilers
  • details (e.g. failed tests):

Testing performed if application target is UFS-coupled:

• (recommended) UFS-coupled testing
  • description:
  • details (e.g. failed tests):

Testing performed if application target is UFS-HAFS:

• (recommended) UFS-HAFS testing
  • description:
  • details (e.g. failed tests):

Hashes used for testing:

• CESM:
  • repository to check out: https://github.com/ESCOMP/CESM.git
  • branch/hash:
• UFS-coupled, then umbrella repostiory to check out and associated hash:
  • repository to check out:
  • branch/hash:
• UFS-HAFS, then umbrella repostiory to check out and associated hash:
  • repository to check out:
  • branch/hash:

[mvertens]

@daniele-peano - Its interesting that MOM6 has chosen OPTION1 instead of OPTION2. This PR is fine. However, it would be good to understand whether long term NEMO wants OPTION1 instead. This is really a science question I think.

[daniele-peano]

Yes, I agree. This is a science question that needs to be discussed.