LAST CHANGED : 2021/08/21 16:08:59 CRUISE NAME(S) : FK210812 CRUISE DATES : 2021/08/11 23:03 to 2021/08/21 16:08 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 : 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/08/11 23:08:37 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 : os75 original alignment: 44.47 additional rotation -0.03 final transducer angle is: (44.47) - (-0.03) = 44.5 applied scale factor 1 additional scale factor (none) COMMENTS : Designing the Future 2. No changes to processing. Transducer alignment calibration. Flagged mostly biases at the surface, whole column biases. A few vertical stripes were observed at turns, but these were corrected with uv ship algorithm. PROCESSOR : Andrew Frambach --- 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 FK210812 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: ================================================== ----------------------------------------------------------------------------- # 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: 31 out of 37 amp = 0.9991 + -0.0007 (t - 228.1) phase = -0.04 + 0.0051 (t - 228.1) median mean std amplitude 1.0000 0.9991 0.0053 phase -0.0190 -0.0362 0.1811 ------------ $ 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:08:59 xducer_dx = -3.334874 xducer_dy = 3.243656 signal = 602.359640 ------------ We have an estimation from the transducer-gps offset, but the signal is low so we will not adjust. We have 31 points of watertrack data, so we used this to adjust the phase only: phase = -0.03 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_angle -0.03 --auto $ catwt **watertrack** ------------ Number of edited points: 31 out of 37 amp = 0.9994 + -0.0007 (t - 228.1) phase = -0.01 + 0.0054 (t - 228.1) median mean std amplitude 1.0000 0.9994 0.0051 phase 0.0120 -0.0051 0.1822 ------------ 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: 1) Biases at the surface were flagged. 2) Hanging data points at the limit of the ADCP depth range were flagged. 3) Data below the bottom was flagged. 4) The seabed was re-traced where visible. 5) A handful of vertical biases were observed. Vertical Biases Observed: 227.37 (corrected with uv ship algorithm)* 227.42 (corrected with uv ship algorithm)* 228.25 (corrected with uv ship algorithm)* *We ran the uv ship algorithm to take care of times when the ship speed calculation is biased, resulting in large vertical stripes in the dataset. $ quick_adcp.py --steps2rerun navsteps:calib --refuv_source uvship --auto 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. $ catwt **watertrack** ------------ Number of edited points: 31 out of 33 amp = 0.9994 + -0.0007 (t - 228.1) phase = -0.00 + 0.0059 (t - 228.1) median mean std amplitude 1.0000 0.9994 0.0050 phase 0.0120 -0.0011 0.1836 ------------ 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 . ../os75nb.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. $ quick_web.py --interactive $ figview.py webpy $ quick_adcp.py --steps2rerun matfiles --auto $ adcp_nc.py adcpdb contour/os75nb FK210812 os75nb --ship_name Falkor $ ncdump contour/os75nb.nc -h