Skip to content

Java Issue - ImageJ vs Fiji #6

@MrImaging

Description

@MrImaging

Hello,

I just downloaded this interesting plugin today, along with a fresh install of Fiji.

When using ImageJ-win64.exe located in the directory Fiji.app, selecting ImDecorr from the plugins menu results in the following console output:

ImageDecorrelationAnalysis_ not up-to-date because 1 source files are not up-to-date (C:\Users\...\AppData\Local\Temp\java...\src\main\java\ImageDecorrelationAnalysis_.java)
Compiling 1 file in C:\Users\...\AppData\Local\Temp\java...

Resolution can nevertheless still be estimated as 0.116 microns for test_image.tif, provided in this repository.

When starting the fiji-windows-x64.exe instead, in addition to the output above, 4 errors are thrown and the plugin (popup) will not start:

...
C:\Users\...\AppData\Local\Temp\java...\src\main\java\ImageDecorrelationAnalysis_.java:274: error: cannot find symbol
			ImageDecorrelationAnalysis IDA = new ImageDecorrelationAnalysis(im,rmin,rmax,Nr,Ng,doPlot,null);
			^
  symbol:   class ImageDecorrelationAnalysis
  location: class ImageDecorrelationAnalysis_
...
4 errors
[ERROR] java.lang.ClassNotFoundException: ImageDecorrelationAnalysis_
	at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:419)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:352)
	at org.scijava.plugins.scripting.java.JavaEngine.compile(JavaEngine.java:228)
	at org.scijava.plugins.scripting.java.JavaEngine.eval(JavaEngine.java:136)
	at org.scijava.script.ScriptModule.run(ScriptModule.java:173)
	at org.scijava.module.ModuleRunner.run(ModuleRunner.java:165)
	at org.scijava.module.ModuleRunner.call(ModuleRunner.java:125)
	at org.scijava.module.ModuleRunner.call(ModuleRunner.java:64)
	at org.scijava.thread.DefaultThreadService.lambda$wrap$2(DefaultThreadService.java:247)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:750)

According to Help - About ImageJ, both are/use ImageJ 1.52v and Java 1.8.0_452 (64-bit), the task bar also displays "(Fiji Is Just) ImageJ for either executables. Except for the size of the executables I was not able to discern any difference between them, other than ImDecorr only working in one of them.

I might have missed the value being displayed somewhere, but could you please confirm if 0.116 microns is the value to expect for the test image to verify the analysis is working corretly in at least one of those 2 cases?
Is there an obvious reason to why not both executables can run the plugin?

Thank you very much for your support!
Kind regards!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions