Skip to content

[WIP] Model Updates (Contributed by Muscle Mimic Team)#73

Draft
vikashplus wants to merge 23 commits into
devfrom
model_upgrade_vk
Draft

[WIP] Model Updates (Contributed by Muscle Mimic Team)#73
vikashplus wants to merge 23 commits into
devfrom
model_upgrade_vk

Conversation

@vikashplus

@vikashplus vikashplus commented Feb 20, 2026

Copy link
Copy Markdown
Contributor

NOTE: This PR is a WIP. [Accepting contribution/ issues/ feedback on all fronts]

AUTHORS: Bianca Ziliotto, Chengkun Li, Huiyi Wang

This update, contributed by the muscle mimic team, brings in important functional updates to myo_sim model. Notably,

  • Addition of Left arm model
  • Improved muscle wrapping
  • Improved Left-Right asymmetries

ToDos

  • Add full contribution and credits to the musclemimic team at all places
  • Integrate model updates (@vikashplus)
  • Sync ArmL with ArmR (@cherylwang20)
  • Add proper change log to all individual models
  • Add figures for new models
  • Add reference to the model studies
  • Add model test scripts
  • Run and comply with all test scripts (@cherylwang20)

  - Corrected left-right limb asymmetries in joint definitions
  - Fixed muscle-jumping behaviors at joint limits
  - Added collision pairs for leg-leg and foot-foot self-contact
@vikashplus vikashplus marked this pull request as draft February 20, 2026 17:02
Comment thread leg/assets/myolegs_assets.xml
Comment thread leg/assets/myolegs_chain.xml
Comment thread leg/assets/myolegs_chain.xml Outdated
Comment thread leg/assets/myolegs_muscle.xml
Comment thread leg/assets/myolegs_muscle.xml Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in other models e.g. arm, myolegs_tendon.xml was integrated into myolegs_assets.xml

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's helpful to have it separated incase one wants to create a simpler model without the tendons.
mjSpec can definitely handle such usecases. It should be handled in a separate scope, if relevant.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it makes sense. We should have this for other models too

Comment thread body/myobody.xml Outdated
<worldbody>
<body name="Full Body" pos="-.025 0.1 1">
<include file="../torso/assets/myotorso_chain.xml"/>
<body name="Full Body" pos="-.025 0.1 1" euler="0 0 -1.57">

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wouldn't this be problematic for the initial condition (assuming the previous one was the correct one)?

@vikashplus vikashplus Feb 22, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The previous one was in-consistent with rest of our models.

cherylwang20 and others added 11 commits May 14, 2026 23:31
Update torso and leg geom color
created myofulbody.
…etection. Updated euler angles for left arm components and removed deprecated myobody and myotorso_bimanual_chain files. Enhanced myotorso_arm_chain with new collision geometries for self-contact.
…in myofullbody.xml for improved model alignment.
…aints and improve moment arm and force-length curve calculations. Updated XML asset files for leg model adjustments and corrected joint axis orientations.
…prove consistency in naming conventions. Adjusted euler angles for various body components to ensure accurate positioning. Enhanced leg and torso collision geometry for better interaction in simulations.
@Vittorio-Caggiano

Copy link
Copy Markdown
Contributor

While reviewing the contribution from the musclemimic team, we observed that the proposed changes go well beyond incremental fixes and introduce a number of structural and numerical differences relative to the current myo_sim models. We now have a fairly comprehensive equivalence report comparing the two MyoFullBody models, and although the majority of actuators match closely, there are several important divergences in geometry, wrapping definitions, joint ranges, and muscle parameters.

Some of the differences identified include:

  • left knee wrapping geometry inconsistencies leading to moment arm errors up to ~19 mm and force discrepancies up to ~59%
  • swapped thumb CMC joint ranges (cmc_flexion vs cmc_abduction)
  • sign inversion in LTpT_T12_l
  • overwritten gainprm values for SUPSP
  • additional smaller but systematic wrapping differences in shoulder/arm assets

These are not isolated parameter changes; they affect model behavior, numerical equivalence, and backward compatibility with the current myo_sim release. In parallel, the current repository organization also likely needs restructuring (see proposal in [Issue #75](https://github.com/MyoHub/myo_sim/issues/75?utm_source=chatgpt.com)), which further complicates maintaining compatibility layers.

Given this, I think we effectively have two paths forward:

  1. Attempt to create a hybrid model between the current myo_sim and the musclemimic version.
    This would likely preserve neither strict backward compatibility nor clean equivalence with the musclemimic reference. It would also increase maintenance burden since we may end up supporting both a hybrid myo_sim branch and the upstream musclemimic evolution.

  2. Deprecate the current models and reorganize the repository around the musclemimic model structure.
    The musclemimic team has already been iterating actively on these models and several of the identified issues appear to already be improved or corrected there. Aligning with that structure may reduce long-term divergence and simplify future maintenance/testing.

At the moment I lean toward option 2, mainly because it provides a cleaner long-term direction and avoids accumulating compatibility debt. That said, there may still be additional considerations from other contributors/users that we should take into account before deciding on the migration strategy.

Please, let me know your thoughts @vikashplus @cherylwang20 @CharlieLeee

@vikashplus

Copy link
Copy Markdown
Contributor Author

Duplicate and diverging models will be very hard to jointly develop as well as maintain. The need of a more structured organization has been felt for a while. We should be forward looking and make fast progress. Incase old references are needed, we do have previous tagged versions for users to resort to.

Having said that, there is merit in taking some time to carefully plan for the upgrade. Modeling editing and compositions can become complex. Additionally, there are myo_sim, myo_skeleton, muscle_mimic. Getting to a common base will be very important to avoid divergence.

@Vittorio-Caggiano

Copy link
Copy Markdown
Contributor

Duplicate and diverging models will be very hard to jointly develop as well as maintain. The need of a more structured organization has been felt for a while. We should be forward looking and make fast progress. Incase old references are needed, we do have previous tagged versions for users to resort to.

Having said that, there is merit in taking some time to carefully plan for the upgrade. Modeling editing and compositions can become complex. Additionally, there are myo_sim, myo_skeleton, muscle_mimic. Getting to a common base will be very important to avoid divergence.

sg. Is there any concern about this current design? #75

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants