I have SoundTrap acoustic data (ST's were run with a click detector) and I keep two backups of the data in separate hard drives and then work on a copy of these files. I have four devices (two deployed at a time in different locations) and have been generating new binary folders and sqlite databases for each device per deployment.
For the first deployment data I had been working with decompressed SUD files, but am now using the newest PAMGUARD version and processing the SUD files directly.
I was moving between viewing different deployments in viewer mode, giving them a cursory overview, which at first was working as expected. However, when I then tried to reopen data from the first deployment the soundtrap click detector data was coming up as 'no data'. I tried removing the module, re-adding the SoundTrap Click detector and re-importing the SoundTrap Click detector data. It seemed like it was working but then no data was displayed.
When I then tried to view later deployments in Viewer mode again, the data map was showing all the data but no data was loading when I tried to view different sections, no spectograms or click detector data.
I'm wondering if anyone has any advice in regard how to structure the binary folders and databases, would I be better off having one per device and as I get new data adding it to the binary folder/database for example?
Also, does anyone have advice for switching between viewing different databases in viewer mode? It seems as if I have mixed up configurations some how. I was under the impression that everything gets saved to the binary folders and database so I thought that if I had the correct ones loaded (which I made sure I did) that I should be able to view the data as before, however I have clearly made a mistake somewhere.
At this point I think I will start the process again, and reprocess the SUD files, including the first deployment, with the updated version. However, I want to make sure to go forward with the best practice to avoid something like this happening again!