Direct Covariance Flux

Reference Designator
Review Status
Review Complete
Only recovered_inst data were downloaded and analyzed due to issues with calculating telemetered data (see annotations).
FDCHP (Direct Covariance Flux)
Make / Model

Dataset Reviews Last processed: 5/24/19, 2:22 PM

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 174 7 0 163 1 4 1,312,118 -5 / 1 1 Complete
3 recovered_inst 135 135 0 0 0 0 36,944,151 -5 / 2 1 1 Complete
4 recovered_inst 209 119 0 89 0 0 32,444,391 -5 / 2 1 1 Complete
5 recovered_inst 179 15 0 163 0 0 3,879,834 -5 / 1 1 Complete
6 recovered_inst / Complete
7 recovered_inst 176 176 0 0 0 0 43,467,415 -5 / 2 1 1 Complete
Data Ranges Review Images

Test Notes

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

Data Coverage

Deployment: 134567

Lat/Lon Differences (km)

Deployment: 134567
1 0.00
3 0.290.00
4 0.110.400.00

System Annotations

Metadata Start Date End Date Comment
Method: recovered_inst
Stream: fdchp_a_instrument_recovered
4/2/15, 4:15 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: 1398 By: lgarzio

4/2/15, 5:00 PM 9/27/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: 77 By: lgarzio
Flag: suspect Exclude: No

Method: telemetered
Stream: fdchp_a_dcl_instrument
4/2/15, 5:20 PM

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. * 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

Id: 1373 By: wingardc
Flag: fail Exclude: No

6/7/19, 1:30 AM 10/22/19, 11:32 AM

For reasons the vendor has been unable to determine, the instrument may suddenly stop recording any data. This failure mode has been observed several times. No further data will be available from this sensor for the remainder of the deployment.

Id: 1681 By: wingardc
Flag: not_operational Exclude: No

Method: telemetered
1/13/20, 1:45 PM

During a large storm event on 2020-01-11, power from the wind turbines was lost. This is the primary means of recharging the battery system on the mooring. With the loss of recharging power, we have had to implement a conservative power model. These systems and instruments have been disabled for the foreseeable future, and no further data will collected from them.

Id: 1900 By: wingardc
Flag: not_operational Exclude: No

Review Notes

Metadata Start Date End Date Comment

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


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 1398 should be updated.

By Lori Garzio, on 6/7/19


The missing data for the majority of deployments 1 and 5 should be annotated.

By Lori Garzio, on 6/7/19

Deployment: 6

recovered_inst data for deployment 6 are not available for download. These data should be available or annotated to explain why they aren't available.

By Lori Garzio, on 6/7/19

New Note