Method | Data Stream | Content | Type | |
---|---|---|---|---|
recovered_host | phsen_abcdef_dcl_instrument_recovered | Data Products | Report M2M Stats | Science |
recovered_host | phsen_abcdef_dcl_metadata_recovered | Metadata | Report M2M | Engineering |
recovered_inst | phsen_abcdef_instrument | Data Products | Report M2M Stats | Science |
recovered_inst | phsen_abcdef_metadata | Metadata | Report M2M | Engineering |
telemetered | phsen_abcdef_dcl_instrument | Data Products | Report M2M Stats | Science |
telemetered | phsen_abcdef_dcl_metadata | Metadata | Report M2M | Engineering |
Deployment | Cruise | Start Date | Stop Date | Mooring Asset | Node Asset | Sensor Asset | Latitude | Longitude | Deployment Depth | Water Depth |
---|---|---|---|---|---|---|---|---|---|---|
1 Review | OC1410A | 10/07/2014 | 04/10/2015 | CGMCE-06ISSM-00001 | CGINS-PHSEND-P0085 | 47.1334 | -124.268 | 7 | 30 | |
2 Review | OC1503D | 04/10/2015 | 10/13/2015 | CGMCE-06ISSM-00002 | CGINS-PHSEND-P0084 | 47.1311 | -124.272 | 7 | 29 | |
3 Review | OC1510A | 10/13/2015 | 05/06/2016 | CGMCE-06ISSM-00003 | CGINS-PHSEND-P0160 | 47.1333 | -124.271 | 7 | 29 | |
4 Review | TN-342 | 05/06/2016 | 09/24/2016 | CGMCE-06ISSM-00004 | CGINS-PHSEND-P0084 | 47.135 | -124.273 | 7 | 29 | |
5 Review | AT37-03 | 09/27/2016 | 04/15/2017 | CGMCE-06ISSM-00005 | CGINS-PHSEND-P0124 | 47.1336 | -124.272 | 7 | 29 | |
6 Review | SKQ201704S | 04/13/2017 | 10/05/2017 | CGMCE-06ISSM-00006 | CGINS-PHSEND-P0122 | 47.1341 | -124.272 | 7 | 29 | |
7 Review | SKQ201715S | 10/05/2017 | 03/28/2018 | CGMCE-06ISSM-00007 | CGINS-PHSEND-P0124 | 47.1346 | -124.272 | 7 | 29 | |
8 Review | SKQ201808S | 03/28/2018 | 09/20/2018 | CGMCE-06ISSM-00008 | CGINS-PHSEND-P0168 | 47.1336 | -124.269 | 7 | 29 | |
9 Review | SR1813 | 09/24/2018 | 04/25/2019 | CGMCE-06ISSM-00009 | CGINS-PHSEND-P0072 | 47.1348 | -124.271 | 7 | 29 | |
10 Review | SKQ201910S | 04/25/2019 | 10/12/2019 | CGMCE-06ISSM-00010 | CGINS-PHSEND-P0122 | 47.1347 | -124.271 | 7 | 29 | |
11 Review | SKQ201921S | 10/12/2019 | CGMCE-06ISSM-00011 | CGINS-PHSEND-P0083 | 47.1344 | -124.271 | 7 | 29 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CE06ISSM-RID16-06-PHSEND000 |
pressure coordinate is missing in the NetCDF data files for all deployments. By Leila Belabbassi, on 1/22/19 |
||
CE06ISSM-RID16-06-PHSEND000 Deployment: 1 |
2/1/15, 12:00 AM | 4/10/15, 12:00 AM |
pH data are suspect. By Leila Belabbassi, on 2/11/19 |
CE06ISSM-RID16-06-PHSEND000 Deployment: 2 |
The following gaps are not annotated in the system: ['2015-04-29T03:30:37', '2015-05-02T10:30:39'] By Leila Belabbassi, on 1/22/19 |
||
CE06ISSM-RID16-06-PHSEND000 Deployment: 2 |
4/10/15, 4:30 AM | 10/13/15, 11:45 PM |
pH data are suspect. By Leila Belabbassi, on 2/11/19 |
CE06ISSM-RID16-06-PHSEND000 Deployment: 3 |
3/7/16, 12:00 AM | 5/6/16, 3:00 PM |
pH data are suspect. By Leila Belabbassi, on 2/12/19 |
CE06ISSM-RID16-06-PHSEND000 Deployment: 4 |
5/6/16, 2:24 AM | 9/24/16, 3:33 PM |
pH data are suspect. By Leila Belabbassi, on 2/11/19 |
CE06ISSM-RID16-06-PHSEND000 Deployment: 5 |
51 days missing at the end of the data record indicates that the ph sensor did not record internally. If this is correct, annotation ID 899 should be modified to indicate the final status of the instruments. By Leila Belabbassi, on 1/22/19 |
||
CE06ISSM-RID16-06-PHSEND000 Deployment: 5 |
9/27/16, 4:43 PM | 10/15/16, 12:00 AM |
pH data are suspect. By Leila Belabbassi, on 2/11/19 |
CE06ISSM-RID16-06-PHSEND000 Deployment: 5 |
1/1/17, 12:00 AM | 4/15/17, 2:00 PM |
pH data are suspect. By Leila Belabbassi, on 2/11/19 |
CE06ISSM-RID16-06-PHSEND000 Deployment: 6 |
4/13/17, 7:53 PM | 10/5/17, 1:53 PM |
pH data are suspect. By Leila Belabbassi, on 2/11/19 |
CE06ISSM-RID16-06-PHSEND000 Deployment: 7 |
10/5/17, 11:35 PM | 11/30/17, 12:00 AM |
pH data are suspect. By Leila Belabbassi, on 2/11/19 |
CE06ISSM-RID16-06-PHSEND000 Deployment: 7 |
1/30/18, 12:00 AM | 3/28/18, 5:54 PM |
pH data are suspect. By Leila Belabbassi, on 2/11/19 |
CE06ISSM-RID16-06-PHSEND000 Deployment: 8 |
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 1/22/19 |
||
CE06ISSM-RID16-06-PHSEND000 Deployment: 8 |
3/28/18, 4:14 PM | 9/20/18, 3:26 PM |
pH data are suspect. By Leila Belabbassi, on 2/11/19 |
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-RID16-06-PHSEND000 |
7/8/19, 6:30 AM | 7/26/19, 4:35 AM |
Data indicates the sensor has either fouled or the intake tubing has become clogged.
Id: 1685
By: wingardc
|
CE06ISSM-RID16-06-PHSEND000 Method: telemetered |
11/26/19, 7:30 AM |
Data indicates the sensor has either fouled or the intake tubing has become clogged.
Id: 1904
By: politank
|
|
CE06ISSM-RID16-06-PHSEND000 Method: telemetered |
5/23/20, 8:00 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: 2195
By: wingardc
|