AI-Powered Automated Underwater Marine Debris and Anomaly Detection System using Side-Scan Sonar Imagery

The receipts 🧾

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

1. Exhibit A

   Public side-scan sonar corpora are small and dominated by shipwrecks and aircraft, not ghost nets, so training on what exists and presenting it as debris detection is a substitution a marine technology judge will spot immediately

2. It gets worse

   Side-scan geometry is not photographic — slant range distortion, variable along-track spacing and the nadir gap mean an off-the-shelf detector applied to raw waterfalls learns artefacts, so geometric correction is a prerequisite rather than a refinement

3. Still reading?

   Acoustic shadows are simultaneously the strongest cue for a raised object and the biggest source of false positives, and a model that keys on shadow shape will flag every boulder on the seafloor

4. And the finisher

   No accuracy target or evaluation protocol is given, so you must define both and a judge may measure you against a different standard than the one you chose

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.

  Public side-scan sonar imagery exists but it is thin and dominated by shipwrecks and aircraft rather than the ghost nets and debris this statement is actually about, so you will train on a few hundred images of the wrong target class and claim debris detection — the model is buildable, the specific capability is not well evidenced.

• Innovation scope

  3/5

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

  The four deliverable components are enumerated and candidate architectures are named, but the genuinely hard part — distinguishing an artificial anomaly from natural seafloor texture under speckle and shadow — is left entirely open and is where any real contribution sits.

• Clarity

  4/5

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

  The four modules are specified individually, the acoustic challenges are named precisely, the report format and its required fields are stated, and the edge-deployment preference is explicit, though no accuracy target or evaluation protocol is given anywhere.

• Acceptance potential

  3/5

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

  Visually distinctive, a well-structured deliverable and a marine acoustics domain almost nobody will enter are all real advantages, but the training data for the actual target — ghost nets and debris — barely exists, so a NIOT judge will immediately ask what your model was actually trained to find.

• Effort

  Heavy

  Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

  Assembling and augmenting a sonar corpus, training a detector robust to acoustic artefacts, building a calibrated confidence and filtering stage, parsing sonar metadata for geotagging and constructing an operator dashboard is five pieces, and the data assembly will take longer than the model.

• Demo-ability

  Easy

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

  Side-scan sonar imagery looks genuinely unfamiliar and striking, so detections appearing over an acoustic waterfall are visually arresting in a way an ordinary photograph is not, and the downloadable geotagged report closes the loop concretely.

• 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 130–300 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.

• Sonar imagery is visually unfamiliar to almost every judge, so your demo carries a novelty that an ordinary image detection pipeline never will
• Geotagged structured output in a specified format is a concrete, checkable deliverable — a judge can verify that the coordinates in your report correspond to what appeared on the scan
• Marine acoustics attracts essentially no student teams, so the competitive field here will be very small