microsoft / microsoft/aurora

Clarification on input data needed for Aurora Air Pollution

Open
#182 3 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

Hi there,

First, thank you for the excellent work behind Aurora!

I'm interested in running Aurora Air Pollution and have a question regarding constructing batches. In the tutorial for Aurora Air Pollution (https://microsoft.github.io/aurora/example_cams.html) the previous 12-hour analysis dataset is included in data array used in the batch. The Bodnar et al. (2025) paper states that for some pollutants, Aurora predicts a 24-hour difference (Section B7 in the supporting information). If I'm interested in generating surface PM2.5 forecasts, should the data array used in the batch include the previous 24-hours in order to initialize with the 24-hour difference?

Additionally, if I'm only interested in PM2.5, does Aurora require trace gas (NO, O3, CO, etc.) input from CAMS in order to work properly?

Thanks so much!

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 Aurora Air Pollution tutorial at microsoft.github.io/aurora/example_cams.html and Section B7 of the Bodnar et al. (2025) supporting information. Confirm the required input window for surface PM2.5 forecasts and whether trace-gas CAMS inputs are required, then document the confirmed guidance in the relevant tutorial or documentation.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.