CTD

Reference Designator
CE06ISSM-MFD37-03-CTDBPC000
Review Status
Review Complete
Note
Depth
29m
Class
CTDBP (CTD Pumped)
Make / Model
Sea-Bird / SBE 16plusV2

Dataset Reviews Last processed: 3/26/19, 7:24 PM

QC Check Info
Dep. Preferred Method Stream DD FD SG EG Gaps GD TS Rate (s) Pressure Comp. Time Order Valid Data Missing Data Data Comp. Missing Coords. Review
1 recovered_inst 186 94 0 91 0 0 13,383 600 30 / 29 1 2 Complete
2 recovered_inst 187 187 0 0 0 0 17,933 900 29 / 30 2 Complete
3 recovered_inst 207 207 0 0 0 0 19,744 900 29 / 30 3 3 Complete
4 recovered_inst 142 142 0 0 0 0 13,589 900 29 / 29 2 Complete
5 recovered_inst 201 146 0 18 2 39 8,973 29 / 30 4 2 Complete
6 recovered_inst 176 138 0 38 0 0 12,955 900 29 / 29 5 2 Complete
7 recovered_inst 175 174 0 0 0 0 16,674 900 29 / 30 Complete
8 recovered_host 177 176 0 0 0 0 2,093 29 / 29 6 Complete
Data Ranges Review Images

Test Notes

  1. fail: data found in another stream (gaps: [1] days: [3])
  2. no comparison: timestamps do not match
  3. no other streams for comparison
  4. fail: data found in another stream (gaps: [4] days: [44])
  5. fail: data found in another stream (gaps: [1] days: [39])
  6. fail: data found in another stream (gaps: [1] days: [1])

Data Coverage

Deployment: 12345678
99%
51%100%100%100%73%78%99%

Lat/Lon Differences (km)

Deployment: 12345678
1 0.00
2 1.630.00
3 1.860.260.00
4 2.070.440.240.00
5 1.900.280.080.170.00
6 1.960.330.120.130.060.00
7 2.010.390.160.090.110.060.00
8 1.880.360.160.340.230.230.250.00

Example Composite Data Plot

System Annotations

Metadata Start Date End Date Comment
CE06ISSM
10/7/14, 3:45 PM 9/30/16, 8:00 PM

All of the inshore surface moorings suffer from an issue called the 'top of the day problem.' A race condition exists in the CPM firmware when transferring daily log files harvested from the various sub-components in a buoy system (e.g. DCL16, CPM3, DCL35, etc) over the Iridium RUDICS connection. The primary CPM rsync's data files from the various sub-components to a central data directory. The first time a daily file is created/copied into that directory (usually shortly after midnight), a compressed copy of the file is created and that compressed file is queued up in a separate text file for transmission to shore. The transfer routine reads that text file and processes the files from that list in order from top to bottom. Once that compressed file is transferred to shore, no further updates for that file are sent to shore. Meanwhile, the CPM continues to rsync data from the different sub-components, updating the original daily log file. The net result is that data is accumulating in the daily log file for an instrument, but we may see only one record (or none) depending on when the rsync job occurred and the compressed file was created and staged for transfer to shore. This affects telemetered data only.

Id: 897 By: michaesm

CE06ISSM
7/26/16, 8:00 PM 10/3/16, 8:00 PM

Correcting the iridium data telemetry issues, permitting full telemetry of data files, resulting in greater power consumption than anticipated. Result is power level of the battery pack has dropped below operational limits and subsystems can no longer power instruments. Shutting the mooring down, and placing in a low power maintenance mode. 11 instruments offline.

Id: 898 By: michaesm
Flag: not_operational Exclude: No

CE06ISSM
12/31/16, 7:00 PM 4/22/17, 8:00 PM

The buoy main battery voltage is being drawn down faster than expected. Have shutdown further power to DCL17 and to the OPTAA on DCL16. This takes the following instruments offline:
DCL17
MOPAK
CTDBP (with attached FLORT)
VELPT
ACOMM
OPTAA
Have had to power off DCL17 and DCL16 and reduce call in frequency to 12 hours. Will still (at least should) receive data from MFN. Instruments affected are:
DCL17 (Buoy)
MOPAK
CTDBP3 (with FLORT)
VELPT1
UCSPP (aka ACOMM)
DCL16 (NSIF)
CTDBP1 (with DOSTA) (should internally log)
FLORT
PCO2W1 (should internally log)
PHSEN1 (should internally log)
OPTAA1
NUTNR (should internally log)
SPKIR
VELPT2 (should internally log)

Id: 899 By: michaesm

CE06ISSM
10/2/17, 8:00 PM 3/2/18, 3:44 AM

CAMDS not serviced by vendor in time for deployment

Id: 1236 By: michaesm
Flag: not_operational Exclude: No

CE06ISSM-MFD37
Method: telemetered
10/17/19, 12:45 AM 5/23/20, 8:00 PM

Updated, 2020-05-24: Between 2019-10-17 and 2020-05-24, the clock on CPM3 was off by approximately 27 minutes. Communications between the buoy and the MFN were out of sync during this time period. The clock was automatically updated during routine operations on May 24, 2020 to the correct time, allowing communications and normal operations on the MFN to resume. *Communications to the seafloor sensors failed. Status of the instrumentation and data loggers is unknown. With the exception of the VEL3D and OPTAA, the sensors on the seafloor platform should continue to autonomously sample for the remainder of deployment. Until we recover and redeploy the mooring in the spring of 2020, no further telemetered data will be available from the seafloor sensors.

Id: 1759 By: wingardc
Flag: not_available Exclude: No

Review Notes

Metadata Start Date End Date Comment
CE06ISSM-MFD37-03-CTDBPC000
Deployment: 1
1/8/15, 8:00 PM 4/10/15, 12:00 AM

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

By Lori Garzio, on 3/27/19

CE06ISSM-MFD37-03-CTDBPC000
Deployment: 3
12/10/15, 12:00 AM 5/6/16, 3:00 PM

Conductivity (salinity and density) dropped to values inconsistent with data from any other deployments. This should be investigated and annotated in the system. Excluding from data range summaries.

By Lori Garzio, on 3/27/19

CE06ISSM-MFD37-03-CTDBPC000
Deployment: 5
12/11/16, 12:00 AM 12/13/16, 12:00 AM

Unreasonable pressure spike - excluding from data range summary.

By Lori Garzio, on 3/27/19

CE06ISSM-MFD37-03-CTDBPC000
Deployment: 5
12/12/16, 2:00 PM 3/28/17, 12:00 PM

44 days of data in the middle of the deployment are missing from the recovered_inst data stream (these data are 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/27/19

CE06ISSM-MFD37-03-CTDBPC000
Deployment: 6
8/28/17, 12:00 PM 10/5/17, 2:00 PM

39 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/27/19

CE06ISSM-MFD37-03-CTDBPC000
Deployment: 8

Deployment 8 recovered_inst data should be available for download (the raw data file is available according to the ingest csv) or annotated to indicate why recovered_inst data are not available.

By Lori Garzio, on 3/27/19

New Note