Method | Data Stream | Content | Type | |
---|---|---|---|---|
recovered_host | adcp_config | Configuration Data | Report M2M | Engineering |
recovered_host | adcp_engineering | Engineering Data | Report M2M | Engineering |
recovered_host | adcp_velocity_earth | Earth Coordinates Data Products | Report M2M Stats | Science |
recovered_inst | adcp_config | Configuration Data | Report M2M | Engineering |
recovered_inst | adcp_engineering | Engineering Data | Report M2M | Engineering |
recovered_inst | adcp_velocity_earth | Earth Coordinates Data Products | Report M2M Stats | Science |
telemetered | adcp_config | Configuration Data | Report M2M | Engineering |
telemetered | adcp_engineering | Engineering Data | Report M2M | Engineering |
telemetered | adcp_velocity_earth | Earth Coordinates Data Products | Report M2M Stats | Science |
Deployment | Cruise | Start Date | Stop Date | Mooring Asset | Node Asset | Sensor Asset | Latitude | Longitude | Deployment Depth | Water Depth |
---|---|---|---|---|---|---|---|---|---|---|
1 Review | OC1503D | 04/09/2015 | 09/25/2015 | CGMCE-09OSSM-00001 | CGINS-ADCPTC-17122 | 46.8539 | -124.958 | 7 | 542 | |
2 Review | OC1510A | 10/15/2015 | 05/07/2016 | CGMCE-09OSSM-00002 | CGINS-ADCPTC-22717 | 46.8531 | -124.954 | 7 | 542 | |
3 Review | TN-342 | 05/12/2016 | 09/22/2016 | CGMCE-09OSSM-00003 | CGINS-ADCPTC-17122 | 46.8537 | -124.961 | 7 | 542 | |
4 Review | AT37-03 | 09/20/2016 | 04/14/2017 | CGMCE-09OSSM-00004 | CGINS-ADCPTC-19002 | 46.8508 | -124.972 | 7 | 542 | |
5 Review | SKQ201704S | 04/12/2017 | 10/06/2017 | CGMCE-09OSSM-00005 | CGINS-ADCPTC-19000 | 46.8529 | -124.959 | 7 | 542 | |
6 Review | SKQ201715S | 10/04/2017 | 03/30/2018 | CGMCE-09OSSM-00006 | CGINS-ADCPTC-22809 | 46.8478 | -124.984 | 7 | 542 | |
7 Review | SKQ201808S | 03/26/2018 | 09/19/2018 | CGMCE-09OSSM-00007 | CGINS-ADCPTC-19000 | 46.853 | -124.958 | 7 | 554 | |
8 Review | SR1813 | 09/19/2018 | 04/25/2019 | CGMCE-09OSSM-00008 | CGINS-ADCPTC-22809 | 46.849 | -124.978 | 7 | 542 | |
9 Review | SKQ201910S | 04/24/2019 | 10/13/2019 | CGMCE-09OSSM-00009 | CGINS-ADCPTC-22114 | 46.8527 | -124.954 | 7 | 542 | |
10 Review | SKQ201921S | 10/11/2019 | CGMCE-09OSSM-00010 | CGINS-ADCPTC-22809 | 46.865 | -124.948 | 7 | 542 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CE09OSSM-RID26-01-ADCPTC000 |
The pressure variable (daPa) is an array of fill values for every deployment. By Lori Garzio, on 8/20/19 |
||
CE09OSSM-RID26-01-ADCPTC000 Deployment: 4 |
|||
CE09OSSM-RID26-01-ADCPTC000 Deployment: 6 |
Annotation ID 1239 should be updated - only 3 days of recovered_inst data are available, so the full data record wasn't available upon recovery. By Lori Garzio, on 8/20/19 |
||
CE09OSSM-RID26-01-ADCPTC000 Deployment: 7 |
There are no recovered_inst adcp_velocity_earth data available for download for this deployment. According to the ingest csv, raw recovered_inst data files are available. These should be ingested or the dataset should be annotated to explain why recovered_inst data aren't available. By Lori Garzio, on 8/20/19 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CE09OSSM-RID26-01-ADCPTC000 |
9/5/16, 8:00 PM | 10/21/16, 8:00 PM |
At roughly 10:30 on Tuesday, the ADCP on the NSIF started to include garbage characters in the data file. It is intermittent, and there are periods where data is still coming through. This could be a low battery, or something else. In an attempt to remedy it, the voltage supplied to the ADCP has been increased to 24V. Update: The garbage continued to come through after the voltage was changed. It could be a suspect cable, or loose connection, rather than a battery issue.
Id: 931
By: michaesm
|
CE09OSSM-RID26-01-ADCPTC000 |
10/5/17, 8:00 PM | 10/5/17, 8:01 PM |
ADCPT started receiving/generating random break commands right after deployment. Interventions at the time were unable to resolve, but the system should still be collecting data. The problem could have been caused by the DCL sending erroneous commands. Telemetered data no longer flowing to the system. Data should be available upon recovery.
Id: 1239
By: michaesm
|
CE09OSSM-RID26-01-ADCPTC000 Method: telemetered Stream: adcp_engineering |
2/9/19, 7:00 PM |
Started to see evidence of random binary encoded data in the ADCP record. In the past, this has been evidence of electronic noise on the serial lines connecting the instrument to the data logger adversely affecting the behavior of the instrument. We have disabled the data logger port for the remainder of the deployment to minimize the chance of any further disruptions to the ADCP.
Id: 1553
By: wingardc
|
|
CE09OSSM-RID26-01-ADCPTC000 Method: telemetered Stream: adcp_velocity_earth |
2/9/19, 7:00 PM |
Started to see evidence of random binary encoded data in the ADCP record. In the past, this has been evidence of electronic noise on the serial lines connecting the instrument to the data logger adversely affecting the behavior of the instrument. We have disabled the data logger port for the remainder of the deployment to minimize the chance of any further disruptions to the ADCP.
Id: 1554
By: wingardc
|
|
CE09OSSM-RID26-01-ADCPTC000 Method: telemetered Stream: adcp_config |
2/9/19, 7:00 PM |
Started to see evidence of random binary encoded data in the ADCP record. In the past, this has been evidence of electronic noise on the serial lines connecting the instrument to the data logger adversely affecting the behavior of the instrument. We have disabled the data logger port for the remainder of the deployment to minimize the chance of any further disruptions to the ADCP.
Id: 1555
By: wingardc
|
|
CE09OSSM-RID26 Method: telemetered |
4/27/20, 3:40 PM |
We are experiencing an intermittent failure of communication between the systems on the NSIF and the buoy. While the systems on the NSIF are operating, due to a change in the telemetry system, only a finite backlog of data is telemetered to shore. As a result, when communications are restored, some of the data backlog may be missing and there may be gaps in the record. Id: 2183 By: wingardc |
|
CE09OSSM Method: telemetered |
5/9/20, 8:40 PM | 5/10/20, 8:00 PM |
Due to a bug in the mooring telemetry system, data during this time range was not telemetered to shore. It was recorded on the mooring and instruments and will be available in the recovered data streams.
Id: 2182
By: wingardc
|