Got it. You suggest we not burden users with fixing a problem that was only recently discovered (between the time they wrote the data with CMOR and the time it was checked by PrePARE. There might be at least 2 cases when we might not want to be that lenient:

When a user has prepared output without using the CMOR tables and without CMOR, and has made an error in defining the standard_name.
When a user has been lazy and not obtained the latest CMOR table before writing output. (The table used might be one made available when the data request was still evolving, long before the time that the user is writing data.) When publishing that data, the updated tables are applied and the error is discovered. Shouldn't we object for such sloppy application of CMOR and require the data be rewritten?

All that being said, I wouldn't strongly object to making this a warning (rather than an error) since it doesn't involve the DRS (i.e., the attributes that determine unique file names and directory structures).

Checking out table versions (e.g. cmip6-cmor-tables) alongside CMOR install #676

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions