Dear OpenSim Moco Community, I am trying to perform a MocoTracking study with Contact Tracking. However, the newly generated ground reaction forces are very different from the measured GRF signals (see file attached). Changing tracking weights between the coordinate tracking, effort and grf tracking...

Dear Nicholas, thanks for your fast response. Yes I am using "DeGrooteFregly2016Muscle" but I am not sure that 'not updating' is the problem. I first use parameter optimization to define new values for tendon slack and opt fibre length--> then generate a moco solution with MocoInverse. If I use the ...

Dear OpenSim Moco community, I am testing the effect of parameter optimization on muscle force computations during gait. The problem I encounter is that after- optimizing tendon lack and opt fiber length Moco does not find a solution. With the scaled-only model it does find a solution. The solver se...

Hi Carlos,

thanks for your suggestions....some time ago but still relevant...... .

Could you maybe clarify how you integrated the MocoStateTrackingGoal and MocoContactTrackingGoal into a MocoProblem?

Thanks and kindregards

Christian

Thanks a lot Nick! That solved the problem....

Regards

Christian

Dear Moco users, I am trying to perform muscle analysis on a Moco Solution in Python. First I used this code: solution = study.solve() outputs = osim.StdVectorString() outputs.append('.*active_force_length_multiplier') table = study.analyze(solution, outputs) However, I received the error message th...

Dear Moco users and developer team, I am working on a MocoState Tracking problem. In the end, I want to use MocoTrack to validate some output from ParameterOptimization. I want to establish which muscle-tendon parameter configurations are best to track measured kinematics and GRFs. As a first step I...

Dear Ross and Nick, I did some debugging on my code and figures that the TendonVGoal is causing trouble. I set the initial weight to 0.001 and it would not converge....but decreasing the weight even further it converges within 90 iterations. I am not sure whether the VGoal still does something but a...

Thanks for the reply. But the problem is that the coordinate values (e.g. ankle angle) and coordinate speeds are not in the solution. When calling study.solve it only computes and writes the activations, excitations and reserve forces. Is that because I am using MocoInverse to prescribe the motion a...

Thanks a lot Ross, @investigating failed solution. I do have some trouble to implement the .analyze() function in the MocoStudy. I think the problem is that there are no states in the solution. At least that is what I make out of the error message below. Could you give me some hint how to add the st...