Repository navigation
Conversation
frazane
force-pushed
the
feat/ensemble-inference
branch
2 times, most recently
from
November 6, 2026 09:06
76bd4dc to
68fefec
Compare
frazane
force-pushed
the
feat/ensemble-inference
branch
from
November 9, 2026 17:00
68fefec to
1d6496d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an optional
ensembleblock toforecasterrun entries, so the inference step produces N members per initialisation. This PR stops at GRIB on disk; ensemble verification comes in a follow-up PR. Stacked on #286: ensembles rely onoutput_variablesto keep storage manageable.anemoi-inference produces one member per process, so the prepare step writes one
config_{NNN}.yamlper member, writing togrib/{NNN}/with the file names of a deterministic run and tagged withnumber,numberOfForecastsInEnsembleanddataType=pf. Oneinference_executejob per init time runs the members on one node,inference_resources.gpuat a time (defaultmin(N, 4), one GPU each), seeding torch withseed + mbefore anemoi-inference starts. Each member has its own log and.okfile underlogs/inference_execute/{run_id}-{init_time}/, a retry only reruns the members that failed, and the rule's.okmeans all members exist. Until ensemble verification lands, verification, plots and MEC use member 001 and log a warning. Theensembleblock is part of the run-specific hash (run ids without it are unchanged) and is rejected on the forecaster of a temporal downscaler.Tested with stormy-plateau (anemoi-inference 0.11.1), 2 inits × 4 members on 2 GPUs: the GRIB keys read back correctly with the COSMO definitions, members differ, and a member rerun with the same seed is bit-identical.
Changes:
ForecasterConfigand the JSON schema,inference_prepare.py,inference_execute(newinference_execute_members.sh),run_specific_hash, arun_grib_dirhelper used by the verification, plot and MEC rules, README, unit tests.Notes
epsgoes ingrib2_keys, notencoding: the COSMO definitions have noepskey, and anemoi-inference reads it from either to pick the ensemble template for accumulated fields.inference_executeoutputs will be rerun once after this change: Snakemake records each rule's shell template and params, and both changed (the rendered command of a deterministic run is identical). To keep existing outputs, remove their records once withsnakemake --cleanup-metadata <files>. New runs are not affected. feat: select the variables written to the inference GRIB output #286 has the same effect through the newoutput_variablesparam ofinference_prepare_forecaster.