ESCOMP / ESCOMP/CDEPS

Make sure data models share grid with forcing data?

Open
#133 5 comments 0 reactions 1 assignee Claimed by @mnlevy1981 View on GitHub
enhancement
Dominant language
Fortran
Stars
32
Forks
68
Avg merge
5d 13h
Merged PRs (30d)
2

Description

When running CESM with `datm` and an active ocean, you can use either CORE forcing or JRA. The former is available on the `T62` grid, while the latter is on the `TL319` grid. In MCT, if you try to use the JRA forcing on `T62` then CESM aborts with the error

```
MCT::m_AttrVectComms::GSM_scatter_: myID = 0. Invalid input, GSMap%gsize = 1036800, lsize(iV) = 64800
shr_mct_sMatReaddnc: Error on scatter of areasrc0
000.MCT(MPEU)::die.: from shr_mct_sMatReaddnc()
```

I suspect NUOPC will run in this configuration, and map the forcing data from TL319 -> T62 before mapping it from T62 -> TL319.

Proper behavior would be an informative error message, preferable from `buildnml`, but silently mapping TL319 -> T62 -> [ocn grid] is worse than aborting with a cryptic error

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.