Export to excel errors about deepsqueak

[JohnReinhart]

https://docs.google.com/presentation/d/1Jg1luBJf9HoF7i6TPMxp0ztRYOpNjkDSR4T3592G9JM/edit?usp=sharing

[DrCoffey]

That error usually only occurs when a box is screwed up and outside the Audio range, but because it is happening for every call there must be something else going on. Are you using separate folders for audio files and detection files? Have you set both of those folders before trying to export the stats?

[JohnReinhart]

Yeah, each animal in the litter has its own folder processed individually. Each file produced by DeepSqueak, before being converted to an excel file, is saved within the same folder that represents each animal.

[DrCoffey]

Got it. Usually I would keep all of the audio files for 1 project in a single folder, and all of the detection files for that project in a separate folder. That way you can analyze the files in a batch. You could then export them all at once or cluster them all at once.

Either way the audio file and detection files need separate folders, and you need to point DeepSqueak to those folders before exporting.

[JohnReinhart]

I did try saving the detection files in one separate folder at one point but was still getting the same error.

[DrCoffey]

It is likely something strange with the one detection file then, without seeing that specific file and corresponding audio file, it will be hard to tell what is going wrong. If you can share them I might be able to help.

[JohnReinhart]

It wont allow me to load zipped files, any good suggestions on how to share them with you?

[DrCoffey]

Google drive links usually work well.

[JohnReinhart]

https://drive.google.com/drive/folders/1NbVNSLRftOq076huDaNPvNxbZoNsdkSP?usp=sharing

[JohnReinhart]

We found a workaround in the excel_Callback function. In effect what was happening was that one of the "if" statements which checked the characteristics of the calls (start time, end time, and length of call) was triggering when the data was being migrated out of Deepsqueak and into the excel sheet output. The reason for this was unclear as the call duration was within acceptable limits. By turning off this part of the warning we were able to get the excel sheet to populate correctly with values that make sense. We tried to replicate it with different files, but there wasn't any apparent similarities between the several files which failed to export. Attached is a screen capture of the change that was made to stop the error message from appearing and blocking the output of the excel sheet.