PinaGruden / Localization_Towed_Array

Localization with ambiguity surfaces for towed array data
BSD 3-Clause Clear License
4 stars 0 forks source link

A0_SetUp doesn't show any tracks with test data #16

Closed sfregosi closed 9 months ago

sfregosi commented 9 months ago

1. Issue Report Checklist

2. Problem Description

2.1. Associated Package

Localization_Towed_Array

2.2. What steps reproduce the problem?

  1. Add Localization_Towed_Array-1.0.0 to path (with subfolders)

  2. Open specify_paths.m

    • Left all paths as defaults in specify_paths.m
    • Because a Crosscorrelograms folder did not exist in ./Test_example/Data, created this folder. Pasted in Test_clicks_rawCrossCorrelogram_ALL.mat and Test_whistles_rawCrossCorrelogram_ALL.mat from the TDOA_tracking_master/Test_example/Data/Raw_CrossCorrelogram folder
    • Created empty Results folder within Test_example to match specify_paths.m default
  3. Left all parameters in specify_parameters.m as default

  4. Run A0_SetUp.m

    • Two figures are generated
      • Figure 1 shows the cross-correlogram for both clicks and whistles with pink dashed lines marking the cutoff. Theare no tracked TDOAs (blue lines)
      • Figure 2 is an empty set of axes (but does have the legend and pink dashed lines)
  5. Run A1_Localize.m

    • Prompt appears in Command window to select a track. Type 1 and hit enter. This runs for a bit and generates Figure 3 which does show a single localization.
    • I can keep that localization and try to localize another group, 2 and this gives an error message:
 i.e. enter [1,2,3] for fragments 1,2,3. 
 2
Elapsed time is 8.015903 seconds.
Localization not possible. 
Selected track(s) do not result in a sufficient bearing change for successful localization. 
Try again. 

2.3. What is the expected output? What do you see instead?

2.4. Paste Error Below (if applicable)

There is not actually an error in figure generation in A0_SetUp and I only get an error in A1_Localize when trying to localize a second track. I'm not sure if the test data includes a second track or not so not sure if that is a true error.


 i.e. enter [1,2,3] for fragments 1,2,3. 
 2
Elapsed time is 8.015903 seconds.
Localization not possible. 
Selected track(s) do not result in a sufficient bearing change for successful localization. 
Try again. 

3. Matlab Version

sfregosi commented 9 months ago

I think this has to do with the test data being used.

The parameters of the results from my run of TDOA_tracking_master do not match the results that are included as the Test_example for the Localization_Towed_Array package (different array spacing), so possibly something funky going on there?

sfregosi commented 9 months ago

Yes, it's related to testing data missmatch! The crosscorrelogram example data is too big to upload to Github.

To fix:

Could do the same thing with raw GPS data!

PinaGruden commented 9 months ago

Done - all committed to GitHub - for both Crosscorrelogram and GPS. Link to the folder with data (Crosscorrelogram and GPS): https://drive.google.com/drive/folders/1VxI0HcsGINs5_v9HUmQOkaHFSvuHFiuW?usp=sharing