Recovered data were not archived and are not available.

By Lori Garzio, on 3/16/17
Redmine Issue #10645

Recovered data were not archived and are not available.

By Lori Garzio, on 3/16/17
Redmine Issue #10645

Recovered data were not archived and are not available.

By Lori Garzio, on 3/16/17
Redmine Issue #10645

The high voltage lines providing power to the MFN via the CVT for CE09OSSM-00004 shorted out yesterday 2017-01-22 at 08:31 UTC:

<snip from 20170122.pwrsys.log>
2017/01/22 08:30:06.391 PwrSys psc: 24.87 2933.33 96.5 0100 00000000 00000000 ... cvt 1 376.31 142.50 1 13.65 0000000c No_FC_Data 526d
2017/01/22 08:31:06.395 PwrSys psc: 24.55 4253.33 96.5 0100 00000000 00000000 ... cvt 1 56.45 1902.50 1 13.84 0000000c No_FC_Data 51dd
</snip>

Sea state was high, but not unusual for this time of year (see attached plot). Have disabled future power scheduling to the MFN and applied an override to disable the CVT. No further data will be logged from the instruments on the MFN. This affects:

On DCL35:
* ADCPS (had already failed upon deployment)
* PCO2W -- should continue to autosample
* PHSEN -- should continue to autosample
* PRESF -- should continue to autosample
* VEL3D -- should continue to autosample
On DCL37
* CTDBP (plus DOSTA) -- should continue to autosample
* OPTAA
* ZPLSC -- had stopped reporting data early on in deployment, may still be autosampling

By Mike Smith, on 3/23/17
Redmine Issue #11837

CE01ISSM CAMDS stopped working

The CAMDS experienced some kind of failure wherein the sampling schedule suddenly changed from every 4 hours to approximately every 5 minutes. The camera stopped taking pictures 10/14 after either blowing through its batteries or disk space. This problem has not been seen before.

By Mike Smith, on 12/6/17
Redmine Issue #12957

Deployments 1 and 2: Data streams for this instrument will not match what we have in the database!! A FLORT was deployed (not a FLORD). The data had to be ingested using the FLORTM driver/parser, meaning the data streams are flort_sample.

By Lori Garzio, on 8/20/18
Redmine Issue #13507

Pressure values are 1-8 dbar higher in the recovered_inst dataset compared to the same data from the recovered_host and telemetered data delivery methods. Based on the Asset Management deployment depth, the recovered_host and telemetered data are more reasonable than the values from recovered_inst. Salinity and density are also offset between the delivery methods.

By Lori Garzio, on 12/13/18

Pressure values are 8-16 dbar higher in the recovered_inst dataset compared to the same data from the recovered_host and telemetered data delivery methods. Based on the Asset Management deployment depth, the recovered_host and telemetered data are more reasonable than the values from recovered_inst. Salinity and density are also offset between the delivery methods.

By Lori Garzio, on 12/13/18

Deployments 1, 4, and 6: The missing data in the recovered_inst stream are found at the end of the record in both the telemetered and recovered_host streams.

Deployments 1, 2, 3, 4, 5, 6 and 7: The timestamps do not match exactly when comparing streams of different methods. Overlapping the data in a plot will hardly show the difference.

Deployments 2, 4, 6, and 8: Invalid data represent data outside global ranges [0 - 400 µmol/Kg] : There are values greater than 400 and less than 0 in the data.

By Leila Belabbassi, on 12/14/18

Deployments 1, 2 and 7: Data gap at the end of the deployment is not annotated in the system.

Deployments 1, 2, 4, 5, 6, and 7: Invalid data represent data well above the maximum global ranges 400 µmol/(L,Kg) for dissolved oxygen concentrations or 110 % for oxygen saturation. Biofouling and DO sensor drift are both observed in the data.

By Leila Belabbassi, on 12/17/18

Deployments 1 and 6: Data gaps and the end of the deployment are not annotated in the system.

By Leila Belabbassi, on 12/17/18

Why are recovered-inst data not in the system?

The missing data in the recovered_host stream are found at the end of the record in the telemetered stream.

By Leila Belabbassi, on 12/17/18

The NetCDF data file is missing the appropriate variables coordinates. In this case the coordinates are 'int_ctd_pressure', 'lat' and 'lon'.

By Leila Belabbassi, on 12/17/18

A data gap is not annotated in the system ['2017-10-24T16:33:21', '2017-10-25T17:30:14'].
From previous notes, the gap in the data is due to batteries not recharging sufficiently. To conserve power, the MFN was turned off and the NSIF was reduced to 1 hour communications. The OPTAA is the only instrument on the MFN without internal batteries. See redmine ticket #12980 .

By Leila Belabbassi, on 12/18/18

A data gap of 26 days is not annotated in the system ['2018-04-29T12:33:33', '2018-05-25T17:30:13']

By Leila Belabbassi, on 12/18/18

A data gap is not annotated in the system ['2017-08-11T20:32:38', '2017-08-13T19:30:16]

By Leila Belabbassi, on 12/18/18

Salinity and density values are consistently higher in the recovered_host and telemetered datasets compared to the recovered_inst dataset (salinity: 0.0028 - 0.0031 higher; density: 0.0023 - 0.0026 kg m-3 higher). See the variable comparison analysis for more details: https://github.com/ooi-data-lab/data-review-tools/blob/master/data_review/output/GI03FLMA/GI03FLMA-RIM01-02-CTDMOG048/GI03FLMA-RIM01-02-CTDMOG048_sciencevar_comparison_summary.csv

By Lori Garzio, on 12/18/18

Annotation ID 350: Seawater temperature (degrees C) values are negative. Salinity and density are also incorrect. Temperature values in counts are within a similar range to those from deployments 2-4 (these deployments have reasonable temperature values). Annotation ID 350 should be updated with additional information after investigation.

By Lori Garzio, on 12/18/18

Annotation ID 351: Temperature values gradually increased over the length of the deployment. Similar behavior is not observed on the CTDs deployed at ~1700m and ~2300m (GI03FLMA-RI000-00-CTDMOH000 and GI03FLMA-RI000-00-CTDMOH400, respectively). Density and salinity values are also suspect. Annotation ID 351 should be updated with additional information after investigation.

By Lori Garzio, on 12/18/18

Conductivity (and salinity and density) dropped suddenly for approx. 24 hours, then returned to reasonable values. Excluding data from final statistics.

By Lori Garzio, on 12/18/18