Top Hat filter bug?

[Gabriel Landini]

Hi,
I found an unusual result when of applying the Top Hat filter to a stack 'one
slice at a time' :

for (i=1;i<=nSlices; i++) {
setSlice (i);
run("Top Hat...", "radius=15 light");
}

compared to 'processing all slices'.

run("Top Hat...", "radius=15 light stack");

The difference between the two results if not zero.
When processing all slices in one go I get a sudden jump every 4 slices or so.
I am running IJ 1.54j46 with Java 14.0.2 under linux.

Cheers,

Gabriel

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[Michael Schmid]

Hi Gabriel,

yes, you are right, there is something wrong. Since the top hat code
came from me, I'll have a look at it.


Michael
________________________________________________________________
On 01.06.21 12:37, Gabriel Landini wrote:

> Hi,
> I found an unusual result when of applying the Top Hat filter to a stack 'one
> slice at a time' :
>
> for (i=1;i<=nSlices; i++) {
> setSlice (i);
> run("Top Hat...", "radius=15 light");
> }
>
> compared to 'processing all slices'.
>
> run("Top Hat...", "radius=15 light stack");
>
> The difference between the two results if not zero.
> When processing all slices in one go I get a sudden jump every 4 slices or so.
> I am running IJ 1.54j46 with Java 14.0.2 under linux.
>
> Cheers,
>
> Gabriel
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[Wayne Rasband-2]

On Jun 1, 2021, at 6:37 AM, Gabriel Landini <[hidden email]> wrote:

>
> Hi,
> I found an unusual result when of applying the Top Hat filter to a stack 'one
> slice at a time' :
>
> for (i=1;i<=nSlices; i++) {
> setSlice (i);
> run("Top Hat...", "radius=15 light");
> }
>
> compared to 'processing all slices'.
>
> run("Top Hat...", "radius=15 light stack");
>
> The difference between the two results if not zero.
> When processing all slices in one go I get a sudden jump every 4 slices or so.
> I am running IJ 1.54j46 with Java 14.0.2 under linux.

Thanks to Michael Schmid, this bug is fixed in the ImageJ 1.53k5 daily build.

-wayne

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html