Fleet Configurations
Deployments
Gliders
Projects
Payload Bays
Instruments
Users
API
Log In
Deployment ru26d-20190905T1802
Pilot Notes
Finished my analysis of the CTD data. CTD pressure read too deep. Was able to utilize pre/post lab checks as well as data during to come up with a correction factor. Goal of the correction factor was primarily to get CTD to about .1 to .2 m below surface at surfacing. This was for beginning and end of deployment. All corrections have the same start time, t0. Choice is to correct it against m_depth or just add the offset in there. No idea how accurate m_depth is and usually its less so than CTD since its calibrated less and subject to loose surface calibration (zero_ocean_pressure). Option exists to use only an offset which was corrected by hand to match ctd surface readings to about .15 m. t0 = datetime(2019,7,23); ctd_corr_slope_only = -0.009903; % This is a linear correction to correct ctd data to match m_depth from the glider (correction based on m_depth as truth) sci_pressure_2 = sci_pressure - (sci_pressure .* ctd_corr_slope_only) - ... (day(ctd_time_datenum-t0)*.0126 + 1.7127); % This is a hand adjusted correction slightly more aggressive that works a touch better (again based on m_depth as ground truth) sci_pressure_3 = sci_pressure - (sci_pressure .* ctd_corr_slope_only) - ... (day(ctd_time_datenum-t0)*.008398 + 2.12); % this is offset only; recconend this since right now there is no way to say m_depth is more accurate sci_pressure_4 = sci_pressure - (day(ctd_time_datenum-t0)*.008398 + 2.12); Salinity also might be about .02 to .03 low from the glider. This passed in tank tests quite well. Corresponds to about .003 in C. I tried to correct cond to the ian ctd cast but when converting to salinity again it got a little wild so withholding further analysis in that regard. There is a spreadsheet compiling all this in the post-recovery folder for ru26d
Category
Informational
Alert
Action Needed
Action Taken
Operations
Update
Credentials Required
Username
Password