LAST CHANGED : 2021/08/21 16:12:48 CRUISE NAME(S) : FK210812 CRUISE DATES : 2021/08/11 23:03 to 2021/08/21 16:12 SHIP NAME : Falkor PORTS : San Diego, CA to San Diego, CA CHIEF SCIENTIST : Brennan Phillips DATABASE NAME : a_fk DATA FILES : fk2021_222_83014.raw to fk2021_232_57600.raw STATUS : to do done ------ ----------- averaged [ x ] 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 : wh300 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 2021/08/11 23:05:35 off 120 70 2 7 2 44.63 0.00 0001 2021/08/12 09:05:35 off 120 70 2 7 2 44.63 0.00 0001 2021/08/17 20:20:35 off 120 70 2 7 2 44.63 0.00 0001 2021/08/19 12:20:35 off 120 70 2 7 2 44.63 0.00 0001 2021/08/19 22:20:35 off 120 70 2 7 2 44.63 0.00 0001 2021/08/20 18:20:35 off 120 70 2 7 2 44.63 0.00 0001 2021/08/21 04:20:35 off 120 70 2 7 2 44.63 0.00 0001 HEADING : PRIMARY : heading from gyro CORRECTION : heading correction from seapath NOTE: time-dependent heading corrections applied IN the ensembles (see cal/rotate/ens_hcorr.ang) POSITIONS : gps positions from cnav CALIBRATION : wh300 original alignment: 44.63 additional rotation 0.06 final transducer angle is: (44.63) - (0.06) = 44.57 applied scale factor 1 additional scale factor (1.003) COMMENTS : Designing the Future 2. No changes to processing. Transducer alignment calibration. Heavy biases from 225.43 -- 228.25. Changed percent good thresholding from 50% to 70% to help, removed the rest manually. PROCESSOR : Andrew Frambach --- processing parameters ---------- ## (determined from "sonar"): model = wh ## (determined from "sonar"): frequency = 300 ## (determined from "sonar"): instname = wh300 ## (determined from "sonar"): pingtype = bb beamangle 20 cruisename FK210812 datatype uhdas ens_len 120 fixfile a_fk.gps frequency 300 hcorr_inst seapath instname wh300 model wh pingtype bb proc_engine python ref_method refsm refuv_smoothwin 3 refuv_source nav sonar wh300 txy_file a_fk.agt xducer_dx 2 xducer_dy 18 yearbase 2021 ================================================== PROCESSING STEPS: ================================================== ----------------------------------------------------------------------------- # 1. Check heading correction ----------------------------------------------------------------------------- # Processing commands here forward start in the os75nb directory. Check that we have a good heading correction for all of the ADCP data: $ plot_nav.py nav/a_fk.gps <-- just to see the cruise track $ figview.py cal/rotate/ens* There should be no poor fixes in the heading correction graphs. These are represented by red crosses, good fixes are represented by green dots. Gaps in the heading correction graphs are okay, no data was collected during these times. If there are red crosses on the heading correction graphs then they need to be patched with patch_hcorr.py. There were no gaps in the ADCP heading correction ensemble. ----------------------------------------------------------------------------- # 2. ADCP calibration, Part 1 ----------------------------------------------------------------------------- Calibrate the dataset in sum by checking the calibration values and applying a fix if necessary. When looking at a water track or bottom track calibration, we want to see statistics inside the following values: median_tolerance amplitude 1.003 phase/angle 0.05 The xy calibration is an estimate of the horizontal separation between the physical location of the ADCP and primary GPS device in meters. When looking at an xy calibration estimate we want the dx and dy values to be as close to zero as possible, as long as the signal is between 1000 and 5000. Less than 1000 means there is very little data, more than 5000 means there is too much change. If values are out of range for either calibration we make a bulk correction to the entire dataset. This should reduce the number of outliers to be edited out. If we make any changes to x or y they should be integers. $ catwt **watertrack** ------------ Number of edited points: 29 out of 32 amp = 1.0031 + -0.0002 (t - 227.8) phase = -0.01 + -0.0258 (t - 227.8) median mean std amplitude 1.0030 1.0031 0.0099 phase 0.0100 -0.0089 0.4337 ------------ $ catbt **bottomtrack** ------------ tail: cannot open 'cal/botmtrk/btcaluv.out' for reading: No such file or directory ------------ $ catxy **transducer-gps offset** ------------ guessing ADCP (dx=starboard, dy=fwd) meters from GPS positions from a_fk.agt calculation done at 2021/08/21 16:12:48 xducer_dx = -0.321611 xducer_dy = 1.751798 signal = 278.272613 ------------ We have an estimation from the transducer-gps offset, but the signal is low so we will not adjust. We have 29 points of watertrack data, so we used this to adjust the amplitude only: amplitude = *1.003 Confirm by checking the distribution: $ figview.py cal/watertrk/*png Adjust the amplitude calibration and recheck the bottomtrack: $ quick_adcp.py --steps2rerun rotate:navsteps:calib --rotate_amplitude 1.003 --auto $ catwt **watertrack** ------------ Number of edited points: 29 out of 32 amp = 1.0007 + -0.0002 (t - 227.8) phase = -0.01 + -0.0297 (t - 227.8) median mean std amplitude 1.0000 1.0007 0.0101 phase 0.0120 -0.0082 0.4308 ------------ Everything looks good for now, time to move to the next step. ----------------------------------------------------------------------------- # 3. Flagging Questionable Data ----------------------------------------------------------------------------- Flagging of biased/questionable data or artifacts in the dataset. We used dataviewer.py to look for problems with the data and flag the data as questionable. $ dataviewer.py -e Comments: There were significant biases from 225.43 through 228.25. Most of these have been flagged where evident. 1) The threshold on percent good for flagging data as bad was changed from 50% to 70% to help flag biases present. 2) Biases from bubbles at the surface were flagged (high counts in shallow water). 3) Data points in medium percent good were flagged if they were visually not good. 4) In cases where it was obvious that a single column of water was biased, that column was flagged. 5) Hanging data points at the limit of the ADCP depth range were flagged. 6) Data below the bottom was flagged. 7) The seabed was re-traced where visible. Biases Observed: 223.12 -- 223.20 225.43 -- 225.73 226.37 -- 228.25 Finally, we check the calibrations again to make sure that there were no large shifts since we made edits. Since the signal will still be low, we will only check the transducer alignment. $ quick_adcp.py --steps2rerun calib --auto $ catwt **watertrack** ------------ Number of edited points: 27 out of 29 amp = 1.0006 + 0.0005 (t - 228.0) phase = 0.06 + -0.0659 (t - 228.0) median mean std amplitude 1.0000 1.0006 0.0112 phase 0.0530 0.0596 0.3631 ------------ The phase could use a slight adjustment: +0.06 $ quick_adcp.py --steps2rerun rotate:navsteps:calib --rotate_angle 0.06 --auto $ catwt **watertrack** ------------ Number of edited points: 27 out of 29 amp = 1.0006 + 0.0005 (t - 228.0) phase = 0.00 + -0.0655 (t - 228.0) median mean std amplitude 1.0000 1.0006 0.0112 phase -0.0060 0.0007 0.3620 ------------ All calibration values are within reasonable limits. ----------------------------------------------------------------------------- # 4. Re-check all figures ----------------------------------------------------------------------------- Check all figures again to make sure that any problems were addressed and no new problems have appeared after making changes to the dataset. $ figview.py All of the figures look fine. ----------------------------------------------------------------------------- # 5. Check edited, calibrated dataset against original dataset ----------------------------------------------------------------------------- Compare the edited, calibrated dataset against the original dataset to make sure all problems have been dealt with and no new problems have appeared. $ dataviewer.py -c . ../wh300.orig ----------------------------------------------------------------------------- # 6. Make plots and files ----------------------------------------------------------------------------- Create the figures and data files needed to finish processing and submit. Make the plots needed for web viewing, matlab files (legacy), and netCDF files, then check that the netCDF files are readable. Plots should be in 3 to 5 day chunks for a cruise longer than one week, or divided by geographic features where it makes sense. $ mkdir webpy $ cp ../os75nb/webpy/sectinfo.txt webpy/. $ quick_web.py --redo $ figview.py webpy $ quick_adcp.py --steps2rerun matfiles --auto $ adcp_nc.py adcpdb contour/wh300 FK210812 wh300 --ship_name Falkor $ ncdump contour/wh300.nc -h