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

Errant DWICount, BaselineCount values in InterlaceChecker #14

Open
mharms opened this issue Dec 9, 2015 · 0 comments
Open

Errant DWICount, BaselineCount values in InterlaceChecker #14

mharms opened this issue Dec 9, 2015 · 0 comments

Comments

@mharms
Copy link
Contributor

mharms commented Dec 9, 2015

On rare occasions (e.g., 4 out of 453 sessions), the DWICount and BaselineCount values in InterlaceChecker are non-sensible, as if they haven't been initialized properly.
e.g.,
DWICount: -1300997086; BaselineCount: 1300997134

FWIW, in all 4 instances, the DWICount was a large negative value, and the BaselineCount was a large positive value. Interestingly, the sum of the two nonetheless accurately reflects the total number of frames remaining after the slicewise check stage.

Also, I don't know if this is somewhat related, but in 3 of 453 sessions which "failed" at the gradient checking stage due to "Too many bad gradient directions found", I get non-sensible values such as the following in the terminal output (or equivalent, the output of the --resultsNotesFile argument):
GradientTotal#/LeftGradientTotal#: 52/1911268545
Baseline#/LeftBaseline#: 2/1904214016
Gradient#/LeftGradient#: 50/7054529
GradientDir#/LeftGradientDir#: 25/-1024065536

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