16
|
1 |
======================================================================
|
|
2 |
R E A D M E . P R O C E S S D A T A
|
|
3 |
doc: Tue May 15 18:49:00 2012
|
20
|
4 |
dlm: Fri Jul 12 12:07:38 2013
|
16
|
5 |
(c) 2012 A.M. Thurnherr
|
20
|
6 |
uE-Info: 118 71 NIL 0 0 72 75 2 8 NIL ofnI
|
16
|
7 |
======================================================================
|
|
8 |
|
|
9 |
=Overview=
|
|
10 |
|
|
11 |
This README describes how to obtain profiles of vertical shear and
|
|
12 |
velocity from CTD/LADCP data. It assumes that all of the required
|
|
13 |
software has been installed (see [README.Install]).
|
|
14 |
|
|
15 |
The re-implemented shear method software provides two commands:
|
|
16 |
|
|
17 |
[LADCPproc] This utility produces LADCP shear data from a raw ADCP
|
|
18 |
data file and the corresponding CTD time series.
|
|
19 |
Additionally, it can create profiles of acoustic
|
|
20 |
backscatter, as well as BT-referenced velocity
|
|
21 |
profiles near the seabed from downlooking ADCPs.
|
|
22 |
|
|
23 |
[LADCPintsh] This utility produces profiles of horizontal velocity
|
|
24 |
from the [LADCPproc] shear output. BT profiles (from
|
|
25 |
[LADCPproc] or from the LDEO_IX inversion software) or
|
|
26 |
SADCP profiles (manually constructed) can be used to
|
|
27 |
reference the velocity profiles.
|
|
28 |
|
|
29 |
For non-standard processing, the shear output from [LADCPproc] can be
|
|
30 |
post-edited before gridding, e.g. in order to filter data collected at
|
|
31 |
very shallow depths when the ADCP may be affected by the magnetic field
|
|
32 |
of the surface vessel (see [README.PostEdit] for details).
|
|
33 |
|
|
34 |
|
|
35 |
=DATA REQUIREMENTS=
|
|
36 |
|
|
37 |
ADCP DATA: The software reads binary RDI BB ADCP files from both down-
|
|
38 |
and upward-looking ADCPs. Clock setting of the ADCP is not important.
|
|
39 |
|
|
40 |
CTD DATA: LADCP processing requires a CTD-derived time series of
|
17
|
41 |
pressure, temperature and salinity. Optionally, it is recommended that
|
|
42 |
an elapsed time field is supplied. A time resolution of 1Hz is
|
|
43 |
recommended. The software is capable of reading both binary and ASCII
|
|
44 |
SeaBird .cnv files with lat/lon information in the header and with the
|
|
45 |
following fields: timeS, prDM, t090C and/or t190C, sal00 and/or sal11.
|
|
46 |
Alternatively, the CTD time series can be supplied as an arbitrary
|
|
47 |
headerless ASCII CTD file with the same information, as described in
|
|
48 |
[LADCPproc.defaults].
|
16
|
49 |
|
|
50 |
|
|
51 |
=CALCULATE LADCP SHEAR PROFILE=
|
|
52 |
|
|
53 |
The following simple example shows how to create separate shear profiles
|
|
54 |
from an upward- and a downward-looking ADCP, as well as a BT-referenced
|
|
55 |
velocity profile near the seabed:
|
|
56 |
|
|
57 |
Input files:
|
|
58 |
001DL000.000 downlooker ADCP file
|
|
59 |
001UL000.000 uplooker ADCP file
|
|
60 |
001.cnv CTD file
|
|
61 |
|
|
62 |
LADCPproc -p 001DL.sh -b 001.BT 001DL000.000 001.cnv > /dev/null
|
|
63 |
- this example creates two files, 001DL.sh (shear profiles) and
|
|
64 |
001.BT (bottom-track data)
|
|
65 |
- the default output (STDOUT) from [LADCPproc] is a list of
|
|
66 |
valid shear samples, which is ignored (sent to /dev/null) in
|
|
67 |
this example
|
|
68 |
- it is recommended that the diagnostic output (STDERR) is
|
|
69 |
captured in a log file; refer to the manual of your shell on
|
|
70 |
how to accomplish this
|
|
71 |
|
|
72 |
LADCPproc -p 001UL.sh 001UL000.000 001.cnv > /dev/null
|
|
73 |
- this example creates one file, 001UL.sh (shear profiles)
|
|
74 |
|
|
75 |
|
|
76 |
In this simple example, processing is carried out with standard
|
|
77 |
parameters. Some of the important parameters can be modified with
|
|
78 |
[LADCPproc] options, which are listed when [LADCPproc] is ran without
|
|
79 |
input parameters. The following are the most important [LADCPproc]
|
|
80 |
options:
|
|
81 |
-d generate diagnostic output (recommended)
|
|
82 |
-r use RDI BT data instead of echo amplitudes to find
|
|
83 |
seabed and determine CTD velocity
|
|
84 |
-o <dz> output grid resolution (defaults to 5m)
|
|
85 |
-p <shearprof> generate shear profile output
|
|
86 |
-b <btm_track> generate BT output
|
|
87 |
-s <setup_file> read additional non-default processing parameters
|
|
88 |
from <setup_file>
|
|
89 |
|
|
90 |
However, there are many more processing parameters than can be modified
|
|
91 |
with options --- a full list with comments can be found in
|
|
92 |
[LADCPproc.defaults]. To change any of the default parameter values,
|
|
93 |
create a perl-file with variable assignments (see [LADCPproc.defaults]
|
|
94 |
for syntax) and use the -s <setup_file> option in [LADCPproc].
|
|
95 |
|
|
96 |
|
|
97 |
=CALCULATE LADCP VELOCITY PROFILE=
|
|
98 |
|
|
99 |
Given the output from the above steps, different full-depth velocity
|
|
100 |
profiles can be produced as follows:
|
|
101 |
|
|
102 |
LADCPintsh 001DL.sh > 001DL.bc
|
|
103 |
- this creates baroclinic (zero vertical mean) velocity profile
|
|
104 |
from the DL shear data
|
|
105 |
|
|
106 |
LADCPintsh -r 001.BT 001DL.sh > 001DL.vel
|
|
107 |
- this creates a BT-referenced absolute velocity profile from
|
|
108 |
the DL shear data
|
|
109 |
|
20
|
110 |
LADCPintsh -r 001.BT 001UL.sh > 001UL.vel
|
|
111 |
- this creates a BT-referenced absolute velocity profile from
|
|
112 |
the UL shear and the DL BT data
|
|
113 |
- note that no -u is required in this case!
|
|
114 |
|
16
|
115 |
LADCPintsh -r 001.BT -u 001UL.sh 001DL.sh > 001.vel
|
|
116 |
- this creates a BT-referenced absolute velocity profile from
|
|
117 |
the combined DL/UL shear data
|
20
|
118 |
- note that -u is only required if both UL and DL data are used
|
16
|
119 |
|
|
120 |
It is also possible to use SADCP data to reference the velocity
|
|
121 |
profiles, although it is up to the user to create an input data file
|
|
122 |
in one of the supported formats. Note that it is *not* possible to use
|
|
123 |
multiple simultaneous referencing constraints with [LADCPintsh].
|
|
124 |
|
|
125 |
The following are common [LADCPintsh] options:
|
|
126 |
-u use uplooker shear (in addition to downlooker,
|
|
127 |
which is always used)
|
|
128 |
-r <file> use reference-velocity data to reference baroclinic
|
|
129 |
velocity profiles; the following file formats
|
|
130 |
are supported 1) bottom-track output produced by
|
|
131 |
the -b option of [LADCPproc], 2) bottom-track
|
|
132 |
output produced by the LDEO processing software
|
|
133 |
(.bot files). SADCP data can be used, too, but
|
|
134 |
they have to be supplied in one of the two
|
|
135 |
supported file formats.
|
|
136 |
-n <samp> set minimum number of shear samples to use
|
|
137 |
-m <samp> set minimum BT samples to use
|
|
138 |
|
|
139 |
|
|
140 |
=QUALITY CHECKS=
|
|
141 |
|
|
142 |
After processing, the quality of the resulting profiles must be
|
|
143 |
assessed. The following steps are recommended:
|
|
144 |
|
|
145 |
1) Compare the down- and up-cast profiles of velocity. Vertical
|
|
146 |
velocity is particularly useful in this context as problematic casts
|
|
147 |
often show a striking "X" pattern.
|
|
148 |
|
|
149 |
2) Inspect the standard deviation profiles of the binned shear and
|
|
150 |
determine (by comparison with similar data) whether the standard
|
|
151 |
deviations have the correct magnitude.
|
|
152 |
|
|
153 |
3) Calculate and compare independent solutions from the uplooker and
|
|
154 |
downlooker data. This will only validate the baroclinic velocities (i.e.
|
|
155 |
the vertical shear).
|
|
156 |
|
|
157 |
4) Compare to velocity profiles calculated with different software (e.g.
|
|
158 |
with the LDEO_IX velocity inversion code).
|