@OOHehir
It's time to give the CSV file a new home :)
[x] Insted of one CSV file in /eloc. It would be better if every session-folder get's it own CSV file.
[x] The Prediction threshold should be increased to a higher (adjustable) value before we get too big CSV files on the SD card.
For example: Only predictions >0.60 are getting written to the CSV file.
[x] Question: Are these irregular time stamps in the CSV file normal? Or should the predictions happen in a more constant interval? Not sure :)
Example using this commit 92497792e591c9f4b4a28a8f8410080cade57051
EI-results-ID-290754-DEPLOY-VER-14.csv
[x] The prediction threshold can be set in project_config.h as required. I'll amend the code to only require when threshold value is reached on the target/ characteristic sound.
[x] I believe the irregular time stamps were bug related. With the latest commit they're occurring ever second, e.g.
EI-results-ID-290754-DEPLOY-VER-14.csv
The EI-results.. file is now created inside the session folder
The EI-results.. file is only created when it is determined that a characteristic sound has exceeded the required threshold, so if the AI detection is running but no characteristic sound is deemed to have been detected this file won't exist
The session folder is only created if the above file is created OR a wav file is created
@OOHehir It's time to give the CSV file a new home :)
[x] Insted of one CSV file in
/eloc
. It would be better if every session-folder get's it own CSV file.[x] The Prediction threshold should be increased to a higher (adjustable) value before we get too big CSV files on the SD card. For example: Only predictions >0.60 are getting written to the CSV file.
[x] Question: Are these irregular time stamps in the CSV file normal? Or should the predictions happen in a more constant interval? Not sure :) Example using this commit 92497792e591c9f4b4a28a8f8410080cade57051 EI-results-ID-290754-DEPLOY-VER-14.csv