Direct Covariance Flux

Reference Designator
GS01SUMO-SBD12-08-FDCHPA000
Start Depth
-5
End Depth
-5
Location
Buoy Tower
Current Status
Review Complete
Class
FDCHP (Direct Covariance Flux)
Series
FDCHP-A
Science Discipline
Physical
Make
WHOI
Model
DCFS
M2M Example
https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/GS01SUMO/SBD12/08-FDCHPA000/metadata
Method Data Stream Content Type
recovered_host fdchp_a_dcl_instrument_recovered Data Products Report M2M Stats Science
recovered_inst fdchp_a_instrument_recovered Data Products Report M2M Stats Science
telemetered fdchp_a_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
1 Review AT-26-29 02/18/2015 12/27/2015 CGMGS-01SUMO-00001 CGINS-FDCHPA-43401 -54.4082 -89.3576 -6 4611
2 Review NBP-15-11 12/14/2015 12/12/2016 CGMGS-01SUMO-00002 CGINS-FDCHPA-44901 -54.4041 -89.2069 -6 4588
3 Review NBP16-10 11/25/2016 12/09/2018 CGMGS-01SUMO-00003 CGINS-FDCHPA-43401 -54.4076 -89.3567 -6 4612
4 Review DY096 12/04/2018 01/20/2020 CGMGS-01SUMO-00004 CGINS-FDCHPA-74102 -54.4072 -89.206 -6 4589
Metadata Start Date End Date Comment
GS01SUMO-SBD12-08-FDCHPA000

Re annotation ID 1376 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

GS01SUMO-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

GS01SUMO-SBD12-08-FDCHPA000

Data arrays are all fill values for every deployment 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 1395 should be updated.

By Lori Garzio, on 6/7/19

GS01SUMO
Deployment: 3

Annotation ID 834 needs to be updated: "Deployment 3: Recovery of the mooring was planned during the NBP 17-09 cruise (Nov - Dec 2017) but not completed due to adverse weather conditions. Recovery options are pending. Instruments that are still operational are likely reaching (or have surpassed) their deployment lifespan."

By Lori Garzio, on 1/14/19

New Note

Metadata Start Date End Date Comment
GS01SUMO-SBD12-08-FDCHPA000
2/18/15, 4:06 PM 12/11/16, 7:00 PM

Deployments 1 and 2: 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: 75 By: lgarzio
Flag: suspect Exclude: No

GS01SUMO-SBD12-08-FDCHPA000
Method: telemetered
Stream: fdchp_a_dcl_instrument
2/18/15, 4:06 PM 1/20/20, 5:01 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: 1376 By: swhite
Flag: fail Exclude: No

GS01SUMO-SBD12-08-FDCHPA000
2/18/15, 4:06 PM 12/27/15, 6:20 AM

Deployment 1: Recovered_instrument data not available for this deployment.

Id: 631 By: lgarzio

GS01SUMO-SBD12
12/13/15, 7:00 PM 12/11/16, 7:00 PM

Upon recovery of deployment 2, damage to some components of the surface buoy were noted (e.g., FDCHP was bent, the tops of the METBK-PRC and FleetBroadBand antenna were missing).

Id: 95 By: lgarzio

GS01SUMO-SBD12-08-FDCHPA000
Method: recovered_inst
Stream: fdchp_a_instrument_recovered
12/14/15, 3:20 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: 1395 By: lgarzio

GS01SUMO-SBD12-08-FDCHPA000
12/14/15, 3:20 PM 12/12/16, 2:58 AM

Deployment 2: Instrument bent at recovery.

Id: 755 By: lgarzio

GS01SUMO-SBD12-08-FDCHPA000
6/11/17, 8:00 PM 12/8/18, 11:42 PM

Deployment 3: The FDCHP is known to have ceased sampling on 2017-06-12. No data are expected after this date.

Id: 2147 By: cdobson
Flag: not_operational Exclude: No

GS01SUMO
12/8/17, 7:00 PM 12/8/18, 11:42 PM

Deployment 3: *UPDATED 2020-04-28: This mooring was recovered 2018-12-09 which was a year later than originally intended. Some instruments were able to continue sampling for the extended deployment.* Recovery of the mooring was planned during the NBP 17-09 cruise (Nov - Dec 2017) but not completed due to adverse weather conditions. Recovery options are pending. Instruments that are still operational are likely reaching (or have surpassed) their deployment lifespan.

Id: 834 By: lgarzio

GS01SUMO-SBD12-08-FDCHPA000
12/13/18, 7:00 PM 1/20/20, 5:01 AM

UPDATED 2020-06-23: On recovery anemometer was found to have a bent shaft and missing one of the transducer tines. * Deployment 4: This instrument failed on deployment 12/14/2018. No telemetered or recovered data expected.

Id: 1591 By: cdobson