Air PollutionWeather Coupled Forecasting System (Delhi NCR Focus)

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   Two-way coupled chemistry-meteorology modelling is the stated core and is computationally out of reach — substituting a statistical model trained on station data answers a question the statement explicitly opens by rejecting, so if you do that, say so rather than implying coupling

2. It gets worse

   Emissions inventories are the largest source of error in any air quality model and reliable local inventories for this region are not openly available, so even a correctly configured coupled run inherits that uncertainty

3. Still reading?

   A single seventy-two-hour coupled forecast can consume more compute than a whole hackathon allows, so you will demonstrate one hindcast rather than an operational system and should frame it that way

4. And the finisher

   No accuracy target is stated, so a forecast that looks broadly right during a smog episode can be presented as a success without any real verification — build the station comparison properly instead

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  2/5

  You have picked a fight with physics, procurement, or both. One of them always wins.

  The statement explicitly requires a coupled weather-chemistry model with two-way feedback, and running one is a research-group undertaking — it needs an emissions inventory the coupled model can consume, expert configuration, and core-hours well beyond a student allocation for even a single seventy-two-hour forecast over a fine domain.

• Innovation scope

  2/5

  Nothing here is new. Your only edge is execution — and execution is also everyone else's only edge.

  The coupled modelling framework is named, the feedback requirement is mandated, the species are listed, the horizon is fixed and the deliverable is specified, so the approach is dictated and what remains is configuration rather than design.

• Clarity

  4/5

  The ask is unambiguous, which quietly removes your favourite excuse.

  The physical mechanism is explained well and correctly, the species to model and the meteorological variables to couple are named individually, and the horizon and deliverables are explicit — though nothing states what forecast accuracy would count as success.

• Acceptance potential

  2/5

  The numbers do not like you. Bring something the numbers cannot see.

  The two-way coupled chemistry-meteorology model is the statement's explicit and central requirement and is beyond student compute, so most teams will substitute a statistical air quality forecast trained on station data — which is entirely achievable but is exactly the uncoupled approach the statement opens by rejecting.

• Effort

  Massive

  A semester of work wearing a hackathon costume. Something is getting cut; decide what now, not in week five.

  Configuring and running a coupled chemistry-transport model over a nested urban domain, assembling emissions inputs, validating against monitoring stations and building an operational dashboard is a research programme with a computational cost that dominates everything else.

• Demo-ability

  Medium

  Demoable, if you rehearse it. Nobody rehearses it.

  Reproducing a documented smog episode with the inversion diagnostic rising ahead of it is a persuasive and honest result, but you will be showing one hindcast run rather than an operating system, because each run is expensive.

• Data

  None supplied

  No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

  Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen 🪞

Somewhere around 140–330 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• The physical argument in the statement is correct and well explained, so the scientific framing of your pitch is already written and defensible
• Ground monitoring data for the region is publicly available and dense, so validation against observed concentrations is straightforward and honest
• Inversion strength as a standalone forecast diagnostic is genuinely useful, cheap to compute from meteorological fields alone, and is the one deliverable here that a small team can definitely produce well