Closed jack-elliott closed 1 year ago
@jack-elliott I'm not able to replicate this. Is it possible the frame set was created before we had fixed the frame name bug and it was overriding other files?
I can't tell now if it is the odd frame set issue or if the first pair isn't working properly due to a unique issue. I can test once a release with the indices working is out?
I did find an off-by-one issue when we're selecting the first frame, but I don't think that would affect the whole set processing. I'll leave the debugging video here if you want to use it with the next release. I'll keep looking at other frame sets to make sure though.
I'm assuming this was the same issue as #403 with the high speed capture. We can always open this issue again if we see the same problem.
IN whole set processing frames 1 and 2 give ~ 0's. May be the autocorrelations (same images)