Limit Memory giving different results #3
Description
Hi, first of all, thanks for creating this awesome software!
It is very easy to use and quite versatile for fluorescence and BF movies. I think this is going to be widely used among many groups.
We noticed one odd behavior with BeatProfiler. We obtain different results depending on we activate the Limit Memory option:
| Filename | num beats (manual) | num beats (MeanFFT) | num beats (MeanFFT, limit memory) |
|---|---|---|---|
| B2_Loop001 | 0 | ||
| B2_Loop002 | 0 | 9 | |
| B2_Loop003 | 0 | 3 | |
| B2_Loop004 | 0 | ||
| B2_Loop005 | 15 | 14 | 14 |
| B2_Loop006 | 30 | 28 | 28 |
Is this issue to be expected?
We have reproduced this issue in a Windows 10 machine and MacBook Air running MacOS 13.5.1. We provide the files in this link, in case you would like to test the files in your environment.
We also noticed that, when we have close to 400 such movies and don't limit the memory, BeatProfiler completes the analysis, but not all movies are processed and included in the Summary.xlsx output.
Please let me know if there is a way around these issues.
Keisuke