Don't distirbute JSON with trap code
Don't distribute a default settings.json with our code. The system loads defaults anyway.
Necessity/problem to solve
Changes between versions (new fields/functionality) meant we had introduced a
"version" field to the JSON to verify the JSON will be compatible between camera trap versions. The problem is that this means every update requires us to maintain the version field in the JSON. If we forget to do this, it would result in the default JSON that not working with the current code version (an error/warning is displayed and default values used instead).
I would suggest simply removing the JSON from the repo to reduce overheads for us and reduce the risk of a non-functioning default system. This means users can generate a JSON if they want to modify settings. If they want to keep their custom settings between versions they would need to regenerate the file with the newest tuner.py (as would be the case anyway). The difference is that we can't accidentally provide an "incompatible" JSON due to an incorrect
This could be followed up at some point with an updated tuner.py that handles old settings.json files and tries to use them with the newest version.
Person hours: <1
Difficulty: Easy -- remove a file
I could work on this