microsoft / microsoft/aurora

Shape Mismatch Between Input Batch and Predicted Output

Open
#158 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1k
Forks
174
PR merge metrics
No merged PRs in 30d

Description

I noticed that when running Aurora with ERA5 at 0.25° (but also with HRES T0 at 0.1°), the shape of the input batch tensors is 721×1440 (or 1801×3600), while the shape of the predicted outputs is 720×1440 (or 1800×3600). It seems that the South Pole is missing, as the metadata containing the latitude coordinates does not include the latitude of the North Pole (lat = -90°). Perhaps I’m missing something, but I wonder: in what kind of grid should we consider the model’s predictions to be represented if we want to validate the prediction? Is it a grid that is staggered relative to the one specified in the latitude and longitude metadata? Thanks

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Reproduce the ERA5 0.25° and HRES T0 0.1° cases, compare input and output tensor shapes with the latitude metadata, and establish which grid represents predictions for validation; done means the pole omission and alignment are explained.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.