zitmen / thunderstorm

ThunderSTORM: a comprehensive ImageJ plugin for SMLM data analysis and super-resolution imaging
http://zitmen.github.io/thunderstorm/
GNU General Public License v3.0
92 stars 42 forks source link

Use of the reset command in "Show results table" within macro change units from analogue to digital #6

Closed zitmen closed 9 years ago

zitmen commented 9 years ago
What steps will reproduce the problem?

1. Create a macro to successively perform and export several filtering possibilities
(see examples attached).
2. Run the command [ run("Show results table", "action=reset")
] (line 161 in macro_thunderstorm_defect.txt) between each [ run("Show results
table", "action=filter ....") ] commands
3. The units in the table change from analogue to digital after the first iteration
of the loop, hence adding confusion to subsequent filtering.

What is the expected output? What do you see instead?

The units in the opened results table (both in headers and within the values) change
from nm and photons to pixels and ADU.

What version of the product are you using? On what operating system?

Windows 7 SP1 [64-bit], on i7-4930K CPU @ 3.40GHz 64GB RAM 250GB SSD (OS + docs)
Fiji ImageJ core 1.48s - Java 1.6.0_24 [64-bit]
ThunderSTORM dev-2014-03-04-b1 still has the issue described here

Please provide any additional information below.

The units of the image and the preview do not change. I cannot call the command to
revert the units from within the Macro although I can still revert the units by right-clicking
on the column header.
I couldn't reproduce the same problem without using macro scripting.
My current workaround is to export the table and re-import at every iteration which
isn't too bad really (added lines 151-153 and 157-158 in macro_thunderstorm_works.txt)!
And thanks for making thunderSTORM such a great tool for data analysis. Fingers crossed
for the paper!

Cheers,
Alex

Original issue reported on code.google.com by alex.f.carisey on 2014-03-23 15:29:39


zitmen commented 9 years ago
This issue was closed by revision 2c2e2e6ffbea.

Original issue reported on code.google.com by vmodrosedem on 2014-03-25 08:40:38