-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[UI] Screen to solve the goal "why was this review item created" #11399
Comments
To slightly add to this: it would also be awesome to submit to Frigate+ from there, once bounding-boxes are available. In trying out the new Review feature (also with a new model, because I do science wrong), I find that many of the events are tagged with an object that's not in them (usually person or cat, because my dogs are confusing), but it's difficult for me to do anything about it. I then need to look through the Frigate+ tab, which is a lot noisier. |
Please add bounding boxes toggle in the UI so I can figure out what triggers false positives. |
Just switched to .14,,,,and yes I have some false positives (probablly new plant growth) but I can't really tell from the image. |
Going to list out the UI troubleshooting things I think are missing, both new and old. This over laps other comments but wanted to dump a list as maybe this all gets re-vamped together.
|
i hope this also include bounding boxes for each objects instead of just one random object from the entire clip |
True, without the bounding box the utility of max/min_area/score becomes somewhat redundant - even more for new cameras. |
An initial improvement towards this has been added for the next version being a side panel that shows the objects, scores, zones, and snapshot for each object (assuming snapshots are enabled) #13063 |
This has been implemented in #13550 and will be available in Frigate 0.15. Snapshots should be enabled in your config for the best experience. Clicking/tapping on the gray "chip" on a review item in the Review pane will bring up a panel with a list of tracked objects, scores, and entered zones that caused the review item to be created. Each object can then be examined further by clicking/tapping the "View object lifecycle" button and scrolling/swiping through the significant moments that Frigate kept track of. |
Is this just for analyzing false positives? I have been having false negatives lately but I can't review the footage to see why without bounding boxes. Events are triggered just not alerts though so hopefully this new feature will be useable at the event level so I can fix my false negatives. |
Yes, this will be available with the Explore view in the upcoming version of Frigate. |
Awesome. Any news on a release window? There has been a spike in break ins in my area and I want to try and find time everything as soon as I can.
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Josh Hawkins ***@***.***>
Sent: Thursday, October 17, 2024 9:11:59 AM
To: blakeblackshear/frigate ***@***.***>
Cc: Nooton92 ***@***.***>; Comment ***@***.***>
Subject: Re: [blakeblackshear/frigate] [UI] Screen to solve the goal "why was this review item created" (Issue #11399)
Yes, this will be available with the Explore view in the upcoming version of Frigate.
—
Reply to this email directly, view it on GitHub<#11399 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5HY5F66YDH2MTGRD3ER4T3Z37HT7AVCNFSM6AAAAABH2S6HL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJZHAZDGNJSGM>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Describe what you are trying to accomplish and why in non technical terms
In the 0.14 UI review items are much more efficient at displaying and allowing the review of periods of time. However, they obfuscate some of the details / information that allows a user to understand why a review item was created.
Describe the solution you'd like
Add a screen that allows the user to see the bounding boxes that were detected for a specific object or review time to better understand why a false positive occurred, object was considered active, object was lost, etc.
The text was updated successfully, but these errors were encountered: