ROIUtil deprecation

[Davide Heller]

Hi guys, 

I noticed the deprecation of many ROIUtil methods with icy 1.7. Specifically I have been using the following

intensity_readout = ROIUtil.getMaxIntensity(sequence, roi, z, t, c);

Could you show me the preferred way to substitute this line? I saw the static ROIMaxIntensityDescriptor.computeMaxIntensity method but it lacks t, z, c parametrization. 

Thanks a lot,

Davide

[Stephane]

Hi Davide,

Indeed now we use the ROIDescriptor interface to get computation information from ROI.
In your case as you discovered you have to use

ROIMaxIntensityDescriptor.computeMeanIntensity(ROI roi, Sequence sequence)

and to specify a specific t, z, c parameter you need to use roi.getSubROI(z, t, c) so you will retrieve a ROI only for the specified Z, T, C position.

Best,

- Stephane

[Davide Heller]

Hi Stephane, 

thanks for your fast reply. I will apply the changes you suggested. Can you give me an approximate date when the ROIUtil methods will be removed? (looks like the getCopy mechanism in ROI2D.getSubROI is not appreciated by one of my wrapper classes:-)

Cheers, 

Davide

[Stephane]

Hi Davide,

We keep the deprecations for a *long* time so don't worry about it if you can't get your getCopy() method working quickly.
Still internally Icy uses a lot the ROI.getCopy() method (ROI statistics calculation and others operations) so you may look if your wrapper does not miss some results here.

Cheers,

- Stephane