A software system that uses AI to spot faulty data from weather station sensors in real time using temperature, pressure, and humidity inputs.
Ministry of Earth Sciences (MoES) · India Meteorological Department · Software
Signing in saves it for your whole team — everyone on your invite link sees the same two entries. Anything you shortlisted while signed out comes with you.
Decomposed from what the description asks for. Nothing added.
Data Stream Processor
Reads and processes incoming temperature, pressure, and humidity data streams.
Anomaly Detection Engine
Identifies sensor faults, spikes, and errors using machine learning models.
Explainable AI Module
Provides confidence scores and reasoning for detected anomalies.
Visualization Dashboard
Displays real-time alerts, sensor health status, and system data.
Value Imputation Tool
Suggests corrected values for anomalous observations.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will evaluate detection accuracy on injected anomaly data, real-time capability, explainability of the AI decisions, scalability, and practical deployability.
A jury can still ask about these. Decide them deliberately rather than by accident.
Generated from the brief's own wording and the competition's published rules — never from a guess about what this ministry prefers.
Specific historical datasets from the organizers?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Exact network size for scalability testing?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Has any part of this been shown at a previous event, hackathon or college project?
The guidelines are explicit: your solution must not have appeared in any previous event or programme, of any sort. A recycled project is what a team under time pressure reaches for.
The brief asks for data stream processor. How would you build that?
Decoded from SIH26073 itself — Reads and processes incoming temperature, pressure, and humidity data streams. The brief asks for it by name.
Each one is quoted from a gap in the brief, not a guess about your team.
No dataset provided
The description depends on real data, and the organisers have not attached a dataset link.
No measurable target
The description lists evaluation criteria weights but never states a required percentage accuracy threshold for success.
What the organisers attached, and what the brief assumes you can get.
Same organisation, same year. Reading two of theirs tells you more about what they care about than reading one.
Pick what you are about to do and copy the prompt. It carries the organisers' own wording, the constraints they never spell out, and an instruction not to invent requirements they never set.
Who has this problem, what already exists, and what you would have to find out.
The brief asks for anomaly detection engine. How would you build that?
Decoded from SIH26073 itself — Identifies sensor faults, spikes, and errors using machine learning models. The brief asks for it by name.
The brief asks for explainable ai module. How would you build that?
Decoded from SIH26073 itself — Provides confidence scores and reasoning for detected anomalies. The brief asks for it by name.
The brief asks for visualization dashboard. How would you build that?
Decoded from SIH26073 itself — Displays real-time alerts, sensor health status, and system data. The brief asks for it by name.
The brief asks for value imputation tool. How would you build that?
Decoded from SIH26073 itself — Suggests corrected values for anomalous observations. The brief asks for it by name.
Where does your data come from — a published source, one you collect, or one you generate?
No dataset is attached to this problem statement, so sourcing it is part of the work and nobody told you that.
Why not use what already exists? Name the closest thing to this that is already running.
A team that has not named the alternative themselves is answering this for the first time in the room.
Which single thing will you demonstrate end to end, start to finish, with nothing skipped?
Ours, not a rule: a narrow thing that fully works survives questioning better than a broad thing that half works. If nobody on the team can name it, that is the finding.
Show me this working: the jury will evaluate detection accuracy on injected anomaly data, real-time capability, explainability of the AI decisions, scalability, and practical deployability.
This is the evaluator read for your problem statement, decoded from the brief's own wording.