Right now, setting nuc_slice to -1 in the config file results in a max-projection; this is also the default.
But it can also seemingly be set to an array slice-like value, and it's irrelevant in the case of 3D nuclei segmentation.
The structure and meaning of the available options for this config setting value should be better encoded and documented, and the relationship between nuc_3d and this one needs to be better captured and enforced, to simplify things for the end user and to make it more clear how the program will behave under different combinations of settings.
Right now, setting
nuc_sliceto -1 in the config file results in a max-projection; this is also the default. But it can also seemingly be set to an array slice-like value, and it's irrelevant in the case of 3D nuclei segmentation. The structure and meaning of the available options for this config setting value should be better encoded and documented, and the relationship betweennuc_3dand this one needs to be better captured and enforced, to simplify things for the end user and to make it more clear how the program will behave under different combinations of settings.Related: #206 , #90 , #14