| Method | Data Stream | Content | Type | |
|---|---|---|---|---|
| recovered_host | ctdbp_p_dcl_instrument_recovered | Data Products | Report M2M Stats | Science |
| recovered_inst | ctdbp_cdef_instrument_recovered | Data Products | Report M2M Stats | Science |
| telemetered | ctdbp_p_dcl_instrument | Data Products | Report M2M Stats | Science |
| Deployment | Cruise | Start Date | Stop Date | Mooring Asset | Node Asset | Sensor Asset | Latitude | Longitude | Deployment Depth | Water Depth |
|---|---|---|---|---|---|---|---|---|---|---|
| 2 Review | NBP-15-10 | 11/14/2015 | 11/08/2016 | CGMGA-01SUMO-00002 | CGINS-CTDBPP-50076 | -42.9246 | -42.5867 | 130 | 5188 | |
| 3 Review | NBP16-09 | 10/27/2016 | 01/14/2018 | CGMGA-01SUMO-00003 | CGINS-CTDBPP-50158 | -42.9204 | -42.4409 | 130 | 5175 |
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
GA01SUMO-RII11-02-CTDBPP033 |
If more details are known, annotation IDs 416 and 417 should be updated to include why the instruments failed during deployments 2 and 3. By Lori Garzio, on 2/7/19 |
||
|
GA01SUMO-RII11-02-CTDBPP033 |
There are no global ranges in the system for recovered_inst ctdbp_cdef_instrument_recovered ctdbp_seawater_temperature, ctdbp_seawater_pressure, and ctdbp_seawater_conductivity. By Lori Garzio, on 3/14/19 |
||
|
GA01SUMO-RII11 |
12/4/15, 12:00 AM | 3/14/16, 12:00 AM |
Deployment 2: The recovered_host data from the following instruments have the same 4 data gaps [['2015-12-04', '2015-12-14'], ['2016-01-06', '2016-01-11'], ['2016-02-05', '2016-02-10'], ['2016-03-11', '2016-03-14']]. These gaps should be annotated to explain why the data are missing, or gaps should be filled in if the data are available. [02-FLORDG031, 02-FLORDG032, 02-FLORDG033, 02-DOSTAD031, 02-DOSTAD032, 02-DOSTAD033] By Lori Garzio, on 2/11/19 |
|
GA01SUMO-RII11-02-CTDBPP033 Deployment: 2 |
1/31/16, 12:00 AM | 2/4/16, 12:00 AM |
Conductivity, salinity and density dropped suddenly, then returned to reasonable values. This appears to be a real event as it was captured by other CTDs on this mooring (GA01SUMO-RII11-02-CTDMOQ015, GA01SUMO-RII11-02-CTDBPP031, and GA01SUMO-RII11-02-CTDBPP032) By Lori Garzio, on 2/7/19 |
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
GA01SUMO |
3/15/15, 5:25 PM | 11/26/15, 5:08 AM |
Deployment 1: Buoy log files showed that seawater was first detected inside the buoy well on 3/26/2015. Both leak detectors showed increasing presence of water over the period of deployment. Upon recovery of the mooring, no external damage was visible and the buoy did not appear to be floating lower than normal. Id: 653 By: lgarzio |
|
GA01SUMO-RII11-02-CTDBPP033 |
5/22/16, 10:00 PM | 11/8/16, 5:10 AM |
Deployment 2: Instrument failed.
Id: 416
By: lgarzio
|
|
GA01SUMO-RII11-02-CTDBPP033 |
5/8/17, 5:46 AM | 5/8/17, 5:46 AM |
Deployment 3: Instrument failed.
Id: 417
By: lgarzio
|