Seemingly random Java error; batch IK with matlab
Posted: Fri Dec 08, 2017 3:31 pm
Hi forum readers!
I'm attempting to batch process some IK trials using matlab (2015a and OpenSim 3.3, both 64 bit), which I've done several times in the past and don't recall having any trouble, but I'm now receiving a sporadic java error. Sometimes the error occurs on the first trial processed, sometimes the 2nd, or 3rd, etc. and sometimes not at all. It's all over the place and the unpredictability is driving me crazy!
The Java error displayed in matlab is:
And when I check the out.log file, the error is: "InverseKinematicsTool Failed: bad allocation"
After searching the forum, it sounds like this could be a Java memory error. Does this sound familiar to anyone? Anybody have any ideas on how to correct the problem, work around it, or at least predict when it will happen? For now I just keep re-running the batch file (without changing anything!) until it works successfully, but it's pretty frustrating and I'm not happy with that 'solution'. Also, occasionally matlab crashes (Fatal Error warning forcing matlab to close) rather than returning the Java error, also with no predictability.
Thanks!
Becky
I'm attempting to batch process some IK trials using matlab (2015a and OpenSim 3.3, both 64 bit), which I've done several times in the past and don't recall having any trouble, but I'm now receiving a sporadic java error. Sometimes the error occurs on the first trial processed, sometimes the 2nd, or 3rd, etc. and sometimes not at all. It's all over the place and the unpredictability is driving me crazy!
The Java error displayed in matlab is:
Code: Select all
Java exception occurred:
java.io.IOException: InverseKinematicsTool Failed, please see messages window for details...
at org.opensim.modeling.opensimModelJNI.InverseKinematicsTool_run(Native Method)
at org.opensim.modeling.InverseKinematicsTool.run(InverseKinematicsTool.java:137)
After searching the forum, it sounds like this could be a Java memory error. Does this sound familiar to anyone? Anybody have any ideas on how to correct the problem, work around it, or at least predict when it will happen? For now I just keep re-running the batch file (without changing anything!) until it works successfully, but it's pretty frustrating and I'm not happy with that 'solution'. Also, occasionally matlab crashes (Fatal Error warning forcing matlab to close) rather than returning the Java error, also with no predictability.
Thanks!
Becky