Skip to content
SIH Buddyby Ganeev Singh
Dev

๐Ÿ”ฅ Roast My Pick ยท SIH26231

Digital Companion for Field Drug Testing

Ministry of Home Affairs

Mild11/100

Good pick. Genuinely. Now sit down, because the judges are going to try anyway โ€” and this is what they will try.

Strong pick. Achievable, well-scoped and genuinely useful โ€” the reference-card calibration and a truly tamper-evident record are the whole game, so build those solidly, and its honest presumptive-not-confirmatory framing is exactly what an MHA judge wants to see. Roughly 210โ€“480 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

    Colour classification must be genuinely robust across lighting, kit brands and camera sensors, and the reference card is what makes that work โ€” skip it and the results are as subjective as the eye

  2. It gets worse

    The tamper-evidence must be real โ€” a hash and signature that can be regenerated after the fact is not tamper-evident, so the crypto design matters

  3. Still reading?

    Different kits use different colour scales, so a classifier tied to one kit will not generalise without care

  4. And the finisher

    It is a modest build, so polish, robustness and the evidentiary rigour are what distinguish it rather than ambition

The damage report

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

  • Feasibility

    4/5

    Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.

    This is very buildable โ€” reference-card colour correction, colour classification and hash-plus-metadata record generation are all standard, need no special hardware, and the reference-card-in-frame approach is a genuinely sound way to make the colour reading robust to lighting.

  • Innovation scope

    3/5

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

    The components are individually standard, so the room is in making the colour classification genuinely lighting-robust and the record genuinely tamper-evident, rather than in novel technology โ€” but the standardisation-and-evidence framing is a real, useful contribution.

  • Clarity

    5/5

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

    The requirement is precise and well-bounded: reference-card calibration, defined outcome categories, the exact tamper-evident record fields, a searchable log, no new hardware, and an explicit note that the output is presumptive, not confirmatory.

  • Acceptance potential

    4/5

    Strong footing before you have written a line. Try not to waste it.

    A strong, achievable pick โ€” it needs no new hardware, the reference-card calibration is a sound answer to the real subjectivity problem, the tamper-evident record directly addresses the evidentiary gap the description names, and it is honestly scoped as presumptive, so a clean build genuinely solves the stated problem rather than over-reaching.

  • Effort

    Medium

    Manageable โ€” which means the bar for polish just went up, because you have no excuse left.

    A camera-capture app with colour correction, classification, signed records and a log is a contained, well-bounded build using standard components.

  • Demo-ability

    Easy

    Easy to demo โ€” and so is everyone else's. Working is the floor here, not the achievement.

    Photographing a test, watching it classify consistently under bad lighting where the eye is unsure, and generating a signed time-and-place record is a clean, concrete, self-explanatory demo you can construct exactly.

  • 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 210โ€“480 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.

  • No new hardware is required, so the whole thing is a software build on existing kits, which keeps it comfortably in scope
  • The reference-card-in-frame approach is a genuinely sound method for lighting-robust colour reading and can be validated with printed standards
  • The tamper-evident time-and-place record directly solves the evidentiary gap the description identifies

Nothing here is fatal. It is just the list of places this statement pushes back, and you now get to push there first.

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.