How It Works

Typical Workflow

1. Flow Chart
2. Initial Data Preparation
3. User Data Settings
4. Species Data Settings
5. DetEdit Interface
6. Data Analysis

Flow Chart

The following diagram shows the processing pipeline to get all the parameters and run the interface:

Initial data preparation

Create parameter files required to use the interface:

1. Make LTSA files (.ltsa)
2. Make TPWS files (TPWS.mat)
3. Make LTSA snippets files (LTSA.mat)

1. Make Long-Term Spectral Average (LTSA) files

LTSA files (.ltsa) are generated from a collection of WAV or XWAV files by averaging spectra over long-time periods and arranging these spectra sequentially as frequency-time spectrogram plots. LTSA files provide a quick overview of long-term recordings.

Using the Command Window in MATLAB, the .ltsafile is created as follows:

> mkLtsa

and follow the prompt windows to specify the audio file format, file directories, and parameters (e.g., time average length and frequency bin size to average the data).

Only 5 filename formats of WAV and XWAV files are supported:

• yymmdd-HHMMSS : SiteName_190326-123700.wav
• yymmdd_HHMMSS : SiteName_190326_123700.wav
• yyyymmdd_HHMMSS: SiteName_20190326_123700.wav
• yymmddHHMMSS : SiteName_190326123700.wav
• yyyymmddTHHMMS : SiteName_20190326T123700.wav

2. Make TPWS files (start Time, Peak-to-peak amplitude, Waveform, and Spectra parameters)

A *_TPWS.mat file contains the following matrices of detected signal parameters:

Variable	Description
MTT	Vector of start times of detections
MPP	Vector of received level amplitudes (dBpp)
MSP	Matrix of detection spectra
MSN	Matrix of waveforms

Create *_TPWS.matfiles is required to call the interface, so the user can:

• provide start times of detected acoustic signals to create the *_TPWS.mat file as follows:

  > edit make_TPWS

  In the editor window, modify input/output locations and detection parameters to run the script.

• apply a generic detector if you do not have any acoustic detections:

  • for use with XWAV files:

        > Edetect

    The user is prompted to supply inputs including a text file or spreadsheet containing detection parameters (see GOM_BW_pfile_320.xlsx for example), and a directory containing XWAV files.

  • for use with WAV files:

        > Edetect_wav ('paramFile','E:\DetEdit\GOM_BW_pfile_320.xlsx',...
        'tfFile','E:\MyTransferFunctionFiles\example_sig1_invSensit.tf',...
        'timeFile','E:\DetEdit\BW_Effort.xlsx',...
        'wavDir','E:\MyWAVFiles',...
        'channel',1)

3. Make LTSA snippets

After *_TPWS.mat files have been created, the following step is making the snippets of LTSAs corresponding to bouts of detections saved in TPWS files.

A *_LTSA.mat file contains the following matrices of detected signal parameters:

Variable	Description
pt	Vector of start times of spectral averages
pwr	Matrix of power spectral densities

Using a script containing the user data settings (see yourDataSettings for example), the LTSA snippets for each detection bout is performed as follows:

> mkLTSAsessions(@yourDataSettings)

or you can invoke the function directly

> mkLTSAsessions

and it will prompt you with a window to select the data settings script.

Assumming mkLTSAsessions invocation, the data settings scripts should contain the required following variables:

User Data Settings Script

Before invoking any of the analysis (mkLTSAsessions, detEdit, modDet, or summaryParams), create your data settings script to define directories and parameters. Examples of data settings scripts are found in DetEdit\Settings folder. You can make different versions of these templates, with different names for different species, sites or analysis.

Variable	Description	mkLTSAsessions	detEdit	modDet	summaryParams
filePrefix	TPWS.mat files name to match	✔️	✔️	✔️	✔️
iterationNum	Iteration number	✔️	✔️	✔️	✔️
sampleRate	Your data sample rate	✔️	✔️	✔️	✔️
sp	Species code	✔️	✔️	✔️	✔️
tpwsDir	TPWS.mat files directory	✔️	✔️	✔️	✔️
tfName	Transfer function file (.tf) directory	🔶	🔶	🔶	🔶
ltsaDir	LTSA.mat files directory	✔️

^{✔️ = required variable 🔶 = optional variable (only if transfer function was not previously applied)}

More parameter preferences can be specified to override default parameters (see yourDataSettings for more details). Uncomment the parameters as needed to overwrite the default settings specified in initDefaultParams.

Species Data Settings Script

DetEdit is provided with initSpParams with signal-specific parameters for the 4 different analysis (mkLTSAsessions, detEdit, modDet, and summaryParams). Different odontocete species parameters and other signals are given in initSpParams

Species abbreviation code:

• : Unknown signal
• De : Delphinid
• Pm : Physeter macrorhynchus - Sperm whale
• Zc : Ziphius cavirostris - Cuvier’s beaked whale
• Me : Mesoplodon europaeus - Gervais' beaked whale
• BWG: BWG signal type - Unidentified beaked whale
• Md : BW31 signal type - Unidentified beaked whale
• Ko : Kogia spp.
• Po : Porpoise spp.
• Dl : Delphinapterus leucas - Beluga whale
• Mm : Monodon monoceros - Narwhal
• MFA: Mid-frequency active sonar

If given a species code, the specific parameter preferences will override the default parameters (see parameters in initDefaultParams for more details). If you define different parameter values in yourDataSettings, those will overwrite the species-specific parameters (initSpParams) and the default parameters (initDefaultParams).

DetEdit Interface

1. Annotation and classification
2. Editing tools

Using a script containing your data settings (see yourDataSettings for example), you can invoke the interface as follows:

> detEdit(@yourDataSettings)

or you can invoke the interface directly

> detEdit

and it will prompt you with a window to select the data settings script.

While running, the user will be presented with progress information and at the beginning will be asked to specify Starting session, use 1 to start with the first bout.

After, the interface panels will be displayed. Arrange the panel as you wish for better visualization:

1. Annotation and classification

Annotation files ( *_TD.mat, *_FD.mat, and *_ID.mat) are created if running detEdit for the first time for a *_TPWS.mat file. All detections (stored in TPWS.mat file) are displayed in the interface. The annotations or classification you make would be stored in the corresponding annotation files, which will be updated each time a bout is edited.

Annotation File	Description	Color detections
*_TD.mat	Vector of true detection times
*_FD.mat	Vector of false detection times
*_ID.mat	Matrix of ID detection classified based on color ID color code. 1st column contains detection times and 2nd column the ID label

All annotation files from this stage are stored in the same directory where *_TPWS.mat files are located.

ID detection color legend:

ID Label	RGB Color
1
2
3
4
5
6
7
8
9
10

2. Editing tools and keyboard shortcuts

The annotation process can be done per bout by annotating the entire window at once or by selecting batches of detections using the Matlab's paintbrush tool - (yellow default color).

⚠️ to activate the brush, click at the plot you want to brush the data and then press p. Brush button will appear selected and you will be ready to flag detections. You can select a different color for the brush which has different meanings.

Keyboard shortcuts:

Keyboard	Brush color	Description
t		All detections in current window as true
f		All detections in current window as false
u		Update window contents
space		Jump to next consecutive bout (next window session)
b		Jump back one bout (previous window session)
+ r	+ u	Detections selected as false
+ g	+ u	Detections selected as true
+ u		Highlights and displays summary info in black outlined () of selected clicks (:warning: but does not change annotation files)
	+ u	Detections selected as ID color code

Other keyboard shortcuts to modify the interface settings, this will prompt the user to introduce the desired number:

Keyboard	Description
j	Jump to a non-consecutive bout
a	Adjust LTSA contrast and brightness
s	Adjust maximum time between detection scale
!	Adjust frequency scale
d	Adjust dB Peak-to-peak scale
'<'	Change dB RMS threshold
:	Change dB Peak-to-peak threshold
^	Change high-frequency threshold

Data Analysis

1. False Positive Rate Evaluation
2. Modify Annotation Files
3. Summarize Parameters

1. False Positive Rate Evaluation

To estimate the dataset's false positive rate, the following keyboard shortcuts will set the interface to display random detections for evaluation:

• x: evaluation at the signal level, where random individual detections are displayed.
• w: evaluation at the time-bin interval level, where a batch of detections within the defined interval length is displayed and the user has to evaluate if at least one detection within the interval is true.

Then, the evaluation decision is done by pressing the following keyboard shortcuts:

• x: as true detection
• z: as false detection

The random detections are selected systematically based on a given step size. The user can specify this parameter at yourDataSettings, by uncommenting the line as follows:

line 42: paramsUser.c4fd = your number;

this will overwrite the default step size parameter (see initDefaultParams for more details).

All evaluation decisions are stored in the *_TD.mat files.

2. Modify Annotation Files

The user can remove the annotated detections from the *_TPWS.mat files as follows:

> modDet(@yourDataSettings)

or you can invoke the function directly

> modDet

and it will prompt you with a window to select the data settings script.

3. Summarize Parameters