MATLAB Answers

Chris
0

Builder JA Error with private file (dicominfo)

Asked by Chris
on 11 Dec 2013
Latest activity Answered by Ashish Uthama on 17 Dec 2013
I'm trying to build/run a java class from matlab that among other things reads a dicom image.
I'm working from the spectralanalysis example in matlab, and have simply added the following line (with appropriate path info):
RSInfo = dicominfo([p flz2(1).name]);
I've added dicomparse.mexw64 under the "Shared resources and helper files" section of the javapackage builder UI (which during build add's the correct:
-a 'C:\Program Files\MATLAB\R2013a\toolbox\images\iptformats\private\dicomparse.mexw64'
However upon trying to run the resulting jar file, I get:
F:\testUser\jabuilder_test\spectral\spectralanalysis\distrib>java -classpath "C:\
Program Files\MATLAB\R2013a\toolbox\javabuilder\jar\javabuilder.jar";spectralana
lysis.jar spectralanalysis.fourier > test.txt
Invalid MEX-file 'C:\Users\testUser\AppData\Local\Temp\2\testUser\mcrCache8.1\spec
tr5\toolbox\images\iptformats\private\dicomparse.mexw64': The specified module c
ould not be found.
Error in dicominfo (line 44)
Error in plotfft (line 24)
Unable to print provided exception.
Caused by:
Errors occurred while loading the Settings files.
Details: C:\Program Files\MATLAB\R2013a\toolbox\matlab\matlab.settings
Internal Error: Failed to find SAX plugin.
C:\Users\testUser\AppData\Local\Temp\2\testUser\mcrCache8.1\spectr5\.matlab\ma
tlab.settings Internal Error: Failed to find SAX plugin.
There is no Settings files associated with this product node: matlab. The Se
ttings files may be deleted after MATLAB started up. Please restart MATLAB to fu
lly solve this issue.
.
Is there any easy fix? Or a solid example of using private mex files in a builder JA?

  4 Comments

Show 1 older comment
I get the error either way. I even tried a simple:
t = imread('test.png');
and it produced a similar error (though a png related mex file instead of the dicom one)
Did any of the documented examples work for you? (To rule out a corrupt install). IMREAD ought work out of the box, your best bet is to contact support at this point.
The problem turned out to be Java 1.7 being incompatible with Matlab2013a. The documented examples like computing the FFT worked with 1.7 but mexfiles did not.

Sign in to comment.

1 Answer

Answer by Ashish Uthama on 17 Dec 2013
 Accepted Answer

Chris:
The problem turned out to be Java 1.7 being incompatible with Matlab2013a. The documented examples like computing the FFT worked with 1.7 but mexfiles did not.

  0 Comments

Sign in to comment.