Enhance broken NEMO data error messaging
@mo-gill is already working on this.
Since Jun 18, 2026.
- Dominant language
- Python
- Stars
- 8
- Forks
- 7
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 23
Description
As an extension to this issue: https://github.com/MetOffice/CDDS/issues/860
It would be good to have a more helpful error message for when pre 1900 NEMO data is used (requiring the reset_time_coords.py to fix it):
```
File "(redacted)/CDDS/mip_convert/mip_convert/load/iris_load_util.py", line 240, in load_cube
merged_cubes = load_cubes(all_input_data, run_bounds, loadable, ancil_variables)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "(redacted)/CDDS/mip_convert/mip_convert/load/iris_load_util.py", line 211, in load_cubes
raise RuntimeError(error_msg.format(constraint_constructor.info, '" and "'.join(run_bounds)))
RuntimeError: No cubes found using constraints "variable_name=thetao" within "1850-01-01T00:00:00" and "1850-02-01T00:00:00"
Critical Errors found in all variables, therefore MIP convert has failed.
*** Finished conversions ***
```
This issue is to enhance that error message (possibly add a list of the files) and suggest that running the script on the NEMO data might fix the issue.
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.