You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But actually, this is very similar to the input specs of napari workflows, just with slightly different limits: we can only use "image" as type and only have up to 2 images, where order matters
=> let's see whether we can use a variant of what we build for napari workflows input & output arguments here as well!
The text was updated successfully, but these errors were encountered:
The review of input arguments & the discussions on pydantic models for napari workflows (e.g. #404) and channel (#386 (comment)) made me think:
We should also refactor the way we handle the channel inputs in Cellpose.
Currently, we do:
But actually, this is very similar to the input specs of napari workflows, just with slightly different limits: we can only use "image" as type and only have up to 2 images, where order matters
=> let's see whether we can use a variant of what we build for napari workflows input & output arguments here as well!
The text was updated successfully, but these errors were encountered: