You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an interest in adding some kind of numerical validation, the kind that's manually called on zarr stores.
Initial ideas are for sanity checks... e.g. "Does the file have temperatures for the surface of the sun?", "Does the file have negative precipitation values?", etc.
Might be worth prototyping these checks in argo manually. Think about standardizing vocabulary here too -- there are many different kinds of "validation"...
The text was updated successfully, but these errors were encountered:
Maybe add universal options/flags so that people can specify checks to be run on output for any command? This is a cool idea but it's a bit tricky because most of dodola's commands are streaming data and not reading it from local disk. Users might end up unintentionally loading +GBs of data that were not needed otherwise. We're not dealing with smaller transactional data but big Zarr stores.
That leads me to think these should be separate, explicit commands.
There is an interest in adding some kind of numerical validation, the kind that's manually called on zarr stores.
Initial ideas are for sanity checks... e.g. "Does the file have temperatures for the surface of the sun?", "Does the file have negative precipitation values?", etc.
Might be worth prototyping these checks in argo manually. Think about standardizing vocabulary here too -- there are many different kinds of "validation"...
The text was updated successfully, but these errors were encountered: