Direct Covariance Flux

Reference Designator
GI01SUMO-SBD12-08-FDCHPA000
Review Status
Review Complete
Note
Only recovered_inst data were downloaded and analyzed due to issues with calculating telemetered data (see annotations).
Depth
-5m
Class
FDCHP (Direct Covariance Flux)
Make / Model
WHOI / DCFS

Dataset Reviews Last processed:

QC Check Info
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_inst / Complete
2 recovered_inst / Complete
3 recovered_inst 401 238 0 0 2 51 67,433,857 -5 / 1 2 2 Complete
4 recovered_inst / Complete
Data Ranges Review Images

Test Notes

  1. pass unique test - ascending not tested
  2. no other streams for comparison

Data Coverage

Deployment: 1234
59%

Lat/Lon Differences (km)

Deployment: 1234
3 0.00

System Annotations

Metadata Start Date End Date Comment
GI01SUMO-SBD12-08-FDCHPA000
9/10/14, 2:50 PM 7/18/16, 8:00 PM

Sonic temperature bugs: general slow response problem leading to errors of +/- 6 degrees from ambient, and an additional nonlinear error in the slow response when the ambient temperature is between -5 and 5 degrees. The fast response (> 1 Hz) of these sensors is still accurate. Therefore, flux measurements using the detrended temperature data should still be valid. w bug: positive vertical velocities w output by the anemometer need to be multiplied by 1.166; negative vertical velocities need to be multiplied by 1.289 (Redmine 11645)

Id: 73 By: lgarzio
Flag: suspect Exclude: No

GI01SUMO-SBD12-08-FDCHPA000
Method: telemetered
Stream: fdchp_a_dcl_instrument
9/10/14, 2:50 PM 8/9/19, 4:04 AM

UPDATED, 2019-11-07: Per communication with the instrument subject matter expert, the onboard processing error applies only to the motion-corrected wind speed and flux calculations. Those parameters are marked here with a QC Flag = "fail". All other measurements are considered to be good. Users should only use the motion-corrected wind speed and flux data from the recovered instrument data stream. * The telemetered FDCHP data contains an onboard processing error that makes the motion-corrected wind speed and flux data unusable. The instrument subject matter expert is being consulted, and the algorithms are under review. Only the processed, recovered data should be used. For further questions please email help@oceanobservatories.org.

Id: 1375 By: swhite
Flag: fail Exclude: No

GI01SUMO-SBD12-08-FDCHPA000
9/10/14, 2:50 PM 8/22/15, 7:00 AM

Deployment 1: Recovered_instrument data not available - instrument was lost.

Id: 624 By: lgarzio

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-SBD12-08-FDCHPA000
8/15/15, 3:22 PM 7/18/16, 8:00 PM

Deployment 2: No recovered_instrument data available for this deployment.

Id: 1399 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-SBD12-08-FDCHPA000
Method: recovered_inst
Stream: fdchp_a_instrument_recovered
7/10/16, 1:44 PM

There are errors in the calculations of the recovered_instrument L1 and L2 data products (motion-corrected wind speeds, sonic temperature, and flux data products). This issue is under investigation (Redmine 13402).

Id: 1396 By: lgarzio

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
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-SBD12-08-FDCHPA000
6/8/18, 1:21 PM 8/9/19, 4:04 PM

Deployment 5: Instrument damaged during deployment no telemetered or recovered data are expected.

Id: 1449 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

Review Notes

Metadata Start Date End Date Comment
GI01SUMO-SBD12-08-FDCHPA000

Re annotation ID 1375 for this instrument - the equivalent annotation on CE02SHSM-SBD12-08-FDCHPA000 (ID 1373) was updated by wingardc: "UPDATED, 2019-02-05: Per communication with the instrument subject matter expert, the onboard processing error applies only to the motion-corrected wind speed and flux calculations. Those parameters are marked here with a QC Flag = "fail". All other measurements are considered to be good. Users should only use the motion-corrected wind speed and flux data from the recovered instrument data stream." This information presumably also applies to this instrument and should be communicated to users.

By Lori Garzio, on 6/7/19

GI01SUMO-SBD12-08-FDCHPA000

There are no global ranges in the system for this instrument for fdchp_a_fluxhot, fdchp_a_fluxmom_alongwind, and fdchp_a_fluxmom_crosswind

By Lori Garzio, on 6/7/19

GI01SUMO-SBD12-08-FDCHPA000
Deployment: 3

Data arrays are all fill values for fdchp_a_tmpatur, fdchp_a_windtur_north, fdchp_a_windtur_up, fdchp_a_windtur_west, fdchp_a_fluxhot, fdchp_a_fluxmom_alongwind, fdchp_a_fluxmom_crosswind (Redmine 13402). There are several errors listed in the computed_provenance section of the provenance.json files (one example file attached). When this issue is resolved annotation ID 1396 should be updated.

By Lori Garzio, on 6/7/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