A couple of the tasks lead to warnings, which might confuse users. From running the test suite locally, I get 73 warnings at the moment, which we should be able to reduce significantly.
This is the output I get:
- FutureWarning: You are using legacy date precision for Iris units - max precision is seconds. In future, Iris will use microsecond precision - available since cf-units version 3.3 - which may affect core behaviour. To opt-in to the new behaviour, set
iris.FUTURE.date_microseconds = True.
- IrisDeprecation: Saving to netcdf with legacy-style attribute handling for backwards compatibility. This mode is deprecated since Iris 3.8, and will eventually be removed. Please consider enabling the new split-attributes handling mode, by setting 'iris.FUTURE.save_split_attrs = True'. warn_deprecated(message)
- IrisVagueMetadataWarning: Collapsing a non-contiguous coordinate. Metadata may not be fully descriptive for 'time'.
- IrisUserWarning: Collapsing spatial coordinate 'latitude' without weighting
- IrisVagueMetadataWarning: Collapsing a multi-dimensional coordinate. Metadata may not be fully descriptive for 'latitude'.
- IrisVagueMetadataWarning: Collapsing a multi-dimensional coordinate. Metadata may not be fully descriptive for 'longitude'.
- IrisLoadWarning: Not all file objects were parsed correctly. See iris.loading.LOAD_PROBLEMS for details.
A couple of the tasks lead to warnings, which might confuse users. From running the test suite locally, I get 73 warnings at the moment, which we should be able to reduce significantly.
This is the output I get:
iris.FUTURE.date_microseconds = True.