Release v0.18.0 · climate-resource/input4mips_validation

Announcements

We have improved our multiprocessing support and the level of control given to the user. This means that multiprocessing should now work on all systems, including logging on non-windows systems. On windows we don't think the logging will come through properly yet (follow #108 for progress).

Changed the interface to [input4mips_validation.database.creation.create_db_file_entry_with_logging][input4mips_validation.database.creation.create_db_file_entry_with_logging] and [input4mips_validation.validation.database.database_file_entry_is_valid][input4mips_validation.validation.database.database_file_entry_is_valid].
Both of these functions were intended for internal use, hence this should hopefully cause minor issues for users. (#106)
Removed (the mostly internal interfaces) input4mips_validation.logging_config.serialise_logging_config and input4mips_validation.logging_config.deserialise_logging_config.
We don't think these are in general need, although it is still being figured out (see #108). (#107)

Added the --mp-context-id option to the command-line interfaces that support multiprocessing to give the user more control of how the multiprocessing is done.
This is then passed down the stack to [input4mips_validation.parallelisation.run_parallel][input4mips_validation.parallelisation.run_parallel]. (#107)

Added [input4mips_validation.parallelisation][input4mips_validation.parallelisation] to assist with simplifying parallelisation, mainly for internal use. (#106)
Added xr_load_kwargs to [input4mips_validation.xarray_helpers.iris.ds_from_iris_cubes][input4mips_validation.xarray_helpers.iris.ds_from_iris_cubes].
By default, this sets things up so the user doesn't get a thousand warnings about using cftime rather than numpy time objects
(but the user can pass the argument to change this however they wish). (#107)