If the first (or second time point technically but the 1/2 mismatch makes it the second in the input) frame of the first ROI is above threshold the entire thing crashes. In this case thresholds were set to 0.3. If you set the first time point to something subthreshold (B2) it still crashes, but if you change B3 (i.e. the first frame that we actually grab) it completes successfully. I would suggest we implement something which checks if the first frame is above threshold and then maybe increments the Event search forward until it finds a value subthreshold? Or maybe there is another way, but this issue has been driving me crazy because I didn't know what the issues was so I'd like to fix it.
If the first (or second time point technically but the 1/2 mismatch makes it the second in the input) frame of the first ROI is above threshold the entire thing crashes. In this case thresholds were set to 0.3. If you set the first time point to something subthreshold (B2) it still crashes, but if you change B3 (i.e. the first frame that we actually grab) it completes successfully. I would suggest we implement something which checks if the first frame is above threshold and then maybe increments the Event search forward until it finds a value subthreshold? Or maybe there is another way, but this issue has been driving me crazy because I didn't know what the issues was so I'd like to fix it.
input file that causes an issue
modification to input file which fixes the issue
error
dump.txt