microsoft / microsoft/aurora

Aurora: regional scale

Open
#87 6 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

Dear @wesselb,

Using the examples available at https://microsoft.github.io/aurora/example_hres_t0.html as a
starting point, we are adapting the Aurora model inputs to a regional scale, focusing on areas
of approximately 20°x40° or smaller. So far, we have concentrated on comparing the
temperature values predicted by the global and regional versions of the model. We have also
compared these results with HRES T0 data. For example, the following figure shows the
surface temperature obtained from the global and regional Aurora and its difference for our
study region.

Image

A similar result was obtained when we compare the Aurora and HRES T0 results.

Image

We initially expected the largest temperature differences between the global and regional
Aurora predictions to occur at the edge of the selected area, while the central region would
show very similar values in both simulations. However, the largest differences observed over
land surfaces, specifically over the northwest African coast and the Canary Islands, whereas
there is strong agreement over the oceanic region.
Could you help us to understand why aurora predicts with so many differences the temperature values over the ocean and the land?

We understand the need for fine-tunning specific to our study region but before this task,
what other factors would you consider important as input parameters for the model? For
example, window_size, decoder_depths, etc. We believe that some of these parameters
should modify to better adapt Aurora to a regional scale, but we do not know which ones
might be more important in this respect.

Thank you in advance for your help

Regards,
Sergio León

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

Start with the linked Aurora high-resolution example and compare the reported global and regional temperature results against the HRES T0 data described in the issue. The issue names no repository files, tests, or entry points, and it does not define a concrete change or acceptance criteria; clarification is needed before implementation can begin.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.