Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Processed events with no matches produce a lot of missed images
See original GitHub issue@erikarenhill, curious to hear your thoughts on this as well.
I’ve been testing some of the recent code changes with untrained detectors. One thing I’ve noticed is that if SAVE_UNKNOWN is set to true, then a lot of images will be produced for each event. Each retry per detector could produce an image if a person is found. For example, if I’m running compreface and deepstack and the snapshot and latest retries are set to 10 each, then I could in theory have 40 images saved for just a single event.
Maybe just taking a couple of the best results from the unknown images instead of saving out every single one to display on the UI.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I went ahead and made the changes I mentioned above in beta. Rather than each detector pulling images from Frigate on their own, the image is pulled then passed to each detector. This allows me to reduce the amount of images that are written. Hope this may help with the Frigate API issues too.
This also sets up the code a little better to handle the MQTT snapshot issue you brought up - #18
Maybe instead of having each detector pull the image, I write the image first and put that image through each detector. It could take a little longer, but would reduce the amount of images in general and Frigate API hits.