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

Specify AREA in shares or percentages #16069

Open
titovskiy opened this issue Jan 21, 2025 · 2 comments
Open

Specify AREA in shares or percentages #16069

titovskiy opened this issue Jan 21, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@titovskiy
Copy link

titovskiy commented Jan 21, 2025

        filters:
          car:
            min_area: 2500
            max_area: 30000

Жаль что эта AREA в пикселях, а не в долях.
Чуть конфиг размера детекта тронул и все нахрен посыпалось или можно как то через переменные делать калькуляцию?
Было бы удобно чтобы например персон - min_area 30% - max_area 50% от кадра и все... все предельно понятно.. а дальше пусть фригат сам считает сколько это в пикселях


It's a pity that this AREA is in pixels, not in shares.
A little bit of the detector size configuration touched and everything fell off or is it possible to make a calculation through the variables?
It would be convenient for the person, for example - min_area 30% - max_area 50% of the frame and that's it... everything is extremely clear.. and then let the frigate itself calculate how much it is in pixels

@titovskiy titovskiy added the enhancement New feature or request label Jan 21, 2025
@DieMetRik
Copy link

I think, percentage is more clear to newble users.
And if u change camera resolution u don't need to change percentage of area

@qtronixx
Copy link

as a percentage is definitely a great idea, but it will be even better if you can choose whether to use percentages or pixels :)

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

No branches or pull requests

3 participants