Skip to content
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

Open
NickM-27 opened this issue May 16, 2024 · 1 comment
Open

[UI] Screen to solve the goal "why was this review item created" #11399

NickM-27 opened this issue May 16, 2024 · 1 comment
Labels
enhancement New feature or request pinned

Comments

@NickM-27
Copy link
Sponsor Collaborator

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.

@NickM-27 NickM-27 added enhancement New feature or request pinned labels May 16, 2024
@jftanner
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pinned
Projects
None yet
Development

No branches or pull requests

2 participants