Critical issues from MIP Convert for CMIP6 simulation UKESM1-0-LL abrupt-4xCO2 r1i1p1f2
- Dominant language
- Python
- Stars
- 8
- Forks
- 7
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 23
Description
Migrated Jira Issue CDDSO-35
Jira creation date 21/04/2022 15:23
-------
1 new variable failure reported in the critical issues log for this simulation;== `zhalfo` (onm, ocean-native)CMOR error is```!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: axis 11 (olevhalf, table: Omon): cmor and user units are! incompatible: and m!!!!!!!!!!!!!!!!!!!!!!!!!!```which implies to me that this part of the MIP table/CMOR is broken -- there have been messages on the CMOR3 github pages about olevhalf, but I don't know what the upshot is.In addition a confusing error from CMOR was traced back to the depth bounds being written for `Lmon/mrsos`.== `mrsos` (ap5, atmos-native)There is also another error in the CMOR log;```!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: axis sdepth1 (table: Lmon) , detected value at:! 0.100000 when valid_max is 0.100000!!!!!!!!!!!!!!!!!!!!!!!!!!```There is nothing in the MIP Convert logs for this one, but I've had a bit of a dig and this is coming from `mrsos` in `Lmon` where the `depth_bnds` written to the file are ```depth_bnds = 0, 0.100000001490116```I guess that the conversion to a double (float64?) from the 32 information in the PP headers is causing a slightly pedantic error message from CMOR (which doesn't raise an issue with MIP Convert?). Should we do anything about this?See comment:7:ticket:733.
-------
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the MIP Convert and CMOR logs for the UKESM1-0-LL abrupt-4xCO2 r1i1p1f2 simulation, focusing on zhalfo in Omon and mrsos in Lmon. Check the olevhalf unit incompatibility and the mrsos depth_bnds boundary value, then confirm that the conversion completes without these CMOR errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100