Features
- Added CMIP7 Fortran examples for regular grids, pressure levels, scalar height coordinates, basin axes, hybrid sigma levels, curvilinear grids, and fixed fields. (#977)
- The Fortran examples include a shared helper module, a run script, and nightly-build coverage.
- Added CMIP7 Python examples matching the new Fortran example coverage. (#978)
- Added example CMIP7 cmorizing notebooks using real model-data excerpts, including regular lat-lon data, pressure levels, hybrid sigma coordinates, basin axes, land-use fractions, and non-lat-lon sea-ice data. (#976)
Bugfixes
- CMOR now checks CV JSON strings and keys against the 1023-character limit before copying them into fixed-size strings, preventing crashes and reporting the offending value in the error message. (#985)
- The Fortran
cmor_dataset_jsonwrapper now returns a reliable status code. (#977)
Changes
- Concatenated variable
commentattributes now identify the source table by file name instead of usingactivity_id. (#984)- Example output now uses text like
CMIP6_Amon.json comment: ....
- Example output now uses text like
- Error and warning color formatting is now only emitted for terminal output, avoiding ANSI color characters in log files. (#985)
Issues / Pull Requests
- Handling of grids other than lat-lon (#832)
- preparing a CMOR demo with a coordinate having character string entries (#837)
- CMORizing notebook (#878)
- CMIP7 Fortran examples (#885)
- Example CMIP7 cmorizing notebooks (#976)
- CMIP7 Fortran examples (#977)
- Add Python examples (#978)
- Use of activity id in concatenated variable comments (#979)
- No error or warning for CV string values exceeding 1023 character limit (#982)
- Error message coloring format changes (#983)
- Use table file name instead of activity_id in variable comment (#984)
- Check the CV file for strings that exceed CMOR's character limit (#985)