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

Consistency Checker Motion Boundaries #32

Open
pgalatic opened this issue Apr 4, 2020 · 0 comments
Open

Consistency Checker Motion Boundaries #32

pgalatic opened this issue Apr 4, 2020 · 0 comments

Comments

@pgalatic
Copy link

pgalatic commented Apr 4, 2020

Hi, I wanted to know more about the decision to have motion boundaries be described as "certain" (MOTION_BOUNDARIE_VALUE = 255) in the consistency checker, as in the associated paper as well as your previous work from 2016, you describe masking out motion boundaries as uncertain.

I ran consistencyChecker with MOTION_BOUNDARIE_VALUE = 0 and got very different results on a sample operation; naturally, the cert file was darker, having more regions masked out. I haven't tested it on a video yet, as clearly the current version works as-is. I'm more interested to know the reasons behind the discrepancy, or if you do something like set MOTION_BOUNDARIE_VALUE to 0 during train time and 255 for test time—or if I'm perhaps misunderstanding how the certs are calculated.

Thanks!

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

No branches or pull requests

1 participant