LAST CHANGED : 2019/10/11 23:23:39 CRUISE NAME(S) : pe2006 CRUISE DATES : 2019/09/23 to 2019/10/03 SHIP NAME : Pelican PORTS : Cocodrie, LA to Cocodrie, LA CHIEF SCIENTIST : K.Donohue DATABASE NAME : aship DATA FILES : pe2019_263_79026.raw to pe2019_275_79200.raw STATUS : to do done ------ ----------- averaged [ x ] redone afterwards to glue together 2 pieces loaded [ x ] NOTE: heading correction instrument exists NOTE: time-dependent heading corrections applied IN the ensembles (see cal/rotate/ens_hcorr.ang) check heading correction [ x ] calibration [ x ] edited [ x ] re-check heading correction [ x ] check editing [ x ] figures [ x ] INSTRUMENT : os75 ACQUISITION : PROGRAM : uhdas PROCESSING: : python LOGGING : PARAMETERS : BT : bottom track mode (on or off) SI : sampling interval or averaging period for ensemble (sec) NB : number of bins BL : bin length (m) TD : transducer depth (m) BK : blanking length (m) HO : heading offset applied by DAS (deg) HB : heading bias (deg) CRPH : compensation for roll-pitch-heading, 1:on, 0:off) yy/mm/dd hh:mm:ss BT SI NB BL TD BK HO HB CRPH 2019/09/21 22:04:07 off 300 60 16 3 8 1.25 0.00 0001 HEADING : PRIMARY : heading from gyro CORRECTION : heading correction from adu800 NOTE: time-dependent heading corrections applied IN the ensembles (see cal/rotate/ens_hcorr.ang) POSITIONS : gps positions from adu800 CALIBRATION : (check original processing parameters) additional rotation 0 final transducer angle is: (original transducer angle) - (rotate_angle) applied scale factor 1 additional scale factor (1.042) # new window requires scale factor COMMENTS : CTD wire interference in some stations : bubbles due to heavy seas : Experimental algorithm "uvship" applied to better account for lost pings in rough seas. See note below. PROCESSOR : J.Hummon --- processing parameters at the start ---------- ## (determined from "sonar"): model = os ## (determined from "sonar"): frequency = 75 ## (determined from "sonar"): instname = os75 ## (determined from "sonar"): pingtype = nb badbeam None beamangle 30 configtype python cruisename PE2006-furuno datatype uhdas dbname aship ens_len 300 fixfile aship.gps hcorr_inst adu800 pgmin 50 pingpref None proc_engine python ref_method refsm refuv_smoothwin 3 refuv_source nav sonar os75nb txy_file aship.gps xducer_dx 0 xducer_dy 0 yearbase 2019 ============================================ (1) check calibration catwt **watertrack** ------------ Number of edited points: 64 out of 68 amp = 1.0425 + 0.0003 (t - 270.0) phase = 0.01 + 0.0014 (t - 270.0) median mean std amplitude 1.0420 1.0425 0.0070 phase 0.0025 0.0079 0.3059 ------------ catxy **transducer-gps offset** ------------ guessing ADCP (dx=starboard, dy=fwd) meters from GPS positions from aship.gps calculation done at 2019/10/11 23:23:38 xducer_dx = 3.470764 xducer_dy = 0.717595 signal = 2451.405582 ------------ Apply a scale factor, and small tweak to gps location relative to the ship: quick_adcp.py --steps2rerun navsteps:calib:rotate --rotate_amplitude 1.042 --xducer_dx 3 --xducer_dy 1 --auto - Check again: catwt **watertrack** ------------ Number of edited points: 65 out of 69 amp = 1.0004 + 0.0002 (t - 270.0) phase = 0.02 + 0.0026 (t - 270.0) median mean std amplitude 0.9990 1.0004 0.0070 phase 0.0230 0.0233 0.3091 ------------ (python3) [jules@joules os75nb.adu800]$ catxy **transducer-gps offset** ------------ guessing ADCP (dx=starboard, dy=fwd) meters from GPS positions from aship.agt calculation done at 2020/11/23 23:46:24 xducer_dx = 1.018508 xducer_dy = -0.870343 signal = 2451.405582 ============================================ (2) try to get rid of some pesky stripes when manuvering on station: test "uvship" algorithm: Explanation: The positions stored for each averaging length ("ensemble") is the position at the end of the ensemble. Traditionally the ship's speed during an ensemble is the distance traveled divided by the time taken. This is calculated using the first difference in positions divided by the averaging length. But if whole profiles are missing, this may not be a good representation. The "uvship" algorithm uses the average of ship speeds at the single-ping stage, but only for profiles that contained ADCP data. The algorithm is not part of the live data processing, but is staged for use after the cruise. In this case it did help. A copy was made and the following command was run on the copy: cd .. rsync -a os75nb/ os75nb.uvship cd os75nb.uvship quick_adcp.py --steps2rerun navsteps:calib --refuv_source uvship --auto They were compared: cd .. dataviewer.py -c os75nb os75nb.uvship and the "uvship" was a definite improvement. ============================================================================= (3) Edit dataviewer.py -e ============================================================================= (4) make the web pages; leverage the sections from wh300 mkdir webpy cp ../wh300.uvship/sectinfo.txt webpy quick_web.py --redo ======================================================= (5) extract the netCDF files adcp_nc.py adcpdb contour/os75nb pe2006 os75nb --ship_name Pelican