-
Notifications
You must be signed in to change notification settings - Fork 14
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
Tracking that doesn't split tracks when there are two gaps of only a few pixels #11
Comments
clare
changed the title
Tracking that doesn't split tracks when there is a gap of only a few pixels
Tracking that doesn't split tracks when there are two gaps of only a few pixels
Jul 10, 2018
It looks like tracking can cope with one small gap but not two like our traps are typically making. See Cat that is split up |
Hi Clare,
If it's only a few pixels we can use the 'open' morphology operation to fix
this. It joins together any close objects. I used to have this enabled
but as far as I remember turned it off due to causing other problems. It
might be worth trying again.
If you'd like to implement it, the method get_regions_of_interest in the
file "trackextractor.py" has a section "erosion" which is disabled at the
moment, you'd just need to change the cv command from erode to open and
enable it and see if it helps.
I've often found with tracking that fixing one problem can cause tradeoffs
with other clips, so it's important to see how it affects other cases. I
have a test mode for the extractor that can help with this. In this case,
it'll probably not cause any issues though.
We can also chat with Richard and Brent tomorrow as I'm sure they'll have
some good ideas about how this can be done more robustly.
…-Matthew.
On Tue, Jul 10, 2018 at 11:02 PM clare ***@***.***> wrote:
It looks like tracking can cope with one small gap but not two like our
traps are typically making.
See Cat that is split up
<https://drive.google.com/file/d/1EkW-x4Z24-OGiJm3kGGm8I7uN-3Im7Ku/view?usp=sharing>
and Cat not split up (but other problems)
<https://drive.google.com/file/d/1nFNMe9FoboC3YBCHjcN3fE3V0bHQBVbx/view?usp=sharing>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEZ8UOHWFQXMSMufy4hjbhsQi05ws-Yhks5uFInXgaJpZM4VJITV>
.
|
Opps cat the is split up link is wrong |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: