Conversation
Contributor
|
I will test |
Contributor
|
Do we expect the other configs to be unaffected? |
Contributor
Author
Yes, other configs will not be affected by this PR. |
Louis-Frey
approved these changes
Mar 16, 2026
Contributor
Louis-Frey
left a comment
Louis-Frey
left a comment
There was a problem hiding this comment.
Thanks Francesco, looks good to me, ready to merge!
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
2 participants
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.
This PR introduces example configs that can be used to run inference with checkpoints generated after the 'multi-dataset' feature from anemoi-core has been merged. #114 fixed the environment generation, this PR fixes the inference execution. Changes in anemoi-inference were also needed (ecmwf/anemoi-inference#450).
Note: the actual changes needed in the configs are small, however entire new files had to be introduced, which might indicate our current design with respect to inference configs and patches is sub-optimal. Perhaps in the future we could allow users to specify some overrides directly in the evalml config.