forked from OceanStreamIO/echopype
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Standardize use of
transmit_frequency_start/stop
and use `pulse_for…
…m` for BB checks (OSOceanAcoustics#1091) * docs: remove outdated Attention box in Data Processing page * In EK80, rename frequency_start/end to convention-based transmit_frequency_start/stop * For EK80 transmit_frequency_start/stop, standardize data type (int to float) and attributes * Add transmit_frequency_start/stop to EK60 & AZFP, set to frequency_nominal * Replace use of frequency_start/stop in ek80 checks for BB channels with pulse_form * Rename pulse_form to transmit_type per convention, and map int codes to strings (CW, FM, FMD) * Assigned attributes to the wrong variable, in previous commit * The meaning for ek80 channel_mode = 1 is not described in ek80 manual * Ensure variables remain encoded as int types even after xr.merge * Overhaul EK80 checks for BB vs CW to use pulse_form / transmit_type * Set transmit_frequency_start/stop attributes in 1.0.yml and update set_groups_azfp/ek60 to use that * For ek80 transmit_freq_start/stop is now created and/or populated with frequency_nominal for power-only channels. Updated all BB vs CW checks. * Simplified ek80 tapered_chirp now that CW channels always contain freq nominal in transmit_frequency_start/stop * Small cleanups to comments, unused function parameter, etc, all involving ek80 * Simplify ek80 test for encode_mode = 'complex' but there are no CW pings * Remove transmit_type from tx_param_names b/c it's no longer an argument in tapered_chirp * Optimize ek80 BB vs CW tests using transmit_type on first ping_time * Update echopype/echodata/simrad.py Co-authored-by: Wu-Jung Lee <[email protected]> * Update echopype/echodata/simrad.py Co-authored-by: Wu-Jung Lee <[email protected]> * Change transmit_type FM string to LFM, per convention, and add more detailed flag_meanings strings, largely from the convention --------- Co-authored-by: Wu-Jung Lee <[email protected]>
- Loading branch information
Showing
9 changed files
with
154 additions
and
115 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.