Currently several variables, including those that are auto-generated, are set to specific values when created to indicate that they have not been properly initialized, while still avoiding potentially random garbage values.
These values are all defined in their respective modules, but it would be better if instead they all used the same unset_XXX parameters located in the runtime_obj module. This would help clean-up the code, and provide a single location to control what these "non-initialized" values should be, at least for all of the host model routines outside of the dynamical core.
This can be done any time you are working on a module which sets variables to uninitialized values. Use the "addresses" GitHub tag in the PR description (at least until you are sure you've got the last one :)
Currently several variables, including those that are auto-generated, are set to specific values when created to indicate that they have not been properly initialized, while still avoiding potentially random garbage values.
These values are all defined in their respective modules, but it would be better if instead they all used the same
unset_XXX
parameters located in theruntime_obj
module. This would help clean-up the code, and provide a single location to control what these "non-initialized" values should be, at least for all of the host model routines outside of the dynamical core.