Ticket #1885 (closed defect: fixed)

Working with large datasets points out the need for autoscale computations to sometimes only calculate on the current plane of the data rather than the whole dataset. There are various places in the code where we call ComputeMinMax and a couple places where we simply loop over pixels using cursors. We should have all of these utilize a AutoscaleService.

The AutoscaleService could be modeled after the ThresholdService. There would be AutoscaleMethods that are autodiscovered. ANd the service would have at least one method called defaultMethod() that returns a method that computes min/max for complete IterableInterval given. It would be API users's job (maybe) to pass the interval of interest (one plane, whole image).

We could extend the service to not just find methods but also run the one found.

To fix the cell img slow autoscale problem we pass only the current plane to the autoscaleService. ALternatively the default autoscale method could work on single plane only. (I like 1st approach better as you can separate calculation algorithms from calculation regions).

There are currently two entry points to this mini-project: DefaultDatsetView::autoscale() and the brightness contrast plugin. Note: DefaultDatasetView::autoscale() should be deprecated and internally it should call autoscale service.