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_host | 186 | 131 | 0 | 0 | 3 | 55 | 2,598 | 1 / 1 | 1 | 1 | Complete | |||||
3 | recovered_inst | 207 | 118 | 0 | 88 | 0 | 0 | 5,545 | 1 / 1 | 2 | Complete | ||||||
5 | recovered_inst | 201 | 64 | 0 | 137 | 0 | 0 | 1,507 | 3,600 | 1 / 1 | 2 | Complete | |||||
6 | recovered_inst | 176 | 162 | 0 | 13 | 0 | 0 | 3,861 | 3,600 | 1 / 1 | 2 | Complete | |||||
7 | recovered_inst | 175 | 96 | 0 | 78 | 0 | 0 | 4,498 | 1 / 1 | 2 | Complete | ||||||
8 | recovered_inst | 177 | 177 | 0 | 0 | 0 | 0 | 7,724 | 1,800 | 1 / 1 | 2 | Complete |
Deployment: | 1 | 3 | 5 | 6 | 7 | 8 |
---|---|---|---|---|---|---|
70% | ||||||
57% | 32% | 92% | 55% | 100% |
Deployment: | 1 | 3 | 5 | 6 | 7 | 8 |
---|---|---|---|---|---|---|
1 | 0.00 | |||||
3 | 1.86 | 0.00 | ||||
5 | 1.90 | 0.08 | 0.00 | |||
6 | 1.96 | 0.12 | 0.06 | 0.00 | ||
7 | 2.01 | 0.16 | 0.11 | 0.06 | 0.00 | |
8 | 1.88 | 0.16 | 0.23 | 0.23 | 0.25 | 0.00 |
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
|
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: 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
|
CE06ISSM-SBD17-06-CTDBPC000 |
10/10/19, 12:30 PM | 10/12/19, 4:00 PM |
Internal batteries in the CTD are running low. Data is no longer available for the CTD and attached ECO Triplet (FLORT).
Id: 1736
By: wingardc
|
CE06ISSM-SBD17-06-CTDBPC000 Method: telemetered |
5/23/20, 8:00 PM | 6/22/20, 2:45 PM |
Reduced battery power on the mooring (unforeseen delay of mooring recovery well past the originally scheduled date) has resulted in the decision to reduce the operational schedule for this sensor for. Data, at a reduced sample rate, will be collected and telemetered to shore for as long as possible. Id: 2188 By: wingardc |
CE06ISSM-SBD17-06-CTDBPC000 Method: telemetered |
6/22/20, 2:45 PM |
Reduced battery power on the mooring (unforeseen delay of mooring recovery well past the originally scheduled date) has resulted in the decision to power off the data logger port for this sensor for the remainder of the deployment. No further data will be telemetered from this instrument, though recovered instrument data should be available after the mooring is recovered.
Id: 2190
By: wingardc
|
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CE06ISSM-SBD17-06-CTDBPC000 Deployment: 1 |
Deployment 1 recovered_inst data should be available for download (according to the ingest csv, the raw data file was never ingested because there wasn't a parser). If the recovered_inst data aren't available, the dataset should be annotated. By Lori Garzio, on 3/27/19 |
||
CE06ISSM-SBD17-06-CTDBPC000 Deployment: 1 |
11/30/14, 12:00 AM | 12/3/14, 12:00 AM | |
CE06ISSM-SBD17-06-CTDBPC000 Deployment: 1 |
12/20/14, 12:00 AM | 1/16/15, 12:00 AM | |
CE06ISSM-SBD17-06-CTDBPC000 Deployment: 3 |
2/7/16, 11:00 PM | 5/6/16, 3:00 PM |
The data gap at the end of deployment 3 should be annotated. By Lori Garzio, on 3/27/19 |
CE06ISSM-SBD17-06-CTDBPC000 Deployment: 5 |
11/29/16, 1:00 PM | 4/15/17, 2:00 PM |
The data gap at the end of deployment 5 should be annotated. By Lori Garzio, on 3/27/19 |
CE06ISSM-SBD17-06-CTDBPC000 Deployment: 6 |
9/21/17, 4:30 PM | 10/5/17, 1:53 PM |
The data gap at the end of deployment 6 should be annotated. By Lori Garzio, on 3/27/19 |
CE06ISSM-SBD17-06-CTDBPC000 Deployment: 7 |
1/9/18, 12:30 AM | 3/28/18, 5:54 PM |
The data gap at the end of deployment 7 should be annotated. By Lori Garzio, on 3/27/19 |