GEOS-ESM / GEOS-ESM/GEOSadas

Differences between AGCM.rc.tmpl in 5_27_1 @GEOSgcm_App version and in the latest version of @GEOSgcm_App

Open
#53 4 comments 0 reactions 3 assignees View on GitHub

@sdrabenh is already working on this.

Since Dec 2, 2020.

Dominant language
Fortran
Stars
8
Forks
3
Avg merge
1d 11h
Merged PRs (30d)
6

Description

Proactive note to remember an issue needed to be addressed as we move the model version forward from the initial 5_27_1 version.
There are inconsistencies between the version of the @GEOSgcm_App repo in initial 5_27_1 GEOSadas tag on git vs the latest version of the @GEOSgcm_App.
For example in the 5_27_1 tag AGMC.rc.tmpl has this for the ocean grid specification:

>>>COUPLED<<<      OGCM_NX: @OGCM_NX
>>>COUPLED<<<      OGCM_NY: @OGCM_NY
      OGCM_IM: @OGCM_IM
      OGCM_JM: @OGCM_JM
      OGCM_LM: @OGCM_LM
OGCM_GRIDNAME: @OGCM_GRIDNAME

      OGCM.GRID_TYPE: @OGCM_GRID_TYPE
      OGCM.GRIDNAME: @OGCM_GRIDNAME
      OGCM.IM_WORLD: @OGCM_IM
      OGCM.JM_WORLD: @OGCM_JM
      OGCM.LM: @OGCM_LM

      OGCM.POLE: 'PE'
      OGCM.DATELINE: 'DE'
      OGCM.NF: @OGCM_NF

>>>COUPLED<<<OGCM_GRIDSPEC: @OGCM_GRIDSPEC

whereas in the latest version of @GEOSgcm_App AGCM.rc.tmpl looks like this:

# Ocean Model Configuration Parameters
# ------------------------------------
      OGCM.GRID_TYPE: @OGCM_GRID_TYPE
      OGCM.GRIDNAME: @OGCM_GRIDNAME
      OGCM.IM_WORLD: @OGCM_IM
      OGCM.JM_WORLD: @OGCM_JM
      OGCM.LM: @OGCM_LM
      >>>COUPLED<<<OGCM.NX: @OGCM_NX
      >>>COUPLED<<<OGCM.NY: @OGCM_NY
      >>>COUPLED<<<OGCM.GRIDSPEC: MAPL_Tripolar.nc

      >>>DATAOCEAN<<<>>>LATLON_OGCM<<<OGCM.POLE: 'PE'
      >>>DATAOCEAN<<<>>>LATLON_OGCM<<<OGCM.DATELINE: 'DE'
      >>>DATAOCEAN<<<>>>CUBE_OGCM<<<OGCM.NF: @OGCM_NF

In particular the DATAOCEAN chevron stuff causes these not to be evaluated causing the model to fail.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.