Optical Sensor Performance Evaluation After Major Storms
When tropical cyclones sweep down the Coral Sea or an east coast low parks itself off Sydney, the pulse of Australian waterways changes overnight. Catchments feeding the Murray–Darling Basin turn chocolate brown, plumes off Cairns and Townsville push sediment across fringing reefs, and stormwater outfalls along Port Phillip Bay roar with runoff from inner suburbs. Anyone running an optical turbidity monitor or suspended-solids sensor through those events knows the data spikes, but they also know the spikes are only useful if the instrument behind them is still telling the truth.
Post-storm performance evaluation is therefore not a tidy laboratory exercise. It is a field discipline that has to be done quickly, often in muddy, debris-choked conditions, with BoM warnings still active and access restricted by flooded roads. The aim is to separate real water-quality signal from sensor artefacts, whether caused by fouling, optical window damage, electronic drift or simply the limits of the measurement range. A short, repeatable checklist helps field crews in Brisbane, Newcastle or Karratha turn that chaotic first 48 hours into data they can defend in a compliance report.
The following sequence works for optical backscatter, nephelometric and IR reflectance probes installed on buoys, fixed jetties, pipelines and dredge plumes. It assumes the instruments were running through the event, but the same logic applies when a station is recommissioned after flood damage.
Pre-Storm Preparation and Baseline Capture
A clean post-event verdict always starts with what was captured beforehand. Before a tropical low forms in the Gulf of Carpentaria or a southerly buster funnels into Jervis Bay, every optical probe should have a fresh calibration certificate, a recorded zero reading in clean water, and a known response to a Formazin or StablCal reference standard. Photographs of that baseline data make later troubleshooting much faster, because the comparison point is sitting on the logger card rather than in someone's memory.
Document the optical window condition too. A quick photograph next to a ruler, taken at the same angle every visit, removes weeks of argument about whether a scratch was there in February or only appeared after the March flood. Australian field crews often use phone cameras with a macro clip, snapping both the window and a small label showing date, site code and time. It is a habit borrowed from the mining sector in the Pilbara, where suspended-solids probes on tailings lines are photographed the same way before cyclone briefings.
Finally, check the wiper or anti-fouling system if the instrument is fitted with one. Wipers on buoy-deployed turbidity sensors around the Great Barrier Reef Marine Park are run through a manual cycle the day before a forecast event, so any mechanical fault shows up when conditions are still manageable, not when the buoy is rolling in three-metre swell. Log the cycle count, battery voltage, and the current drawn by the wiper motor, because a tired motor that drags the supply down is a common silent failure mode during extended storm power budgets.
Visual and Mechanical Inspection in the Field
Once the worst of the weather has passed and it is safe to approach the station, walk the whole installation before trusting any number on the screen. Look at cable runs first: a tropical cyclone along the Queensland coast will routinely rip catenary cable off jetties in Cairns and Mackay, exposing conductors to salt spray that later corrupts the 4–20 mA loop. Tug gently on each connector, look for green verdigris on brass fittings, and confirm that desiccant packs inside instrument heads are still blue rather than pink.
Next, look at the mounting itself. A turbidity sensor on a pile in the Brisbane River can be lifted half a metre by debris, and a probe in a stormwater channel in western Sydney is often knocked out of alignment by a fallen branch. Even small angular shifts change the optical path length, especially for backscatter instruments that rely on a fixed scattering angle. A spirit level or a simple inclinometer on the mounting bracket takes seconds and can resolve a mystery drift that looks like sensor noise but is actually geometric.
If the sensor sits in a pipeline rather than open water, the same logic applies. The position of the probe relative to the pipe wall and flow direction matters enormously, and damage to a stilling well or sample line can completely change the air entrainment seen by the optics. For stations tied to process control, reviewing pipeline turbidity sensor placement during the inspection walk helps confirm that nothing has shifted since commissioning.
Optical Window Cleaning and Fouling Assessment
The optical window is the single most common source of post-storm measurement error. Flood events drag biofilm sloughs, oil sheens, iron floc and fine clay onto sapphire and quartz faces, and a layer that is invisible in still water can become a clear absorber once flow resumes. Wipe with a clean lint-free cloth and a small amount of deionised water, never solvents that could attack the housing seal, and re-photograph the window against the same ruler shot taken before the storm.
Biofouling also accelerates after major rain in warm Australian waters. In Moreton Bay and around the Dampier Archipelago, nutrient pulses from flood plumes trigger rapid algal growth on submerged surfaces within days. Crews servicing dredging plume monitors for port authorities in Gladstone or Port Hedland routinely schedule a second clean one week after the first post-event visit, because a single wipe is rarely enough once the water settles.
When comparing readings before and after cleaning, the difference tells you a lot about the data collected during the event itself. A 15–20 percent drop in turbidity after a clean window in heavy sediment suggests the sensor was reporting too high and the storm peak numbers are exaggerated. A very small change suggests the optical surface held up well and the data can be trusted more readily. Either way, the comparison belongs in the site log.
Calibration Verification with Field Standards
Field verification is where the post-event checklist earns its keep. A secondary standard, ideally a sealed Formazin or polymer bead suspension stable to within a few percent, should be poured across the optical face in a calibration cup. For instruments working in the hundreds to thousands of NTU range typical of flood plumes, a high-range standard is necessary because dilute 4000 NTU stock will not exercise the upper electronics the way the storm did.
For sites attached to dredging or mining operations, where suspended-solids concentrations regularly exceed 10 g/L, the more relevant check is a site-specific slurry reference. Carrying a jar of decanted tailings supernatant from the previous dry-season sampling trip is a common trick on the Pilbara and in the Bowen Basin, and it gives a sanity check that the sensor is still linear in the working range rather than just at low NTU. A broader discussion of extreme turbidity sensor selection is useful background when planning that reference set.
Document both the value the sensor reports on the standard and the time it takes to stabilise. A sluggish response after a storm, where the reading drifts towards the reference over several minutes instead of locking on immediately, often points to a partially fouled window or a weak light source. A fast, accurate response on a known standard is the strongest single reassurance that the storm-time data are usable for regulatory or research purposes.
Signal Quality, Drift and Range Performance
Raw signal diagnostics tell a different story than the cleaned-up engineering value on the display. Most modern optical turbidity sensors and suspended-solids probes expose internal counts, LED drive current, detector gain or signal-to-noise ratio through a service menu or serial command. Logging these during the storm, or pulling them afterwards from the logger, often reveals whether the instrument was working at the edge of its range or beyond it.
A flat-line signal at the maximum reported value, even though neighbouring staff gauges show the river still rising, is a classic sign of saturation. Optical backscatter sensors in particular lose linearity above their design point because multiple scattering invalidates the assumed single-scatter geometry. For Australian catchments, where a single east coast low can push Hunter River turbidity above 1500 NTU in hours, knowing the documented linear ceiling of the probe prevents treating saturated readings as genuine peaks.
Drift behaviour is equally informative. A sensor that returned to its pre-storm baseline reading within a few hours of the river clearing is behaving normally. One that sits 5–10 percent high for days afterwards probably has a thin biofilm layer the cleaning missed, or an LED that has aged. Either way, the trend in the diagnostic parameters usually points to the cause and saves shipping the instrument back to the workshop unnecessarily.
Cross-Validation Against Independent References
No optical probe should ever be the only source for compliance reporting after a major event. Side-by-side comparison with a freshly calibrated handheld turbidity meter, a Secchi disc measurement, or a laboratory TSS result on a co-located autosampler is the final layer of confidence. In the Murray–Darling system, the state agencies and WaterNSW routinely run independent laboratory checks on event samples taken at gauging stations, and aligning those numbers with the in-situ probe builds the case for keeping or flagging the continuous record.
For environmental research around seagrass meadows or coral monitoring sites, the stakes are higher because the data feed into recovery models. Pairing the optical reading with a physical sediment sample on the same tide and depth lets a researcher run a regression and quantify any systematic offset introduced by the storm. That offset can then be applied retrospectively to the continuous record.
A useful supporting piece on sediment oxygen demand discusses how turbidity feeds into wider water-quality interpretation, which is helpful when justifying post-event data corrections to project managers or regulators who only see the final numbers.
Documentation and Long-Term Sensor Health
The last step is often the most neglected. Every cleaning, every standard check, every diagnostic parameter pulled from the instrument should be filed with the deployment metadata and time-stamped against the storm peak. Australian projects that win repeat work, whether for a state environment authority or a port corporation, almost always have a standard post-event report template, and the discipline of filling it in within a week of the event is what separates a defensible dataset from a disputed one.
Long-term, this documentation feeds back into maintenance planning. A probe that consistently shows drift after flood events might need a different wiper schedule, a relocated mounting depth, or a switch to a longer-wavelength infrared optical path that is less affected by coloured dissolved organic matter washed out of eucalyptus-lined creeks. Sensor selection in Australia often shifts in response to those field learnings, particularly where catchments carry tannins and humic acids that interfere with visible-light nephelometric designs.
The end of the checklist is really the beginning of the next deployment. A short debrief with the field team, a note added to the asset register, and a copy of the storm-time diagnostic logs filed against the serial number of the probe all build a quiet institutional memory. When the next cyclone forms off the Top End, or the next east coast low spins up off the Illawarra, the crew will know exactly what their optical sensors did last time and where to look first.