Skip to content

Conversation

@wael-mika
Copy link
Contributor

@wael-mika wael-mika commented Jan 16, 2026

Description

Geoinfo channels are static/constant-in-time variables such as altitude, land-sea mask, orography, etc. These variables provide geographic context to the model and can be used in the decoder for location-aware predictions.

Previously, geoinfo was only supported for OBS-type streams. This implementation extends geoinfo support to anemoi-type streams (ERA5, CERRA, etc.).

brief summary of the changes introduced in this pull request.

  • Caching Logic: Added _cached_geoinfo to store data after the first read. Updated _get() to pull from this cache instead of hitting the disk repeatedly, and ensured init_empty() resets it.
  • Channel Selection: Added select_geoinfo_channels() to filter the config for static fields (is_constant_in_time=True).
  • Initialization: Updated init to wire everything together—populating the channel indices, calculating normalization stats (mean/stdev), and priming the cache.

Issue Number

Closes #1428

Checklist before asking for review

  • I have performed a self-review of my code
  • My changes comply with basic sanity checks:
    • I have fixed formatting issues with ./scripts/actions.sh lint
    • I have run unit tests with ./scripts/actions.sh unit-test
    • I have documented my code and I have updated the docstrings.
    • I have added unit tests, if relevant
  • I have tried my changes with data and code:
    • I have run the integration tests with ./scripts/actions.sh integration-test
    • (bigger changes) I have run a full training and I have written in the comment the run_id(s): launch-slurm.py --time 60
    • (bigger changes and experiments) I have shared a hegdedoc in the github issue with all the configurations and runs for this experiments
  • I have informed and aligned with people impacted by my change:
    • for config changes: the MatterMost channels and/or a design doc
    • for changes of dependencies: the MatterMost software development channel

@clessig
Copy link
Collaborator

clessig commented Jan 16, 2026

Geoinfo channels do not have to be constant in time. They can be dynamic variables and the goal of the issue is that any channel can be a geoinfo channel. So no caching is possible.

@wael-mika
Copy link
Contributor Author

Thanks for your comment @clessig. I will adapt accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants