For the metadata fields that dump configuration YAML data (ie, metadata/pge_runconfig or metadata/algorithm_parameters_yaml), validations can fail due to whitespace differences in the source YAML. This is especially an issue for metadata/algorithm_parameters_yaml since it will raise a validation error if such a difference exists - this happened to me when I ran the golden dataset with an algorithm parameters file that lacked a trailing newline. The validator failed the products since their dtypes didn't match (|S#### != |S####-1).
For the metadata fields that dump configuration YAML data (ie,
metadata/pge_runconfigormetadata/algorithm_parameters_yaml), validations can fail due to whitespace differences in the source YAML. This is especially an issue formetadata/algorithm_parameters_yamlsince it will raise a validation error if such a difference exists - this happened to me when I ran the golden dataset with an algorithm parameters file that lacked a trailing newline. The validator failed the products since their dtypes didn't match (|S#### != |S####-1).