iCorrected viewColour correction runs in the cloud once the image arrives, not on the
camera. An early test — results will improve.
…—
Corrected——
Corrected
—
iFish count — model estimates
Each frame was sent once to a vision-language model, which returned a box and a confidence for every fish
it saw, and a total count. Show inference draws those boxes with their confidence and names the
model that produced them. Results are pre-computed; this page never calls the model.
Confidence is self-reported by the model, not a calibrated probability. Boxes are
approximate. Proof of concept.
Min confidence0.00
visibilityHow this is derivedEach capture is converted to greyscale and passed through an edge filter; the
score is the mean edge response across the frame — mean(|∇I|). Suspended sediment
and plankton scatter light, softening every edge, so the number falls as the water thickens.
No model. Observed 0.8–17.5. A proxy, not metres. A partial frame is missing
pixels, which lowers the score without the water being worse — the % beside it is completeness.clearhazymurkycamera offdeployment
Conditions & history
◆ deployment● notefish countwavesSignificant wave heightsignificant_wave_height_m from the Sofar Spotter on this
mooring, hourly, around the clock.The buoy reports through the night while the camera
sleeps, so this series is continuous where the image series is not.windWind speedwind_speed_mps, same Spotter, hourly.
Across this deployment wind and visibility show no meaningful relationship
(r = +0.14). Context, not a predictor.
This is a demonstration site showing a proof of concept, not a finished product.
Imagery is published with the express permission of our deployment partners.
Live data. Captures and completeness come from /devices/<id>/media; waves and wind from
/systems/<id>/spotter-telemetry. All times are stored UTC and rendered in the selected zone.
Visibility could not be measured — the image host does not allow pixel access
from the browser, so capture bars are coloured by transmission completeness instead. Computing it at ingest
would make it exact and free here.
Events and deployments are stored server-side and shared by everyone with access to this system.