Hi Nick, Sorry to resurrect this thread, but I just wanted to mention I ran into the same issue, and how I avoided it. I ran a MocoTrack study in explicit mode, which worked fine. I then set the following code: solver.set_multibody_dynamics_mode('implicit'); solver.set_minimize_implicit_multibody_ac...

Hi all, Two of my papers (PhD chapters) that used Moco have come out recently. The first is my paper on bird locomotion, where we've built and simulated a model of the emu to try to understand why birds use grounded running gaits at intermediate speeds. This came out last week in Science Advances LI...

Hi Brodie, Moco automatically adds a controller to each muscle when you run an optimization. It computes the control inputs (i.e., muscle excitation signals) or whatever problem you've defined. These are normalized (so between 0 &1, or perhaps bounded between 0.00001 & 1 or similar). Control input (...

Hi Nick, Adding the following goal throws no errors. %% Add peakGRFy maximization goal forceset = model.getForceSet() contactforcenames = {}; #to be reused in a different section of the script weight = -0.01; for f = 1:(forceset.getSize) force = forceset.get(f-1); CCN = force.getConcreteClassName()....

Hi all, I've been trying to think of ways to increase or decrease duty factors in a running simulation. The release notes for OpenSim 4.5 say Foot-ground contact forces can now be optimized (e.g., maximize contact impulse) via MocoOutputGoal using the new Outputs 'sphere_force' and 'half_space_force...

Ah got it, thanks! I'll edit my previous post to point out I was wrong.

Cheers,
Pasha

Hi Nick,

What would adding a regular Controller with multiple muscles added to it as I described achieve?

Cheers,
Pasha

HI Ana, Looking at the documentation again, it looks like it should have been addActuator(muscle_one) etc, not setActuator (which doesn't exist, like you said). mycontroller = Controller() mycontroller.addActuator(muscle_one) mycontroller.addActuator(muscle_two) model.addController(mycontroller) mod...

EDIT: my suggestion was based on the incorrect assumption that you can add multiple muscles to a "Controller" to achieve the desired result, but this was not correct, Nick suggested later in the thread to use the newly added SynergyController(). /EDIT Hi Ana, If you load a model into a problem that ...

Hi Nick,

I'll be excited to try it out! I think in situations where we're not too sure about the muscle architecture (but are confident about the muscle mass), this would be a cool feature to have. There are also many other applications of such a customizable goal.

Best wishes,
Pasha