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

Frigate+ submission re-classification of all objects in frame #11529

Closed
mjdyson opened this issue May 26, 2024 · 1 comment
Closed

Frigate+ submission re-classification of all objects in frame #11529

mjdyson opened this issue May 26, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request

Comments

@mjdyson
Copy link

mjdyson commented May 26, 2024

Describe what you are trying to accomplish and why in non technical terms
I want to reduce the time spent labelling objects within a frigate+ submission so that I can spend more time submitting more photos.

Describe the solution you'd like
The current workflow only identifies a single item in the image - I presume this is because it takes the bounding box from the original motion tile (snapshot?) and then overlays it on top of the bigger video frame that it came from. Within this image, there may be multiple objects that are untagged that needs to be bounded and labelled. This starts to get a bit tedious for objects that might be fairly static (cars, plants etc).

It would be great if there was a pipeline that could send a bit more through the local classifier. Perhaps, the whole frame looking for new items, or more pragmatically, an auto-labelling of a new bounding box.

@mjdyson mjdyson added the enhancement New feature or request label May 26, 2024
@mjdyson mjdyson changed the title Frigate+ submission re-classification Frigate+ submission re-classification of all objects in frame May 26, 2024
@NickM-27
Copy link
Sponsor Collaborator

This is a duplicate of #8229

@NickM-27 NickM-27 added the duplicate This issue or pull request already exists label May 26, 2024
@NickM-27 NickM-27 closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants