Raw data review (QA1): Difference between revisions

From Atomix
Yuengdjern (talk | contribs)
No edit summary
Yuengdjern (talk | contribs)
No edit summary
Line 15: Line 15:
#* Velocities outside expected distribution
#* Velocities outside expected distribution
</div>
</div>
= Significant instrument motion and orientation =
== Significant instrument motion and orientation ==
<div class="mw-collapsible mw-collapsed" id="motion" data-collapsetext="Collapse" data-expandtext="Expand">
<div class="mw-collapsible mw-collapsed" id="motion" data-collapsetext="Collapse" data-expandtext="Expand">
#* High variability in pitch, heading and roll
#* High variability in pitch, heading and roll

Revision as of 09:40, 16 November 2021

The objective of the raw data review is to ensure that the velocity data used for the calculation of the structure functions are of good quality before proceeding with the turbulence analysis. Bad data are typically identified from the velocity data themselves and other ancillary data (e.g. correlations). It is recommended that velocity data should be flagged if the following are observed:

Data quality is poor

    • Low correlation values
    • Echo intensity anomalies
    • Low percent good values
    • Data return rate varies

Unrealistic velocity values

    • Evidence of phase wrapping
    • Velocities outside nominal measurement range
    • Velocities outside expected distribution

Significant instrument motion and orientation

    • High variability in pitch, heading and roll
    • Orientation deviates from expected values

There is wave or periodic motion

    • Periodic motion at wave frequencies observed in velocity data

Velocity shear is too large

    • earth velocities indicate significant horizontal shear

Stationary assumption may be violated

    • variance of velocity bursts shows spatial or temporal trends

Stratification is too large

    • Temperature and salinity (if available) indicate local stratification

Next step: Compute structure functions and dissipation estimates

Previous step: Deployment

Return to ADCP Flow Chart front page