ADCP Hardware: Difference between revisions
From Atomix
Yuengdjern (talk | contribs) Created page with "== Hardware & instrument configuration considerations == # Available Power and Storage #: What battery pack equivalent you have, what storage you have # Motion contr..." |
No edit summary |
||
| Line 1: | Line 1: | ||
== Hardware & instrument configuration considerations == | == Hardware & instrument configuration considerations == | ||
# | # Environmental conditions | ||
# | ## Ensure velocity range is sufficient for anticipated background flow, tides, surface waves and internal waves | ||
## Select spatial range (number of bins and bin size) consistent with eddy inertial range Ozmidov length given anticipated stratification and turbulence levels | |||
# Velocity measurements | |||
## Record in Beam coordinates | |||
## Maximise velocity accuracy whilst minimising averaging (pings per ensemble) | |||
## Select <math>\varepsilon<\math> estimate observation period (period over which structure function is evaluated) consistent with fundamental requirement of stationary statistics | |||
## Maximise the number of profiles (ensembles) per <math>\varepsilon<\math> estimate observation period to improve statistics | |||
# Motion control during deployment | # Motion control during deployment | ||
## Sufficient buoyancy on frame to hold position well, but not obstructing beam path | ## Sufficient buoyancy on frame to hold position well, but not obstructing beam path | ||
## Consider also nearby moorings and frames to reduce/avoid interference. | ## Consider also nearby moorings and frames to reduce/avoid interference. | ||
## If | ## If the mooring can move, collect depth (pressure sensor on ADCP or adjacent instrument) and orientation data (heading, pitch and roll) at the same frequency as the velocity profiles data. Consider high resolution add-on’s such as AHRS. | ||
## | ## Mooring design should consider impact of knock-down on location of observations in the water column | ||
## Vertical beam in different mode such as alternating high resolution repetition rate? | ## Vertical beam in different mode such as alternating high resolution repetition rate? | ||
# | # Power and Storage for self-contained deployments | ||
## | ## Planned deployment duration | ||
# | ## Manufacturer’s expected energy consumption versus battery capacity at expected temperature | ||
## | ## Manufacturer’s expected memory required per recorded profile (ensemble) versus available memory | ||
Return to [[Deployment]] | Return to [[Deployment]] | ||
Revision as of 12:19, 9 November 2021
Hardware & instrument configuration considerations
- Environmental conditions
- Ensure velocity range is sufficient for anticipated background flow, tides, surface waves and internal waves
- Select spatial range (number of bins and bin size) consistent with eddy inertial range Ozmidov length given anticipated stratification and turbulence levels
- Velocity measurements
- Record in Beam coordinates
- Maximise velocity accuracy whilst minimising averaging (pings per ensemble)
- Select <math>\varepsilon<\math> estimate observation period (period over which structure function is evaluated) consistent with fundamental requirement of stationary statistics
- Maximise the number of profiles (ensembles) per <math>\varepsilon<\math> estimate observation period to improve statistics
- Motion control during deployment
- Sufficient buoyancy on frame to hold position well, but not obstructing beam path
- Consider also nearby moorings and frames to reduce/avoid interference.
- If the mooring can move, collect depth (pressure sensor on ADCP or adjacent instrument) and orientation data (heading, pitch and roll) at the same frequency as the velocity profiles data. Consider high resolution add-on’s such as AHRS.
- Mooring design should consider impact of knock-down on location of observations in the water column
- Vertical beam in different mode such as alternating high resolution repetition rate?
- Power and Storage for self-contained deployments
- Planned deployment duration
- Manufacturer’s expected energy consumption versus battery capacity at expected temperature
- Manufacturer’s expected memory required per recorded profile (ensemble) versus available memory
Return to Deployment
