Skip to content
SIH Buddyby Ganeev Singh
Dev

๐Ÿ”ฅ Roast My Pick ยท SIH26144

Design & Development of a High-Sensitivity Micro barometer Infrasound sensor

National Technical Research Organisation (NTRO)

Incinerated96/100

Bold. Let us find out precisely how bold, in the order a panel will find out.

Proceed with caution. This is a precision-instrumentation physics problem requiring an acoustics lab and calibration standards no student team has โ€” the software-adjacent framing is misleading, and it belongs to a specialist hardware team or nobody. Roughly 65โ€“150 teams are expected to go here.

The receipts

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

  1. Exhibit A

    Detecting sub-audible pressure fluctuations at the sensitivities required is precision physics needing a low-noise transducer and analog design beyond a student team's reach

  2. It gets worse

    Calibration against a reference microbarometer requires equipment and standards that only a specialist lab has, so you cannot verify your own sensitivity claim

  3. Still reading?

    Generating genuine infrasound to demonstrate against is itself difficult, so the demo is likely to be unconvincing

  4. And the finisher

    NTRO evaluators work with this instrumentation professionally and will measure your prototype against real performance standards

The damage report

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

  • Feasibility

    1/5

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

    This is precision instrumentation physics โ€” detecting pressure fluctuations far below audible thresholds needs a low-noise mechanical transducer, sub-pascal differential sensing, careful long-period equalisation and formal calibration against a reference, which requires an acoustics lab, reference standards and analog design expertise no student team has.

  • Innovation scope

    3/5

    Mildly interesting. The novelty will not carry the room; the build has to.

    The description enumerates the required subsystems, so the architecture is largely prescribed, and infrasound sensor design is a mature specialist field, leaving limited room within a heavily constrained problem.

  • Clarity

    5/5

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

    The description lists all nine hardware subsystems and states the target frequency band precisely, so the requirement is unambiguous โ€” the difficulty is entirely in building it, not in understanding it.

  • Acceptance potential

    1/5

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

    One of the least suitable problems in the set for a student team โ€” the sensing physics demands a low-noise transducer and calibration infrastructure that are inaccessible, and NTRO judges work with infrasound instrumentation professionally and will assess a prototype against real sensitivity standards.

  • Effort

    Massive

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

    Nine interlocking hardware subsystems including a custom mechanical transducer, low-noise analog electronics and a calibration methodology is a full precision-instrument development effort.

  • Demo-ability

    Hard

    Near impossible to show working in five minutes, which is roughly five minutes more than you get.

    Generating and detecting genuine infrasound in a demo setting is difficult, and proving sensitivity and frequency response requires calibrated reference sources you will not have on hand.

  • 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 65โ€“150 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 requirement is completely specified, so there is no ambiguity about what to build
  • The wind-noise reduction interface and the mechanical design are well-documented in published infrasound literature to work from
  • Hardware plus a specialist title guarantees an essentially empty field

None of that means do not pick it. It means do not walk into that room having heard any of this for the first time from a judge.

The framing is a joke. The findings are not โ€” they are the same analysis on the statement page, and every line above is attached to a score or a fact in the record. It is one opinion with its reasoning attached, so argue with it before you trust it.