-
Notifications
You must be signed in to change notification settings - Fork 51
Closed
Labels
data:ioIssues with the zarr output produced during inference/validationIssues with the zarr output produced during inference/validationevalanything related to the model evaluation pipelineanything related to the model evaluation pipelineinfraIssues related to infrastructureIssues related to infrastructuremodelRelated to model training or definition (not generic infra)Related to model training or definition (not generic infra)
Description
Describe the task. It can be a feature, documentation, etc.
To save space/time when running inference runs for Quaver we should run inference with the same time steps and frequency as the ones required by the Quaver database:
- initialization times are always at 00:00 and 12:00, so the samples should be distributed with a different frequency (now it's 6h)
- Pangu/GraphCast/AIFS scores have 12h forecast_steps. Is there a way to compute or store only those forecast steps so we can reduce the output zarr by half?
Maybe all these settings already exist and we just need to play with the config. Seeking for advice here and we could open sub-issues for the different tasks that come out of the discussion.
Hedgedoc URL, if you are keeping notes, plots, logs in hedgedoc.
No response
Area
- datasets, data readers, data preparation and transfer
- model
- science
- infrastructure and engineering
- evaluation, export and visualization
- documentation
Metadata
Metadata
Assignees
Labels
data:ioIssues with the zarr output produced during inference/validationIssues with the zarr output produced during inference/validationevalanything related to the model evaluation pipelineanything related to the model evaluation pipelineinfraIssues related to infrastructureIssues related to infrastructuremodelRelated to model training or definition (not generic infra)Related to model training or definition (not generic infra)
Type
Projects
Status
Done