SEA032 raw data format is different

[richardsc]

It appears that values are only written to the file when they change, rather then reflecting when the instrument was actually sampled.

What are the consequences of this? (E.g. for SOCIB?)

[richardsc]

This is looking to be a disaster.

For one thing, the NAV state only updates when it changes which means for any given data point we don't know what the NAV state is unless we look back in time. And that means that at the beginning of a file, because the state was last recorded in the previous file, we have no idea what it was. E.g.

PLD_REALTIMECLOCK;NAV_RESOURCE;NAV_LONGITUDE;NAV_LATITUDE;NAV_DEPTH;AROD_FT_TEMP;AROD_FT_DO;FLBBCD_CHL_COUNT;FLBBCD_CHL_SCALED;FLBBCD_BB_700_COUNT;FLBBCD_BB_700_SCALED;FLBBCD_CDOM_COUNT;FLBBCD_CDOM_SCALED;GPCTD_CONDUCTIVITY;GPCTD_TEMPERATURE;GPCTD_PRESSURE;GPCTD_DOF;
29/05/2018 14:12:31.001;;;;;;;251;1.5192;538;;88;4.0635;3.12181;7.5355;4.76;;
29/05/2018 14:12:31.101;;;;;;;;;;;;;3.12886;7.6813;4.59;;
29/05/2018 14:12:31.831;;;;;;;255;1.5480;513;;90;4.2441;;;;;
29/05/2018 14:12:32.101;;;;;;;;;;;;;3.13245;7.7502;4.42;;
29/05/2018 14:12:32.341;;;;;7.714;370.74;;;;;;;;;;;
29/05/2018 14:12:32.960;;;;;;;262;1.5984;537;;;;;;;;
29/05/2018 14:12:33.101;;;;;;;;;;;;;3.13739;7.8486;4.24;;
29/05/2018 14:12:34.080;;;;;;;267;1.6344;555;;91;4.3344;;;;;
29/05/2018 14:12:34.101;;;;;;;;;;;;;3.14196;7.9287;4.09;;
29/05/2018 14:12:35.101;;;;;;;;;;;;;3.14483;7.9754;3.96;;
29/05/2018 14:12:35.210;;;;;;;255;1.5480;528;;92;4.4247;;;;;
29/05/2018 14:12:36.101;;;;;;;;;;;;;3.14752;8.0048;3.87;;
29/05/2018 14:12:36.340;;;;;;;258;1.5696;511;;91;4.3344;;;;;
29/05/2018 14:12:36.381;;;;;8.023;367.99;;;;;;;;;;;
29/05/2018 14:12:37.101;;;;;;;;;;;;;3.14521;7.9118;3.84;;
29/05/2018 14:12:37.460;;;;;;;244;1.4688;509;;;;;;;;
29/05/2018 14:12:38.101;;;;;;;;;;;;;3.14510;7.9066;3.86;;
29/05/2018 14:12:38.591;;;;;;;250;1.5120;526;;;;;;;;
29/05/2018 14:12:39.101;;;;;;;;;;;;;3.14593;7.9576;3.97;;
29/05/2018 14:12:39.710;;;;;;;267;1.6344;547;;93;4.5150;;;;;
29/05/2018 14:12:39.761;115;;;5.006;;;;;;;;;;;;;
29/05/2018 14:12:40.101;;;;;;;;;;;;;3.14111;7.9544;4.14;;
29/05/2018 14:12:40.421;;;;;7.915;371.33;;;;;;;;;;;
29/05/2018 14:12:40.840;;;;;;;277;1.7064;530;;91;4.3344;;;;;
29/05/2018 14:12:41.101;;;;;;;;;;;;;3.14502;7.9492;4.38;;
29/05/2018 14:12:41.960;;;;;;;257;1.5624;558;;;;;;;;

[richardsc]

Worse, there are times where the CTD is sampled, but apparently the pressure hasn't changed, so only C and T are written to the file (see bold numbers for examples):

29/05/2018 14:13:42.101;;;;;;;;;;;;;3.23763;9.8372;1.67;;
29/05/2018 14:13:42.740;;;;;;;140;0.7200;404;;;;;;;;
29/05/2018 14:13:43.101;;;;;;;;;;;;;3.23459;9.7813;;;
29/05/2018 14:13:43.861;;;;;;;141;0.7272;424;;;;;;;;
29/05/2018 14:13:44.101;;;;;;;;;;;;;3.23254;9.7749;;;

[richardsc]

From Nicolas:

Just a quick update regarding the new firmware, the implementation is completed, we are now planning to deploy a glider this week in order to qualified this new version. I will keep you updated.