Investigate time contiguity failure for `tpt-u-hxy-u` variables in `ap8`
- Dominant language
- Python
- Stars
- 8
- Forks
- 7
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 23
Description
During diagnostic review testing of UKCM2-0-LL historical u-dx055 the following set of variables failed QC due to the error `"Total length of time coordinate, 29216, is different from 29217 implied by time bounds (from 1900-01-01T00:00:00Z to 1910-01-01T00:00:00Z) and time frequency (PT3H)"`. This should be investigated as it appears to prevent the production of all `tpt-u-hxy-u` type variables for this stream.
The affected variables here are:
`cltcalipso_tpt-u-hxy-u|rsds_tpt-u-hxy-u|rsdscs_tpt-u-hxy-u|rsut_tpt-u-hxy-u|clt_tpt-u-hxy-u|rldscs_tpt-u-hxy-u|clwvi_tpt-u-hxy-u|rsutcs_tpt-u-hxy-u|rlds_tpt-u-hxy-u|clivi_tpt-u-hxy-u`
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the QC failure for the affected `tpt-u-hxy-u` variables in the UKCM2-0-LL historical `u-dx055` stream, using the reported time bounds and PT3H frequency. Trace the time-coordinate validation and production path to determine why 29216 points are produced instead of 29217. Done means the cause is identified and the production/QC behavior is corrected or clearly documented with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100