Right now the sound speed and attenuation are calculated only using constant environmental parameters.
This issue is the first step to broaden the compute_Sv/compute_TS functions to use a depth-dependent profile.
Along with the discussions we had in #1666, we should also discuss if/how we want to handle the case when users supply multiple profiles, either at different times or at different lat/lon locations. IMHO if we do, we need to be very clear what the behavior is for missing data sections.
cc @ctuguinay @LOCEANlloydizard @johnepohl-noaa @ElizabethMPhillips
Right now the sound speed and attenuation are calculated only using constant environmental parameters.
This issue is the first step to broaden the
compute_Sv/compute_TSfunctions to use a depth-dependent profile.Along with the discussions we had in #1666, we should also discuss if/how we want to handle the case when users supply multiple profiles, either at different times or at different lat/lon locations. IMHO if we do, we need to be very clear what the behavior is for missing data sections.
cc @ctuguinay @LOCEANlloydizard @johnepohl-noaa @ElizabethMPhillips