Butterworth filter

[merlinthemagician]

Good afternoon,
When attempting to apply a Butterworth filter to a stack of images, the command seems to get stuck, for the example I ran at "Creating process 14/16". This is not necessarily related to the filter itself, it is accompanied by an error message "Too many open windows". Hitting the "Stop" button leads to IndexError exceptions ("list index out of range") and flika needs to be terminated.

Thanks a lot and best wishes
Ivo

P.S.: Traceback at "Creating process 14/16":

Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/flika-0.2.33-py3.9.egg/flika/process/progress_bar.py", line 28, in run
File "/usr/local/Cellar/python@3.9/3.9.4/Frameworks/Python.framework/Versions/3.9/lib/python3.9/multiprocessing/context.py", line 103, in Queue
File "/usr/local/Cellar/python@3.9/3.9.4/Frameworks/Python.framework/Versions/3.9/lib/python3.9/multiprocessing/queues.py", line 48, in init
File "/usr/local/Cellar/python@3.9/3.9.4/Frameworks/Python.framework/Versions/3.9/lib/python3.9/multiprocessing/context.py", line 68, in Lock
File "/usr/local/Cellar/python@3.9/3.9.4/Frameworks/Python.framework/Versions/3.9/lib/python3.9/multiprocessing/synchronize.py", line 162, in init
File "/usr/local/Cellar/python@3.9/3.9.4/Frameworks/Python.framework/Versions/3.9/lib/python3.9/multiprocessing/synchronize.py", line 57, in init
OSError: [Errno 24] Too many open files

[merlinthemagician]

Similar to #50 this is related to calling deprecated methods. It can be fixed by using a previous Python version (Python 3.8.10 worked for me).

[kyleellefsen]

Hi Ivo,

I just upgraded my python to version 3.9.5 on MacOS Big Sur, created a fresh virtual environment, install all flika dependencies, and am unable to recreate this error. Which deprecated methods are being called?

[merlinthemagician]

Hi Kylle,
thanks for looking into this issue. I've tested calling the Butterworth filter again both with a virtual environment as well as my system installation of python 3.9.5 and I wasn't able to reproduce this issue either. I assume that it was related to the sequence of commands that I ran earlier. I believed that this was related to calls to deprecated methods but the Traceback suggests that it is instead related to parallelisation. My apologies, it seems that it is not related to #50.
Thanks a lot and best wishes
Ivo

[kyleellefsen]

Ok since we can reproduce it I'm closing this issue.