aux_cdeps test using f19_g17_rx1 fails, because no longer defined in ccs_config
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- fortran
- Domain
- testing-qa
Research direction
Start with the aux_cdeps DROF test named in the issue and inspect ccs_config for the available grid aliases. Run the exact SMS_Ld3.f19_g17_rx1... test to reproduce the failure, then confirm which supported grid naming and configuration make the test pass.
Written by the indexing model from the issue text.
Description
The drof test in aux_cdeps using the f19_g17_rx1 grid alias fails because it's no longer defined in ccs_config. The exact test is:
SMS_Ld3.f19_g17_rx1.2000_SATM_SLND_SICE_SOCN_DROF%NYF_SGLC_SWAV.derecho_intel
PR #343 ran into this in it's testing
The grids that could be used that have rx1 explicitly are only old ones that support POP grids:
<model_grid alias="T31_g37_rx1" compset="_DROF" not_compset="_MOM">
<model_grid alias="f45_g37_rx1" compset="_DROF" not_compset="_MOM">
<model_grid alias="f45_g37_rx1" compset="_DROF" not_compset="_MOM">
<model_grid alias="f45_g37_rx1" compset="_DROF" not_compset="_MOM">
<model_grid alias="ne30_g16_rx1" compset="_DROF" not_compset="_MOM">
<model_grid alias="ne30_g16_rx1" compset="_DROF" not_compset="_MOM">
But, we are proposing to standardize the names for them to have the rx1 after the atm grid. And the older g16 grids for ocean shouldn't be used.
However, for example, f19_g17 could be used, because it should figure out that DROF will use the rx1 grid.
Since we no longer support POP and the standard CAM grid is now the SE dycore. The grid to use is probably this one:
ne30pg3_t232
- Dominant language
- Fortran
- Stars
- 32
- Forks
- 71
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ESCOMP/CDEPS
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
CESM Only enhancement question
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
If statements in DATM buildnml wrongly assume False if the value is 0.0May be free again @ekluzek claimed this 44 days ago, and no pull request is open. Openbug Responsibility: CTSM
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Chip source filter and denial markers miss Storage rows when a Storage activity source is pickedOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs-triage presubmit-gate
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
gke-labs/kube-agents#5001 ·
Maintainers usually reply within 1 day
-
crate: spate-core priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ComposioHQ/composio#5249 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
ai-driven-dev/framework#1163 ·
Maintainers usually reply within 1 day