visual3d:documentation:pipeline:model_based_data_commands:default_joint_names
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| visual3d:documentation:pipeline:model_based_data_commands:default_joint_names [2024/06/19 14:01] – created sgranger | visual3d:documentation:pipeline:model_based_data_commands:default_joint_names [2024/07/17 15:46] (current) – created sgranger | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Definition of a Joint ===== | + | ====== Default Joint Names ====== |
| + | |||
| + | ==== Definition of a Joint ==== | ||
| We use the word " | We use the word " | ||
| Line 11: | Line 13: | ||
| If for example, a functional hip joint is computed and the landmark is not within the distal radius of the pelvis from the distal end of the pelvis, no joint will be created. This is not a problem for joint moments because the joint moment is really the proximal moment on the segment, so no joint is needed. This is, however, a problem for joint power because there will be no way to compute the joint angular velocity. If a joint has not been created where you expect it, check to see that he landmark is sufficiently close to the pelvis. | If for example, a functional hip joint is computed and the landmark is not within the distal radius of the pelvis from the distal end of the pelvis, no joint will be created. This is not a problem for joint moments because the joint moment is really the proximal moment on the segment, so no joint is needed. This is, however, a problem for joint power because there will be no way to compute the joint angular velocity. If a joint has not been created where you expect it, check to see that he landmark is sufficiently close to the pelvis. | ||
| - | ===== Default Joint Names ===== | + | ==== Default Joint Names ==== |
| Visual3D creates joint names automatically for the default segments. | Visual3D creates joint names automatically for the default segments. | ||
| Line 37: | Line 39: | ||
| |LHA |Left Hand | |LHA |Left Hand | ||
| - | ===== Custom Joint Names ===== | + | ==== Custom Joint Names ==== |
| The joint moment computed by Visual3D is expressed as the proximal moment on a segment. | The joint moment computed by Visual3D is expressed as the proximal moment on a segment. | ||
| Line 47: | Line 49: | ||
| If the link model is defined with a shank segment and no thigh segment, the joint moment at the proximal end can be computed, but the joint is given the name of the shank segment (e.g. [[Visual3D: | If the link model is defined with a shank segment and no thigh segment, the joint moment at the proximal end can be computed, but the joint is given the name of the shank segment (e.g. [[Visual3D: | ||
| - | ===== Custom Segment Joint Names ===== | + | ==== Custom Segment Joint Names ==== |
| If the user has created a custom segment name, Visual3D uses that segment name. | If the user has created a custom segment name, Visual3D uses that segment name. | ||
visual3d/documentation/pipeline/model_based_data_commands/default_joint_names.1718805701.txt.gz · Last modified: 2024/06/19 14:01 by sgranger