Level 3 data (velocity profilers): Difference between revisions
Line 141: | Line 141: | ||
| stationarity_testing | | stationarity_testing | ||
| Any testing done on the segment to verify stationarity? | | Any testing done on the segment to verify stationarity? | ||
| {{FontColor|fg=white|bg=red|text=To be revisited once testing begins}} | | {{FontColor|fg=white|bg=red|text=To be revisited once testing begins}}. Tentatively refer to [https://bitbucket.org/efm_cb/netcdf/src/master/TestData/adcp_atomix_metada.yml demo yaml] file. | ||
|- | |- | ||
| noise_testing | | noise_testing |
Revision as of 17:18, 16 December 2021
Page status: Draft | |
---|---|
Author(s): | Cynthia |
Reviewer(s): | |
Comment: |

The required dimensions and variables for the structure-function processing level within NetCDF ATOMIX format for velocity ADCP measurements are described below. This NetCDF group contains the structure function (DLL) calculated as a function of the along-beam separation for the available/usable ADCP bins.
Dimensions
Short name | Standard name | Dimensions | Comments |
---|---|---|---|
TIME | time | TIME | Units in Days since 1950-01-01T00:00:00Z. Provide a bounds attribute to designate the variable containing the limits of each segment (see CF-compliant example). |
R_DIST | distance_from_sensor_along_beams | R_DIST | Along-beam bin centre distance (in meters) from the transducer |
R_DEL | along-beam_separation_distance_
at_which_structure_function_is_evaluated |
R_DEL | Estimated from bin sizes and theta in Level 2 qaqc variables |
N_BEAM | unique_identifier_for_each_beam | N_BEAM | Array of 1 to number of beams (3 to 5 typically) |
Optional dimensions for 5-beam ADCP | |||
R_DIST5 | distance_from_sensor_along_beam_5 | R_DIST5 | Along-beam bin centre distance (in meters) from the transducer for the 5th vertical beam |
R_DEL5 | along-beam_separation_distance_
at_which_structure_function_is_evaluated_in_beam_5 |
R_DEL5 | Estimated from bin sizes and theta in Level 2 qaqc variables |
Variables
Short name | Standard name | Dimensions | Comment |
---|---|---|---|
DLL | second_order_structure_function
_instrument_in_each_beam |
TIME, R_DIST, R_DEL, N_BEAM | Differences in velocities squared have been time-averaged (units of m2/s2). |
DLL_FLAGS | status_flags | TIME, R_DIST, R_DEL, N_BEAM | To be linked, when boolean flags defined |
DLL_N | number_of_velocity_difference_squared_observations_
averaged_in_DLL |
TIME, R_DIST, R_DEL, N_BEAM | Measure the number of available measurements in each segment i.e., data quality. |
N_SEGMENT | unique_identifier_for_each_segment_
in_the_entire_available_timeseries |
TIME | Enables backtracking to previous processing level |
BURST_NUMBER [math]\displaystyle{ \dagger\dagger }[/math] | unique_identifier_for_each_burst | TIME | Only required when measuring in burst-mode. Integers of 1, 2, etc to designate which burst the velocities are associated with. |
Optional dimensions for 5-beam ADCP | |||
DLL5 | second_order_structure_function_in_beam_5 | TIME, R_DEL5, R_DIST5 | Only necessary for 5-beam ADCP |
DLL5_FLAGS | status_flags | TIME, R_DEL5, R_DIST5 | Same as DLL_FLAGS but for the 5th vertical beam when present. |
DLL5_N | number_of_velocity_difference_squared_observations_
averaged_in_DLL5 |
TIME, R_DIST, R_DEL, N_BEAM | Measure the number of available measurements in each segment i.e., data quality. |
[math]\displaystyle{ \dagger\dagger }[/math] Variable required only when measuring in bursts e.g., 18 min of continuous measurements every hour. |
Group attributes (metadata)
This section describes attributes that may provide additional information about how the data was processed and manipulated at this stage.
Attribute name | Purpose | Suggested content | |
---|---|---|---|
processing_level | Boilerplate about the content of the NetCDF group. |
| |
dll_calculation_type | Specify differencing technique used to estimate DLL | Examples include:
| |
Optional group attributes [math]\displaystyle{ \ddagger }[/math] | |||
stationarity_testing | Any testing done on the segment to verify stationarity? | To be revisited once testing begins. Tentatively refer to demo yaml file. | |
noise_testing | Details of testing the noise levels, or if the signal comprises mostly of noise? | ||
comment (optional) | Any additional information pertinent to other users who test their algorithms against the file. |
Return to Level 2 quality controlled and segmented velocities