>
>> There is an important new piece of functionality courtesy of Dan and
>> available via the Peak --> Peak Separator menu. I'll leave it to Dan to
>> explain what this does.
>
> This might be a nice peace of code, but is has no protection in memory
> usage. It tried it with a peak where two signals are close by and it
> filled 4GB RAM + 8GB swap until the OS hang! That shouldn't happen.
Hi Justin, you're right - it shouldn't ever do that. However, (in my desperate defence) it hasn't ever done that for me. Could you tell me how large the spectral region (in points) was that you picked? I wouldn't recommend going above 15 x 15 when you're first trying the code out. If you were at this size and the app crashed then there is something more serious going on.
Thanks, Dan
Daniel O'Donovan
[log in to unmask]
|