CMC and Static Optimization fails with Disabled Muscle

[Alex MacIntosh]

Hello,

I am trying to analyze a model while removing the influence of a muscle. In the OpenSim GUI I have disabled a muscle and then tried to run an analysis. When I do this however, either the tool immediately fails or I get an error message (below).

When I try to run CMC with a disabled muscle the tool closes and says:

Tool execution failed or cancelled by user. Output files were not written

When I try to run a static optimization with a disabled muscle I get this error:

java.lang.RuntimeException: SimTK Exception thrown at State.cpp:2080:
State Cache entry was out of date at Stage Acceleration. This entry depends on version 23 of Stage Velocity but was last updated at version 3.
at org.opensim.modeling.opensimModelJNI.AnalyzeTool_run__SWIG_0(Native Method)
at org.opensim.modeling.AnalyzeTool.run(AnalyzeTool.java:154)
at org.opensim.tracking.AnalyzeToolModel$AnalyzeToolWorker.construct(AnalyzeToolModel.java:136)
at org.opensim.swingui.SwingWorker$2.run(SwingWorker.java:108)
[catch] at java.lang.Thread.run(Thread.java:662)

I have reproduced this issue with OpenSim 3.1, 3.0 and on multiple models. This also occurs while running through the command line.

If anyone has/has not had this issue, or has suggestions as to how to fix/work around it, your help would be greatly appreciated.

Thanks,

Alex

[Ilan Eskinazi]

What happens if you delete the muscle altogether, and try to run it?

[Yusuke Okita]

Hi Alex,

I am working on the similar topic.
So far I never succeeded in running CMC or static optimization with disabled muscles on version 3.1.
I run them after deleting muscles from the .osim file as said above.

Best regards,
Yusuke Okita

[Alex MacIntosh]

Thank you for your replies,

I too am deleting the muscles to get the same effect, and this works fine. I just wanted to make sure I was not the only one with the issue.

Thanks

Alex

[jimmy d]

Hi-
We have been able to reproduce this bug and will address. The problem seemingly comes from the tools using a getMuscles() method that results in the number of possible states not matching the states being initialized.

As you you have seen, the workaround is to delete the muscle and run.

Thanks for finding!
-james

[Alex MacIntosh]

Thanks so much for taking a look at it so quickly.

Alex