Hello, A reasonable approach would be to get the number of markers in use from the solver solver.getNumMarkersInUse() Then cycle through this list in turn and print the corresponding names using solver.getMarkerNameForIndex(index) The challenge that the solver is dealing with is that there're multip...

Thanks Mohammadreza,

Indeed the function was introduced post 4.5 but should be available in 4.5.1 which is also available as a conda package.

Hope this helps,
-Ayman

Hello Hanzhe Li, This looks very similar to an issue we fixed lately that was caused by calling the method on markers that are not in the intersection of model markers and those in the trc file. Code innocently assumed names passed in to be valid. Now we throw exceptions but earlier versions would h...

Hello, As described on the page you linked to, using conda packages is the best and most easily supported pathway to getting opensim to work under python. Since you're using version 4.5, you should find the packages here https://anaconda.org/opensim-org/opensim If for some reason you must use the in...

Hi Rahmatullah, Best of luck with your effort to integrate your finite element model with OpenSim. As it stands I'm not aware of a streamlined workflow for this process. Similar to most modeling/simulation environments, OpenSim natively supports importing (one-way) geometry from modeling packages us...

Hi Walter, Thanks for reporting. Can you explain how you're getting the OpenSim python bindings? Basically before version 4.0 we used to build in-house bindings with a fixed version of python. Considering that OpenSim 3.3 was released in 2015 and used the python version available then, it's not surp...

Hi Sunny, The core libraries and scripting interfaces can all be compiled from source on arbitrary new platforms, if you try compiling from source and run into problems please open issues on github and we'll address. As to the GUI/application, it has extra dependencies on more third party tools and ...

Thanks for reporting, For the record, OpenSim version 3.3 used vtk's native libraries to load .vtp files so they were able to parse more vtk based files. As of version 4.0, due to switching to a visualizer that's not based on vtk, we use the Simtk native parsers instead, which are much smaller and w...

Hi Arthur, Wonderful to hear from you, and thanks for reporting. If you're able to build the OpenSim API then you can enable python bindings by turning on a flag (BUILD_PYTHON_WRAPPING in CMake) and that will locate/try-to-find other needed tools (e.g. swig) and the python available on the build mac...

Hello, Removing the muscles form the model should be easy though it involves editing the xml file of the model (.osim). You just remove the xml blocks for the corresponding muscles (typically these have the full class names rather than just "Muscle" e.g. "Millard2012EquilibriumMuscle"). If you have ...