(manual loading of LTA data into CODAS database, followed by postprocessing)
=======================================================
(1) find out information about the data
starting in ps0918_ltaproc, run this command:
vmdas_info.py --logfile lta_info.txt os ../../vmdas_data/ps0918/*LTA
The output says:
- 3 files, all have data
- averaging length: 300sec
- instrument frequency 75
- pingtypes: bb pings
- bottom track was on for part of the cruise
- beam angle 30 (normal for OS75)
- transducer angle (EA) 1.18
- messages available and what was used:
N1R HEHDT <-- VmDAS primary heading
N2R GPGGA
N2R GPHDT
N2R PASHR,AT2 <-- VmDAS backup heading
N2R PASHR,ATT
N2R PASHR,POS
N3R GPGGA <-- VmDAS primary position
N3R GPGLL
(2) set up processing directory:
adcptree.py os75bb_manual_lta --datatype lta
(3) Look at vmdas_info.py again and note:
- what kind of pings
- averaging length
- are filenames sorted in chronological order?
- what was the heading source?
Start a text file "os75bb_lta.txt" adjacent to the processing directory,
"os75bb_lta" and put this information in it:
--> these are 'bb' pings
--> averaged over 300sec
--> frequency is 75kHz, so "sonar" os "os75bb"
--> primary heading was HEHDT
--> there is an Ashtech, used as secondary heading
(4) Change directories to ADCP processing directory just created.
All the rest of the work (except for editing the text file)
will be done in this directory
cd os75bb_manual_lta
(5) create a quick_adcp.py control file
create a quick_adcp.py control file
windows:
- you can create q_py.cnt with an editor to have the
parts between (or including) the comments
- it may be easier to call it "q_py.txt" to avoid
fighting with your editor, which may try to set the suffix
unix: this example is written as a bash "heredoc" for
cut-and-past ease, but you can create q_py.cnt with
an editor to have the parts between (or including)
the comments
cat << EOF > q_py.cnt
##### q_py.cnt is
### python processing
--yearbase 2009 ## required, for decimal day conversion
## (year of first data)
--cruisename ps0918 ## always required; used for titles
--dbname aship ## database name; in adcpdb. eg. a0918
--datatype lta ## datafile type
--sonar os75bb ## instrument letters, frequency, [ping]
--ens_len 300 ## specify correct ensemble length
--pgmin 30
--datadir ../../../vmdas_data/ps0918 ##use this option to avoid
## copying or linking files
#### end of q_py.cnt
EOF
(6) run quick_adcp.py:
quick_adcp.py --cntfile q_py.cnt --auto
(7) Check calibrations
**watertrack**
------------
Number of edited points: 2 out of 2
amp = 1.0040 + 0.1053 (t - 264.8)
phase = 1.42 + 15.5789 (t - 264.8)
median mean std
amplitude 1.0040 1.0040 0.0085
phase 1.4200 1.4200 1.2558
------------
codaspy:(os75bb_LTA.calibrated)-PY3$ catbt
**bottomtrack**
------------
unedited: 36 points
edited: 33 points, 2.0 min speed, 2.5 max dev
median mean std
amplitude 0.9998 0.9998 0.0025
phase 1.3538 1.5970 0.5428
------------
(8) apply rotation correction (no scale factor necessary)
(all in one line)
quick_adcp.py --steps2rerun rotate:navsteps:calib --rotate_angle 1.5 --auto
**bottomtrack**
------------
unedited: 37 points
edited: 33 points, 2.0 min speed, 2.5 max dev
median mean std
amplitude 0.9995 0.9998 0.0026
phase -0.1377 0.0900 0.5427
------------
- this is "close enough" to allow editing at this point
(9) edit bad data
cd edit
gautoedit.py
# apply editing:
cd ..
quick_adcp.py --steps2rerun apply_edit:navsteps:calib --auto
(10) make web plots
quick_web.py --interactive
- view with a browser, look at webpy/index.html
(11) extract data
quick_adcp.py --steps2rerun matfiles --auto
adcp_nc.py adcpdb contour/os75bb ps0918_demo os75bb
done with processing.
Add cruise_info.txt to the top of this file.
Edit with correct info
