@ctuguinay had the idea of adding echodata.align_to_ping_time() to handle the timestamp alignment that we now have in the code for in:
- calibration (align timestamps of Environment group variables to
ping_time)
- add depth (align timestamps of Platform group variables to
ping_time)
I think this is a really interesting idea and am just recording my thoughts below. Essentially right now in the consolidate subpackage we have functions to add ancillary data into the Sv dataset once it is calibrated, and in Echolevels we call these Level 2 datasets. If we have echodata.align_to_ping_time() then the EchoData object may actually qualify as Level 2 in addition to the Sv.
One good thing about this is that we can have all the messy timestamp handling in one place, instead of interspersed in the code in various places when it's needed:
echopype/consolidate/ek_depth_utils.py::_var_time2_to_ping_time
echopype/calibrate/evn_params.py::harmonize_env_param_time
@ctuguinay had the idea of adding
echodata.align_to_ping_time()to handle the timestamp alignment that we now have in the code for in:ping_time)ping_time)I think this is a really interesting idea and am just recording my thoughts below. Essentially right now in the
consolidatesubpackage we have functions to add ancillary data into the Sv dataset once it is calibrated, and in Echolevels we call these Level 2 datasets. If we haveechodata.align_to_ping_time()then theEchoDataobject may actually qualify as Level 2 in addition to the Sv.One good thing about this is that we can have all the messy timestamp handling in one place, instead of interspersed in the code in various places when it's needed:
echopype/consolidate/ek_depth_utils.py::_var_time2_to_ping_timeechopype/calibrate/evn_params.py::harmonize_env_param_time