Implement missing value normalisation and standardisation #162
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes how missing values are handled across the workflow, addressing the problems raised in issue #157.
The main idea is to treat missing data consistently from start to finish. Missing values are converted to NaN early on, so xarray can handle them naturally during calculations. Just before writing the final output, values are converted back to the CMIP6-expected missing value (for example 1e20). This avoids silent errors and inconsistent behaviour when processing data.
To support this, a small set of shared utilities was added to handle missing values in a consistent way, both in the core processing code and in the CMIP6 vocabulary handling. These utilities work with lazy datasets, so there is no unnecessary loading of large files.
As part of the cleanup, exception handling in one of the derivation utilities was also simplified by using standard Python errors instead of a custom exception.