CTD (80 m)

Reference Designator
GI01SUMO-RII11-02-CTDBPP032
Start Depth
80
End Depth
80
Location
Fixed on Inductive Wire
Current Status
Review Complete
Class
CTDBP (CTD Pumped)
Series
CTDBP-P
Science Discipline
Physical
Make
Sea-Bird
Model
SBE 16plus-IM V2
M2M Example
https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/GI01SUMO/RII11/02-CTDBPP032/metadata
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 AT-30-01 08/15/2015 07/19/2016 CGMGI-01SUMO-00002 CGINS-CTDBPP-50073 59.9436 -39.5737 80 2668
3 Review AR-07-01 07/10/2016 08/14/2017 CGMGI-01SUMO-00003 CGINS-CTDBPP-50137 59.9341 -39.4673 80 2691
4 Review AR21 08/05/2017 10/12/2017 CGMGI-01SUMO-00004 CGINS-CTDBPP-50074 59.9449 -39.5751 80 2659
5 Review AR30-03 06/08/2018 08/09/2019 CGMGI-01SUMO-00005 CGINS-CTDBPP-50076 59.9329 -39.4655 80 2693
6 Review AR35-05 08/05/2019 CGMGI-01SUMO-00006 CGINS-CTDBPP-50125 59.9451 -39.574 80 2664
Metadata Start Date End Date Comment
GI01SUMO-RII11-02-CTDBPP032

Annotation IDs 477 and 478 should be updated to explain why the instrument failed (if known).

By Lori Garzio, on 3/14/19

GI01SUMO-RII11-02-CTDBPP032

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

GI01SUMO-RII11-02-CTDBPP032
Deployment: 4

There should be an annotation in the system explaining why recovered_inst data are not available for deployment 4. According to the ingest csv, the instrument was damaged and data weren't recoverable.

By Lori Garzio, on 3/13/19

GI01SUMO-RII11-02-CTDBPP032
Deployment: 4
8/5/17, 7:00 PM 8/9/17, 12:00 AM

Several bad pressure data points - excluding from final statistics.

By Lori Garzio, on 3/14/19

GI01SUMO
Deployment: 4
10/12/17, 12:00 AM 6/14/18, 8:02 AM

The surface buoy detached from the mooring and the subsurface portion of the mooring fell to the seafloor (see annotation ID 102). Excluding all mooring data for this time range from final statistics.

By Lori Garzio, on 1/15/19

New Note

Metadata Start Date End Date Comment
GI01SUMO
2/14/15, 7:00 PM 8/21/15, 8:00 PM

Deployment 1: Status data sent from the buoy included leak detects in the buoy well, drop in battery voltage, and loss of wind turbine input. Upon recovery, the buoy was primarily intact but several instruments were damaged and/or missing. Ice build-up on the tower is speculated to be the cause for much of the damage. No telemetered or recovered_host data expected. Functional instruments could continue to collect data using internal battery power and storage cards.

Id: 46 By: lgarzio

GI01SUMO
1/26/16, 7:00 PM 7/18/16, 8:00 PM

Deployment 2: A period of violent weather caused power outages on multiple instruments. No telemetered or recovered_host data expected. Functional instruments could continue to collect data using internal battery power and storage cards. Upon recovery, the buoy well was flooded.

Id: 47 By: lgarzio

GI01SUMO-RII11-02-CTDBPP032
4/15/16, 5:00 PM 7/18/16, 8:00 PM

Deployment 2: Instrument failed.

Id: 477 By: lgarzio
Flag: not_operational Exclude: No

GI01SUMO
12/26/16, 7:00 PM 4/6/17, 8:00 PM

Deployment 3: Wind turbines were disabled due to evidence of ice build-up on the surface buoy tower. The platform's battery charge state declined steadily. As of 2017-01-15, all DCLs were shut down and the telemetry schedule was reduced to conserve power. Battery-powered instruments should continue to collect data. UPDATE 2017-04-07: With increasing daylight at this location, sufficient power was generated by solar panels to re-establish limited high-bandwidth telemetry and data transmission. UPDATE: at recovery, wind turbines were missing their hubs and blades, and one solar panel was missing.

Id: 121 By: lgarzio

GI01SUMO-RII11-02-CTDBPP032
2/10/17, 3:02 AM 8/14/17, 5:33 AM

Deployment 3: Instrument failed.

Id: 478 By: lgarzio
Flag: not_operational Exclude: No

GI01SUMO
8/5/17, 2:17 PM 6/14/18, 4:02 AM

Deployment 4: at 10:03 UTC on 12 October 2017 the Irminger Sea Surface Mooring stopped all communications. At recovery, the surface buoy was missing. The subsurface portion of the mooring had fallen to the seafloor and was recovered. CTDMOs, CTDBP-F, DOSTA, and ADCP instrumentation were full ocean depth rated and survived, although any recovered data available after 2017-10-12T10:03:00 are suspect. All other instrumentation imploded or flooded. The cause for the loss of the buoy is inconclusive.

Id: 102 By: lgarzio

GI01SUMO-RII11-02-CTDBPP032
Method: telemetered
4/30/19, 8:00 PM

Deployment 5: Communications to instrument began failing around 5/1/2019. Data quality is suspect after this date. Instrument may be collecting data on battery power, but it is unlikely.

Id: 1586 By: cdobson

GI01SUMO
6/19/19, 8:00 PM

Deployment 5: Battery voltage dropped below 24V. All DCLs were turned off. CPM1 was placed on a wake schedule. Data collection and telemetry will be irregular until voltage rebounds.

Id: 1625 By: cdobson

GI01SUMO
Method: telemetered
10/21/19, 8:00 PM

Deployment 6: *UPDATED 2020-04-27: As of 2020-02-21 data for most instruments are being telemetered again (via Iridium). A gap in telemetered data is expected between 2019-10-22 and 2020-02-21 and will not be backfilled but these data will be available upon recovery.*Both fleet broadband units have failed and no more telemetered data is expected at this time. Instruments are believed to be operating as normal and their data will be available upon recovery.

Id: 1743 By: cdobson