@@ -25,12 +25,21 @@ then the GUI will automatically run 3D segmentation and display it in the GUI. W
2525the command line for progress. It is recommended to use a GPU to speed up processing.
2626
2727In the CLI/notebook, you need to specify the ``z_axis `` and the ``channel_axis ``
28- parameters to specify the axis (0-based) of the image which corresponds to the image channels and to the z axis.
29- For example an image with 2 channels of shape (1024,1024,2,105,1) can be
30- specified with ``channel_axis=2 `` and ``z_axis=3 ``. These parameters can be specified using the command line
31- with ``--channel_axis `` or ``--z_axis `` or as inputs to ``model.eval `` for
28+ parameters to specify the axis (0-based) of the image which corresponds to the image channels and to the z axis.
29+ For example an image with 2 channels of shape (1024,1024,2,105,1) can be
30+ specified with ``channel_axis=2 `` and ``z_axis=3 ``. These parameters can be specified using the command line
31+ with ``--channel_axis `` or ``--z_axis `` or as inputs to ``model.eval `` for
3232the ``CellposeModel `` model.
3333
34+ As a convenience, :func: `cellpose.io.imread_3D ` will attempt to load a 3D image and
35+ automatically guess the axes. For grayscale images (3D array), axis 0 is assumed
36+ to be the Z axis (e.g., Z x Y x X). For multichannel images (4D array), the
37+ channel axis is assumed to be the smallest dimension, and the Z axis is assumed to
38+ be the first remaining axis after the channel axis is identified (e.g., for a
39+ Z x C x Y x X image, channel axis = 1 and z axis = 0). If your image does not
40+ follow these conventions, use ``cellpose.io.imread `` and specify ``z_axis `` and
41+ ``channel_axis `` manually.
42+
3443Volumetric stacks do not always have the same sampling in XY as they do in Z.
3544Therefore you can set an ``anisotropy `` parameter in CLI/notebook to allow for differences in
3645sampling, e.g. set to 2.0 if Z is sampled half as dense as X or Y, and then in the algorithm
0 commit comments