lermontov
Contributor
can you already achieve this though? you can work out what the MV reading should be at 'X' depth at 1.4 and 1.6I wonder if/when CCR dive computers will track/store/test/alert to more information about sensor behavior, beyond just instantaneous ppO2 readings.
Beyond just flagging or voting out sensors based on ppO2 (or mV) alone, a modern dive comp could sense when a sensor is out of spec, responds slower than it did on the previous dives, or seems blocked--e.g. less mV change expected during depth change with no solenoid injection--or has an mV pattern that matches more complex known problems (with x% confidence), or track/profile/flag a more detailed history of individual sensor data over their whole lifetimes.
Many of us are already doing this ("keeping an eye on sensor #3...")
A few thousand detailed CCR dive logs with the relevant data could easily generate a 'baseline' profile for what normal sensor data should look like. Predicting outliers in realtime is increasingly trivial machine learning/classification
I *hope* this is included in whatever Shearwater is doing with the new default/mandatory clouding of any dive logs imported into its apps
I have it written im my wet notes so I can cross check at predetermined depths
