When trying to start a new pixel classification project, I get the following error:
"zero size array to reduction operation maximum which has no identity "

this is the log:

> ERROR 2023-03-04 18:37:20,531 excepthooks 11172 3476 Unhandled exception in thread: 'MainThread'
> ERROR 2023-03-04 18:37:20,532 excepthooks 11172 3476 Traceback (most recent call last):
>   File "C:\Program Files\ilastik-1.4.0\lib\site-packages\ilastik\applets\pixelClassification\suggestFeaturesDialog.py", line 852, in _run_selection
>     self.opFilterFeatureSelection.setupOutputs()
>   File "C:\Program Files\ilastik-1.4.0\lib\site-packages\ilastik\applets\pixelClassification\opPixelClassification.py", line 707, in setupOutputs
>     data, labels.astype("int"), self._filter_method
>   File "C:\Program Files\ilastik-1.4.0\lib\site-packages\ilastik_feature_selection\filter_feature_selection.py", line 47, in __init__
>     self._X = normalize_data_for_MI(np.asarray(X))
>   File "C:\Program Files\ilastik-1.4.0\lib\site-packages\ilastik_feature_selection\filter_feature_selection.py", line 44, in normalize_data_for_MI
>     X[:, i] -= X[:, i].min()
>   File "C:\Program Files\ilastik-1.4.0\lib\site-packages\numpy\core\_methods.py", line 44, in _amin
>     return umr_minimum(a, axis, None, out, keepdims, initial, where)
> ValueError: zero-size array to reduction operation minimum which has no identity
I got this with a previous installation of Ilastik, so I installed the last release but this continues to happen.

Is there a way to solve this?

Many thanks,

Neta.
              
Hello @netama,
does this really happen when you start a new project? I would expect this code path to fire when using the Suggest Features functionality…
I tried reproducing it, and indeed I can reach it, if I
create a new pixel classification project
load some data
select feauteres
click on Suggest Features, without adding any annotations.
It would be important to know whether you arrived there with a different path. The one I outlined is a bug, and this we can fix.
Sorry that you ran into this!

Cheers

Dominik
              
Hello @gemwilson,
first of all, welcome to the image.sc community   
And second, sorry that you ran into this issue. In order to resolve it it would be great to find out how this is triggered (so far I have not been successful reproducing it).
What version of ilastik are you using, and what did you do in ilastik, roughly?
Cheers

Dominik