Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analyze Particles creates unexpected measurement #211

Open
schmiedc opened this issue May 24, 2023 · 0 comments
Open

Analyze Particles creates unexpected measurement #211

schmiedc opened this issue May 24, 2023 · 0 comments

Comments

@schmiedc
Copy link

schmiedc commented May 24, 2023

I created a macro to just count objects in a binary image.
For this I add the objects to the ROI manager and read out the number of ROIs.
The number of ROIs are then added to the result table.

However I noticed that apparently Analyze Particles creates per ROI a measurement.
As far as I can tell I did not select any measurement options.

I used Fiji on Ubuntu 22.04.

Here is a macro that reproduces that issue:

`
run("Set Measurements...", " redirect=None decimal=3");

run("AuPbSn 40");

setAutoThreshold("Default dark no-reset");
//run("Threshold...");
//setThreshold(126, 255);
setOption("BlackBackground", true);
run("Convert to Mask");
run("Analyze Particles...", "show=Nothing add");

result = roiManager("count");

setResult("count", 0, result);
`

It then produces this result table:

1 41
2 0
3 0
4 0
5 0
6 0
7 0
8 0
9 0
10 0
11 0
12 0
13 0
14 0
15 0
16 0
17 0
18 0
19 0
20 0
21 0
22 0
23 0
24 0
25 0
26 0
27 0
28 0
29 0
30 0
31 0
32 0
33 0
34 0
35 0
36 0
37 0
38 0
39 0
40 0
41 0

It does not come from the ROI manager as when I just add ROIs manually to the ROI manager these measurements are not created. Selecting "clear results" in the particle analyzer does not fix the issue.

For me this behavior was surprising. Mind also that without writing the ROI manager count in the results table the 0 measurement per ROI is also not visible actually. As no results table is opened. Further indicating for me that this was unintentional and maybe erroneous measurements are created in the background.

There are other ways I can get the same workflow going. Maybe I overlook also a setting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant