Open ctrueden opened 6 years ago
You should be using the main branch (master) instead of a deprecated branch (your link points to very very old code...)
(your link points to very very old code...)
Dude, it is the latest tag. And the last commit to touch that source file is the same on master still. I never post links to master because it will change out from under you over time, invalidating the link.
Oh I see, I saw some cuda flags and assumed it was very old code. I would test in FiJi first and see how it goes, my guess is that there is a GPU, GPU driver problem, or the native libs of JOCL are missing...
I am guessing this is a MATLAB-specific issue; from the original thread, it sounds like the plugin works when launched from Fiji normally.
I was thinking it might be some subtle thing with MATLAB's JRE, but upon reflection, perhaps it is as simple as the JARs from the jars/<platform>
folder not being added to MATLAB's classpath.
I do not have time to test it, but Andreas, if you are reading this: you could try:
javaaddpath 'C:\Users\andreas\Fiji.app\jars\win64'
Where C:\Uesrs\andreas\Fiji.app
is the location of your Fiji installation.
And see if that makes a difference. See the javaaddpath documentation for details.
ctrueden, I attempted your solution.
I did
javaaddpath 'C:\Users\Swag\Documents\4D-SoftwareChet\ae4d-master\Fiji.app\jars\win64'
My MatLab Execution is attached and so is the ImageJ execution error. MATLAB.txt ImageJ.txt
I attempted a clean installation of Fiji, the newest version available. Opened my MatLab version that is running:
Java 1.8.0_144-b01 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
Added to my path
'C:\Users\Swag\Documents\4D-SoftwareChet\ae4d-master\Fiji.app\scripts'
Than by suggestion from ctrueden did
'javaaddpath 'C:\Users\Swag\Documents\4D-SoftwareChet\ae4d-master\Fiji.app\jars\win64'
Getting the same error as mentioned before. It is possible that clearVolume does not work with Imagej-MatLab
From Andres Barragan via the ImageJ mailing list:
I investigated a little, and based on the relevant code, I guess that
ClearVolumeRendererFactory.newBestRenderer
and/orClearVolumeRendererFactory.newOpenCLRenderer
must be returning null. But more investigation required to discern why that would be the case from a MATLAB environment.