Action item to be refined. Relevant message from Brian Leslie during ADMT26:
From a float manufacturer’s perspective: The current approach to how a sensor is sampled on a float depends heavily on guidance from the sensor manufacturer and ARGO. When direction is clear, we can implement the correct behavior. However, when multiple options exist, standardization needs to clarify whether one option should be preferred or if supporting multiple options is desirable. In some cases, the current implementation reflects what was first adopted rather than a strict limitation of the float platform. I’m happy to discuss this further and make any necessary float firmware changes to support the agreed approach.
Followed on by a request for manufacturers to provide a recommended sensor configuration "if the float belonged to them" during the RBR CTD talk and SBE Dynamic Correction talk. I think the optimal thing here is for manufacturers to publish this, and Argo Tech CoP to maintain a page linking to the latest proper configuration (as in #22).
Natural extension to #5, which already includes/mentions TSWAIT for Seabird CTDs.
Action item to be refined. Relevant message from Brian Leslie during ADMT26:
Followed on by a request for manufacturers to provide a recommended sensor configuration "if the float belonged to them" during the RBR CTD talk and SBE Dynamic Correction talk. I think the optimal thing here is for manufacturers to publish this, and Argo Tech CoP to maintain a page linking to the latest proper configuration (as in #22).
Natural extension to #5, which already includes/mentions TSWAIT for Seabird CTDs.