Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plans for BLOM/iHAMOCC for NorESM3.0 #462

Open
6 of 20 tasks
TomasTorsvik opened this issue Jan 15, 2025 · 0 comments
Open
6 of 20 tasks

Plans for BLOM/iHAMOCC for NorESM3.0 #462

TomasTorsvik opened this issue Jan 15, 2025 · 0 comments
Assignees
Labels
code release Issues related to upcoming code release or tagging

Comments

@TomasTorsvik
Copy link
Contributor

TomasTorsvik commented Jan 15, 2025

Tentative plans for default (and optional) settings for BLOM/iHAMOCC towards NorESM3.0

When shall MCT support phase out?
Due to changes in the timing of releases of NorESM2.3 and NorESM2.5, fixes in the hybrid coordinates would be good to enter a tag 1.8 of Blom that still supports MCT and could still be used together with NorESM2.3. See also: #439

General

BLOM-specific

NorESM 2.3+ (BLOM tag v1.8)

  • fix negative tracers in hybrid coordinates due to virtual freshwater fluxes

NorESM 3.0 and beyond

  • only mks (default) (remove cgs dependencies)
  • Test all model configurations with NUOPC coupler
  • Apply existing higher order vertical reconstruction for the remapping of diagnostic fields on to reference depths (hybrid coord. only, reconstruction does not exist for isopycnic coord.)

iHAMOCC-specific

NorESM 2.3+ (BLOM tag 1.8)

NorESM3.0 (envisaged BLOM tag 1.9 or 2.0) - due in INES II by June 2025

NorESM3.0+

  • Remove/modify compsets for the extended N cycle (in cime_config/config_component.xml), once MCT is depreciated
  • Nitrogen cycling interactive coupling through NUOPC

General iHAMOCC ideas

  • Potentially enable to include weathering rates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code release Issues related to upcoming code release or tagging
Projects
Status: In Progress
Development

No branches or pull requests

5 participants