Small force range

Provide easy-to-use, extensible software for modeling, simulating, controlling, and analyzing the neuromusculoskeletal system.
POST REPLY
User avatar
Moe Curtin
Posts: 43
Joined: Fri Oct 02, 2009 5:40 am

Small force range

Post by Moe Curtin » Thu Jan 21, 2010 4:27 am

When using the CMC tool I get a warning for some muscles, e.g. "WARN - small force range for muscleX ( A to B )"

What exactly are numbers A and B and what muscle parameters do I need to be addressing to change this?

Thanks,

Moe

User avatar
Tim Dorn
Posts: 125
Joined: Tue Feb 26, 2008 10:14 pm

RE: Small force range

Post by Tim Dorn » Sun Jan 24, 2010 5:55 am

Hi Moe,
I believe the way CMC works is at each time frame, given the current "pose" of the model, a check is done to see what force each muscle can produce with muscle excitation u = 0 (value A) and u = 1 (value B). If a muscle is operating at a "very short" or "very long" fiber length (away from it's optimal fiber length), it can not produce much force (even at full excitation u = 1), and hence it's force producing range is low. (A muscle's force producing range is also low if it is contracting at a velocity near Vmax).

A warning is issued, but this is not necessarily a bad thing: it is only a bad thing if that particular muscle is required to produce torque, but otherwise, it is just saying that no real control can be offered to that muscle at that time due to the "state" of the muscle.

Say for example say you are simulating an activity where there are high levels of hip flexion, your iliacus & psoas muscles at high hip flexion may be operating way in the low ascending of the F-L curve, hence unable to generate any active force. But if a hip extensor moment is required at that point in time to bring the thigh back, then it doesn't matter if the hip flexors have a small range because they will not be activated anyway.

Tim

User avatar
Moe Curtin
Posts: 43
Joined: Fri Oct 02, 2009 5:40 am

RE: Small force range

Post by Moe Curtin » Tue Jan 26, 2010 5:30 am

Thanks Tim!

POST REPLY