LAST CHANGED : 2021/03/03 20:15:17 CRUISE NAME(S) : FK210206 CRUISE DATES : 2021/02/06 07:25:33 to 2021/03/03 20:15:03 SHIP NAME : Falkor PORTS : Brisbane, AUS to Brisbane, AUS CHIEF SCIENTIST : Derya Guerer DATABASE NAME : a_fk DATA FILES : fk2021_036_26432.raw to fk2021_061_72000.raw STATUS : to do done ------ ----------- averaged [ X ] loaded [ X ] # loaded at sea 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 2021/02/06 07:25:33 off 300 55 16 7 8 44.47 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 : os75nb original alignment: 44.47 additional rotation: -0.08 final transducer angle is: 44.55 (44.47) - (-0.08) original scalefactor: 1.0 additional scale factor (none) final scale factor: 1.0 COMMENTS : Falkor cruise that kept the os75nb on almost the entire time. No major problems or changes that needed to be made through the cruise, and enough watertrack points (127 out of 129) to not need a flanking calibration. PROCESSOR : Joseph Gum --- processing parameters ---------- ## (determined from "sonar"): model = os ## (determined from "sonar"): frequency = 75 ## (determined from "sonar"): instname = os75 ## (determined from "sonar"): pingtype = nb beamangle 30 cruisename FK210206 datatype uhdas ens_len 300 fixfile a_fk.gps frequency 75 hcorr_inst seapath instname os75 model os pingtype nb proc_engine python ref_method refsm refuv_smoothwin 3 refuv_source nav sonar os75nb txy_file a_fk.agt xducer_dx 1 xducer_dy 21 yearbase 2021 ================================================== PROCESSING STEPS: ================================================== # Processing commands start in the os75 directory. ----------------------------- # 1. Check heading correction ----------------------------- Check that we have a good heading correction for all of the ADCP data. There should be no holes in the heading correction graphs, where good fixes are green circles and no fixes are red crosses. Gaps in the plots where there are no symbols are okay, no data was collected there. If there are red crosses on the heading correction graphs (cal/rotate/ens_hcorr_*.png) then they need to be patched in the cal/rotate dir using patch_hcorr.py. $ plot_nav.py nav/a_fk.gps $ figview.py We're missing a few heading fixes near the end of cruise between 49.8 and 50.9. We'll need to recover them using patch_hcorr. $ dataviewer.py It looks stable around the gaps, time to look at watertrack. $ catwt **watertrack** ------------ Number of edited points: 127 out of 129 amp = 0.9997 + 0.0000 (t - 50.7) phase = -0.09 + -0.0010 (t - 50.7) median mean std amplitude 1.0000 0.9997 0.0066 phase -0.0780 -0.0863 0.4002 ------------ $ cd cal/rotate $ dataviewer.py -c . ../os75nb.orig The first hole shows a change in data, while the second larger hole shows a gap of data that isn't recoverable. We gained on the first and no change on the second gap. --------------------- # 2. ADCP calibration --------------------- Calibrate the dataset in sum by checking the calibration values and applying a fix to the necessary categories 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 # 0.3% phase/angle 0.05 When looking at an xy calibration to adjust the relative location of the sonar to the currently known location we hope that the dx and dy values are as close to 0 as possible, and the signal is between 1000 and 5000. Less than 1000 means very little data, more than 5000 means too much change. If values are out of range we make a bulk correction to the entire dataset which 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: 127 out of 129 amp = 0.9997 + 0.0000 (t - 50.7) phase = -0.10 + -0.0006 (t - 50.7) median mean std amplitude 1.0000 0.9997 0.0065 phase -0.0790 -0.0983 0.3875 ------------ $ catbt No bottom track points found $ catxy **transducer-gps offset** ------------ guessing ADCP (dx=starboard, dy=fwd) meters from GPS positions from a_fk.agt calculation done at 2021/04/01 01:25:29 xducer_dx = -0.328018 xducer_dy = 2.901580 signal = 1846.598139 ------------ We will apply a small phase correction based on the catwt. $ quick_adcp.py --steps2rerun rotate:apply_edit:navsteps:calib --rotate_angle -0.08 --auto $ catwt **watertrack** ------------ Number of edited points: 127 out of 129 amp = 0.9997 + 0.0000 (t - 50.7) phase = -0.02 + -0.0006 (t - 50.7) median mean std amplitude 1.0000 0.9997 0.0065 phase 0.0000 -0.0188 0.3875 ------------ ------------------- # 3. Editing points ------------------- Edit out biased data or artifacts deeper than the range of the sonar in the dataset, or other problems. Use `dataviewer.py -e` to look for problems with the data and flag the bad data as bad. After editing out data we rerun the calibration to see if the changed dataset statistics have changed enough that a new calibration is needed. $ dataviewer.py -e Bins at or past effective range were removed, very little otherwise. $ quick_adcp.py --steps2rerun navsteps:calib --auto $ catwt **watertrack** ------------ Number of edited points: 127 out of 129 amp = 0.9997 + 0.0000 (t - 50.7) phase = -0.02 + -0.0006 (t - 50.7) median mean std amplitude 1.0000 0.9997 0.0065 phase 0.0000 -0.0188 0.3875 ------------ $ catxy **transducer-gps offset** ------------ guessing ADCP (dx=starboard, dy=fwd) meters from GPS positions from a_fk.agt calculation done at 2021/04/01 02:00:00 xducer_dx = -0.304609 xducer_dy = 2.805746 signal = 1846.598139 ------------ The values did not change as we did not make enough edits to the data. catwt and catxy are still good enough that we don't need to make corrections, but we could. -------------------------------------------------- # 4. Re-check heading correction and other 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 (or lack thereof) dataset against the original dataset to make sure all problems have been dealt with and no new problems have appeared. $ dataviewer.py -c . ../os75nb.orig The phase adjustment looks to have worked, smoothing out transition points at turns in the data. ------------------------- # 6. Make plots and files ------------------------- Create the figures and data files needed to finish processing and make public/submit to a repository (JASADCP, if nowhere else). 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. $ quick_web.py --interactive $ quick_adcp.py --steps2rerun matfiles --auto $ adcp_nc.py adcpdb contour/os75nb FK210206 os75nb --ship_name Falkor $ ncdump contour/os75nb.nc -h