CTD

Reference Designator
CE01ISSM-RID16-03-CTDBPC000
Review Status
Review Complete
Note
Data missing from recovered_inst streams
Depth
7m
Class
CTDBP (CTD Pumped)
Make / Model
Sea-Bird / SBE 16plusV2

Dataset Reviews Last processed: 3/19/19, 6:59 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 122 102 0 20 0 0 14,544 600 7 / 7 1 1 Complete
2 recovered_inst 185 65 0 119 0 0 8,922 600 7 / 7 2 3 Complete
3 recovered_inst 127 126 0 0 0 0 12,020 7 / 7 4 3 Complete
4 recovered_inst 216 216 0 0 0 0 20,628 900 7 / 7 4 3 Complete
5 recovered_host 138 84 0 54 0 0 1,860 7 / 7 Complete
6 recovered_inst 200 108 0 92 0 0 9,837 900 7 / 7 5 3 Complete
7 recovered_host 177 64 0 112 0 0 1,531 7 / 7 Complete
8 recovered_inst 172 172 0 0 0 0 16,386 900 7 / 7 Complete
9 recovered_inst 181 181 0 0 0 0 17,326 900 7 / 7 3 Complete
Data Ranges Review Images

Test Notes

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

Data Coverage

Deployment: 123456789
61%36%
84%35%99%100%54%100%100%

Lat/Lon Differences (km)

Deployment: 123456789
1 0.00
2 0.000.00
3 0.080.080.00
4 0.200.200.220.00
5 0.080.080.000.220.00
6 0.180.180.170.090.170.00
7 0.240.240.220.430.220.390.00
8 0.170.170.160.090.160.010.380.00
9 0.170.170.180.370.180.340.100.330.00

Example Composite Data Plot

System Annotations

Metadata Start Date End Date Comment
CE01ISSM
4/17/14, 4: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: 868 By: michaesm

CE01ISSM
8/7/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.

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

CE01ISSM
12/11/16, 7:00 PM 5/30/17, 8:00 PM

On Monday, Mon Dec 12 15:30:00 2016, stopped receiving any data from CTDBP3. No indication as to possible cause.

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

CE01ISSM
2/5/17, 7:00 PM 4/30/17, 8:00 PM

The buoy and mfn battery voltages have been drawn down faster than expected. Have shutdown further power to DCL16, DCL17, CPM3, and DCL37 (DCL35 failed several weeks ago). This takes the following instruments offline:
DCL16
CTDBP + DOSTA (probably internally recording)
FLORTNUTNR (probably internally recording)
PHSEN (probably internally recording)
PCO2W (probably internally recording)
OPTAA
SPKIR
VELPT (probably internally recording)

DCL17
MOPAK
CTDBP + FLORT
VELPT (probably internally recording)
ACOMM
DCL35
ADCPT (probably internally recording)
PCO2W (probably internally recording)
PHSEN (probably internally recording)
PRESF (probably internally recording)
VEL3D (probably internally recording)
DCL37
CTDBP + DOSTA (probably internally recording)
OPTAA
ZPLSC (probably internally recording)

Id: 871 By: michaesm
Flag: not_available Exclude: No

CE01ISSM-RID16
Method: telemetered
1/11/20, 1:45 PM

During a large storm event on 2020-01-11, the surface buoy and NSIF broke free and went adrift. The buoy and NSIF were recovered from the beach the following mooring. No further data will be collected from these systems for the remainder of this deployment.

Id: 1893 By: wingardc
Flag: not_operational Exclude: No

Review Notes

Metadata Start Date End Date Comment
CE01ISSM-RID16-03-CTDBPC000
Deployment: 1
7/27/14, 9:50 PM 8/16/14, 10:30 PM

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

By Lori Garzio, on 3/26/19

CE01ISSM-RID16-03-CTDBPC000
Deployment: 2
12/13/14, 12:00 PM 4/12/15, 12:00 AM

There are recovered_host and telemetered data available for the second half of deployment 2 (2014-12-13T12:00:00 to 2015-04-12T00: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

CE01ISSM-RID16-03-CTDBPC000
Deployment: 5
5/18/16, 3:44 PM 10/2/16, 8:15 PM

Deployment 5 should be annotated to indicate why no recovered_inst data are available. According to the ingest csv, "No Data on instrument. Did not start logging."

By Lori Garzio, on 3/26/19

CE01ISSM-RID16-03-CTDBPC000
Deployment: 6
1/15/17, 3:00 AM 2/1/17, 12:00 PM

There are recovered_host and telemetered data available at the end of deployment 6 (2017-01-15T03:00:00 to 2017-02-01T12: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

CE01ISSM-RID16-03-CTDBPC000
Deployment: 7
4/19/17, 4:18 AM 10/12/17, 9:50 PM

Deployment 7 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/26/19

New Note