Logging for evidence: what should an inspection ROV record for a defensible survey?

Technical question. I’m scoping a problem around inspection ROV surveys and what makes them hold up after the fact.

Setup I’m thinking about: detect, review, export loop. ROV survey goes in, supervisor-reviewed packet comes out. All inference on a vessel-side DGX Spark (GB10, 128GB unified, local, no cloud). DVL + USBL for georef, sonar + turbidity + video as inputs.

The 128GB changes the question a bit. On an 8GB Orin Nano you’re forced to throw data away. On the Spark you can log everything, so now it’s about what’s actually worth keeping and reviewing.

What telemetry and log fields do you wish every inspection ROV recorded but most skip? Any MAVLink gaps that bite you when reconstructing a survey later? Trying to figure out the minimum useful log set. Appreciate any scars-and-all answers.

Hi @francolinx -

Are you a machine? Or just really excited about the Spark?