jrenfree
commented
1 month ago Wrote an R script to read Valeport UCTD files, parse out the downcast data, then insert the depth and sound speed profile into a template .ecs file. It also computes the average temperature, salinity, and depth over the entire downcast to enter as single values into the .ecs file, which are used for computing the absorption coefficients.
Right now we create separate EV files for processing CPS and krill data. This is done because the integration for both are conducted over different ranges, and as such we use different sound speeds averaged over the integration range. Echoview now lets you use a sound speed profile, which means that instead of using single values, we can input CTD data into the .ecs file, which would mean we no longer would need to have separate CPS and krill EV files.