nickrsan / seabird_ctd

Handles command, control, and data reading for stationary Seabird CTDs on fixed deployment
https://seabird-ctd.readthedocs.io
2 stars 0 forks source link

Comparison of streaming vs. internally-logged data #19

Open rgov opened 1 year ago

rgov commented 1 year ago

Is there information that's captured via Seabird internal logging (e.g., in the CNV format) that would not be available to a client receiving the realtime stream over serial?

nickrsan commented 1 year ago

Hi @rgov - I don't know the answer to that, especially not for all devices and I don't have any seabird CTDs available at this moment to test with. We did a little testing around this when we were deploying our devices, but I don't know if we looked for additional data stored in the download of the internal data on the device. Is there a parameter in particular you're looking for?

nickrsan commented 1 year ago

As another followup, that might be a question for Sea-Bird Scientific itself. They were pretty responsive to us while we were working on our deployments.

rgov commented 1 year ago

Will ask them, thanks.

We have a system (not using this package) that logs a serial stream from a CTD, which is received as four comma-separated decimal values. A user says they prefer the .CNV files which contain some additional metadata and are more directly usable, e.g., can be loaded into Sound Speed Manager.

Ideally I'd like to still use the streaming data (possibly with this package), since we use depth to trigger certain behaviors. But I have to investigate whether I can synthesize the same .CNV file (or equivalent) for the user's process.