Skip to content
SIH Buddyby Ganeev Singh
Dev

🔥 Roast My Pick · SIH26126

Vision Based Autonomous Navigation for Unmanned Ground Vehicle for Outdoor environment

Bharat Electronics Limited

Medium39/100

Reasonable choice. The scoreboard liked it. The scoreboard is not the one asking questions on the day.

Worth considering. A respectable classic robotics problem with real public datasets, but all three components must work at once to show anything — decide early whether you have a physical rover, because a simulation-only run will be discounted by a BEL judge. Roughly 80–180 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

    Monocular visual odometry drifts badly outdoors and fails on textureless ground and in changing light, which is precisely the environment the statement specifies

  2. It gets worse

    All three components must work simultaneously for a single successful run, so partial progress produces no demonstrable result at all

  3. Still reading?

    The statement never says whether a physical vehicle is required, and a simulation-only submission may be judged as having avoided the hard part

  4. And the finisher

    Outdoor demos are weather and lighting dependent, so a run that worked yesterday may fail in front of the judges

The damage report

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

  • Feasibility

    3/5

    Buildable. Not comfortably. There is a week in here you have not planned for yet.

    Off-road traversability datasets such as RUGD and RELLIS-3D are public and mature visual SLAM implementations exist, so the components are individually reachable — but integrating perception, odometry and control into a system that actually completes a run needs either a physical rover or serious simulation work.

  • Innovation scope

    3/5

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

    All three sub-problems are long-established research areas with standard solutions, so your room is in the integration and in making the stack light enough to run onboard rather than in the individual components.

  • Clarity

    4/5

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

    The description numbers the three challenges and names the four expected components with a clear success criterion of collision-free navigation from point A to point B, leaving only the platform and evaluation environment unstated.

  • Acceptance potential

    3/5

    Middle of the pack. This statement will not win the room for you — you will have to.

    A well-posed classic robotics problem with public datasets available, but visual SLAM outdoors is genuinely brittle, all three components must work at once for anything to be demonstrable, and BEL judges will know precisely how hard the pose estimation actually is.

  • Effort

    Massive

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

    Perception, state estimation and control each demand real work, and the failure of any one of them means the vehicle does not complete a run, so all three must reach working quality simultaneously.

  • Demo-ability

    Medium

    Demoable, if you rehearse it. Nobody rehearses it.

    A vehicle completing a run autonomously is compelling, but outdoor runs are fragile and lighting-dependent, and a simulation-only demo carries the usual credibility discount for a robotics judge.

  • 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 80–180 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.

  • RUGD and RELLIS-3D are public off-road segmentation datasets built for exactly this unstructured outdoor setting, so traversability is trainable immediately
  • Mature open-source SLAM implementations mean you integrate rather than invent the pose estimation
  • The success criterion is binary and honest — the vehicle either reaches the goal without collision or it does not

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

Full analysis ↗Roast another

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.