[Insight-developers] min. max over ROI (floodfilliterator)

[Luis Ibanez]

It seems that the image calculator makes more sense.
At least until the pervasive pipelining is in place.

Checking for the modified time is a good idea, we should
do it in all the calculators.

It will also be helpful to make Calculators invoke
Start and End events, since they can be used for
triggering updates in other filters that may depend
on the output of the calculator.


    Luis


---------------------
Stephen R. Aylward wrote:
> Hi,
> 
> Should the itk "thing" to calculate a min, max, etc of an image for an 
> ROI (done internally using the floodfilliterator) be implemented as a 
> filter or an image calculator?
> 
> As a filter, it doesn't produce an image as an output.
> 
> An image calculator seems appropriate, but it will cause a recalc on 
> every call since they don't (by default) keep track of whether or not 
> the input has changed (could be done, however, by having the calculator 
> monitor the input image's modified time - Julien's suggestion).
> 
> We have image min, max, etc implemented both ways in itk at this time.
> 
> Will do as an image calculator unless I (Julien) hear otherwise.
> 
> Thanks,
> Stephen
>