Example forward-difference: Difference between revisions

From Atomix
No edit summary
No edit summary
Line 11: Line 11:
For bin 1 the squared velocity difference can be evaluated for <math>1\leqslant\delta\leqslant29</math>, whilst for bin 2 it is restricted to <math>1\leqslant\delta\leqslant28</math>, reducing by 1 with each bin, so that for bin 29, it can only be evaluated for <math>\delta=1</math> and there are no options for bin 30.  This is summarised as follows:
For bin 1 the squared velocity difference can be evaluated for <math>1\leqslant\delta\leqslant29</math>, whilst for bin 2 it is restricted to <math>1\leqslant\delta\leqslant28</math>, reducing by 1 with each bin, so that for bin 29, it can only be evaluated for <math>\delta=1</math> and there are no options for bin 30.  This is summarised as follows:


[[File:Forward difference.png|frameless|center]]
[[File:Forward diff.png|frameless|center|1000px]]
 
The mean is then taken across the 300 profiles in the data segment e.g.
 
:<math>D(1,1) = \sum_{t=1}^{300}D(1,\delta,t)</math>

Revision as of 17:24, 12 November 2021

Consider the example of an ADCP with a beam angle of 20, configured with a vertical bin size of 10 cm, recording profiles at 1 second intervals with a data segment length of 300 seconds. The Level 1 QC of the data identified that good data was typically returned from bins 1 to 30.

The velocity data from a single beam for a single data segment can therefore be visualised as:

The square of the velocity difference between bins separated by δ bins is then evaluated for each t. So for t1, bin 1 and δ=1, we get:

D(1,1,1)=[v(1,1)v(2,1)]2

For bin 1 the squared velocity difference can be evaluated for 1δ29, whilst for bin 2 it is restricted to 1δ28, reducing by 1 with each bin, so that for bin 29, it can only be evaluated for δ=1 and there are no options for bin 30. This is summarised as follows:

The mean is then taken across the 300 profiles in the data segment e.g.

D(1,1)=t=1300D(1,δ,t)