suspect data

By Leila Belabbassi, on 5/14/19

suspect data

By Leila Belabbassi, on 5/14/19

a gap of 2 days at the end of April 2014 in are not annotated in the system

By Leila Belabbassi, on 5/14/19

gaps seen between 20 Dec 2014 and 10 Feb 2015 are not annotated in the system.

By Leila Belabbassi, on 5/14/19

gaps at the end of deployments 1 and 2 are not annotated in the system.

By Leila Belabbassi, on 5/14/19

The missing data at the end of deployments 1 and 2 (98 and 95 days) should be annotated.

By Lori Garzio, on 6/24/19

optical_absorption and beam_attenuation are arrays of all fill values. According to the computed_provenance in the provenance.json file, practical salinity and temp are missing from the ctdbp_cdef_dcl_instrument_recovered data stream.

By Lori Garzio, on 6/24/19

There is no pressure variable in the .nc files. This should be a coordinate.

By Lori Garzio, on 6/21/19

According to Roesler and Barnard (Optical proxy for phytoplankton biomass in the absence of photophysiology: Rethinking the absorption line height, Methods in Oceanography, 2013), “absorption meters are highly prone to biofouling, particularly biofilms which not only attenuate the collimated beam but also impact the scattering properties of the optical surfaces and tubes. In productive coastal waters biofouling can have significant impacts (i.e. 10% of the signal) within one to two weeks”.

By Lori Garzio, on 6/21/19

Conductivity, salinity, and density drop suddenly - this should be investigated and annotated if an issue is found. Excluding from summary data ranges.

By Lori Garzio, on 3/26/19

There are recovered_host and telemetered data available at the end of deployment 7 (2017-08-24T20:00:00 to 2017-10-12T20:00:00), and the same data are not available in the recovered_inst data stream. These data should be available in the recovered_inst data stream (or annotated if there was an issue with internally recording data).

By Lori Garzio, on 3/26/19

The missing data at the end of deployment 6 should be annotated.

By Lori Garzio, on 3/26/19

Suspect deployment - DO values below zero for a substantial part of the deployment. Issue should be investigated and annotated.

By Lori Garzio, on 3/29/19

The DO values at the end of deployment 3 are <50 umol kg-1 and jump to 150-200 umol kg-1 at the beginning of deployment 4. Further analysis should be done using shipboard bottle data, which is outside the scope of this project.

By Lori Garzio, on 3/29/19

The DO values at the end of deployment 8 are <50 umol kg-1 and jump to 150-200 umol kg-1 at the beginning of deployment 9. Further analysis should be done using shipboard bottle data, which is outside the scope of this project.

By Lori Garzio, on 3/29/19

49 days of data at the end of the deployment are missing from the recovered_inst data stream, but available in the recovered_host and telemetered data streams. These data should be available in the recovered_inst data stream (or annotated if there was an issue with internally recording data).

By Lori Garzio, on 3/28/19

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

Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

By Mike Smith, on 10/25/16
Redmine Issue #11427

The ZPLSC internal clock on CE01ISSM is slowly drifting out of alignment with GPS time. On two occasions now, I have had to shift the sampling window on the DCL to catch the reported condensed profile. Most recent data shows and estimated offset of approximately 1 minute 6 seconds.

CI needs to develop methods for correcting internal instrument clock data when working with recovered instrument data for cases where the recovered instrument data provides more information (e.g. full acoustic profiles rather than condensed). If left uncorrected, the recovered instrument data could be out of alignment with co-located sampling.

By Mike Smith, on 1/30/17
Redmine Issue #11809

The ZPLSC clock has drifted approximately 45 seconds, putting it outside of the original sample window. Sent a new mission file yesterday to change the time window. Went a little too far and have backed it back today. DCL37 will now turn on the ZPLSC port at 35 minutes after the hour and
leave it on for 2 minutes. ZPLSC is reporting it's first condensed profile at ~36 minutes and 13 seconds after the hour. Will need to monitor over the course of the deployment to make sure any further clock drift is accounted for. But, should be good for now.

There will be a data gap of about 7 days in the telemetered data. The recovered data will have the full record.

By Mike Smith, on 11/16/16