If you have two channels in for a process, they will probably get saved something like this: align&channel000align&channel001. These keys cannot be recognized by the mechanism for determining if something should be rerun. There are a few reasons for this, least of which is the name...
Most functions will use Same as the output type. This type isn't currently recognized by Pipeline. It should be recognized, and considered ambiguous. Pipeline should load whatever image it finds and use the name as the type, or have a default type.
The same needs to happen in ImageHelper and/or Operation, such that the output type can be predicted ahead of time. Basically same in the key, should get replaced with image, mask, etc.
The presence of the _split_key in the output name, means that the Operation won't ever find a name that exactly matches.
This probably won't happen until after the v0.0.0 patch.
If you have two channels in for a process, they will probably get saved something like this:
align&channel000
align&channel001
. These keys cannot be recognized by the mechanism for determining if something should be rerun. There are a few reasons for this, least of which is the name...Same
as the output type. This type isn't currently recognized byPipeline
. It should be recognized, and considered ambiguous.Pipeline
should load whatever image it finds and use the name as the type, or have a default type.ImageHelper
and/orOperation
, such that the output type can be predicted ahead of time. Basicallysame
in the key, should get replaced withimage
,mask
, etc._split_key
in the output name, means that theOperation
won't ever find a name that exactly matches.This probably won't happen until after the v0.0.0 patch.