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 ...

Hello, Thanks for reporting but it's not clear where the script you're referring to comes from. If it's published by us we'll need to fix and incorporate into our testing suite. If however this is your custom code, we'll need to find out what changed, and when and if we confirm the API has changed, ...

Hello, Looking at the code/line where the exception occurs, it seems to be a corner case where the wrapping algorithm reports that a wrapping has occurred but also reports no actual wrap points. It's an internal inconsistency between the core libraries and the application/GUI that we need to account...

Hi Ekaterina, If you have the application installed, you can go to the help->Report a bug option, just make sure to describe the environment you're using and include any model/data/minimal code files necessary to reproduce. If you're on github you can open a new issue on the repository https://githu...

Hi Ekaterina, Thanks for reporting, looking at the change log nothing stands out as potential reason for this change of behavior other than possibly using a different python version/environment. Please open an issue and provide a description of your environment (Python distribution/version, IDE if a...