GEOS-ESM / GEOS-ESM/GEOSgcm_GridComp

Resolution-dependent values: Is basing off grid name "good"?

Open
#406 4 comments 0 reactions 4 assignees View on GitHub

@srfreita is already working on this.

Since Feb 5, 2021.

question :grey_question:
Dominant language
Fortran
Stars
10
Forks
13
Avg merge
17h 35m
Merged PRs (30d)
14

Description

This is sort of inspired by https://github.com/GEOS-ESM/GOCART/issues/18, but it reminded me of code in, say, Moist GC like this:
https://github.com/GEOS-ESM/GEOSgcm_GridComp/blob/e0cf9fabbe700c3e23571466f444973dd6b20e4e/GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSmoist_GridComp/GEOS_MoistGridComp.F90#L6120-L6128
and:
https://github.com/GEOS-ESM/GEOSgcm_GridComp/blob/e0cf9fabbe700c3e23571466f444973dd6b20e4e/GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSmoist_GridComp/GEOS_MoistGridComp.F90#L6156-L6158

I'm wondering if it would be better to express this in terms of, say, AREA from FV3? I ask only because if we ever get the stretched grid working in GEOS, I'm not sure what this code will do. Would it use an "average" value? So the fine-grid-area of the stretch uses a value too "coarse" and vice-versa?

Not sure. But I thought I'd ask the scientists. (The first swath of people I'm tagging are the Moist Team as that's where this code is from...)

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.