HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » modeling » muscles » Muscles Overview
visual3d:documentation:modeling:muscles:muscles_overview

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
visual3d:documentation:modeling:muscles:muscles_overview [2024/07/17 15:45] – created sgrangervisual3d:documentation:modeling:muscles:muscles_overview [2025/10/02 19:53] (current) – Cleaned up References section. wikisysop
Line 1: Line 1:
-====== Muscles Overview ======+===== Muscles Overview =====
  
-Muscles are defined by linear segments connecting a series of Landmarks. The Landmarks can be created using any of the rules for creating landmarks in Visual3D.+Visual3D allows users to define muscles as linear segments connecting a series of landmarks. These [[visual3d:documentation:modeling:landmarks:landmarks_overview|landmarks]] can be created using any of the rules for creating landmarks in Visual3D.
  
-=== Muscle Tab ===+Muscles are created and edited from the **Muscle Tab** in [[visual3d:documentation:definitions:model_builder_mode|Model Builder Mode]].
  
-Muscles are created and edited from the **Muscle Tab** in Model Builder Mode.+{{:MuscleTab.gif}}
  
-{{:MuscleTab.gif}}\\+==== Muscle Definition ====
  
 +Muscles are defined as a connect series of linear segments, passing from Landmark to Landmark. The user can add or delete the landmarks in the list box. Note that the order of the landmarks is important regarding how they are interpreted:
 +  * the first landmark is always considered to be the **Origin** of the muscle;
 +  * the last landmark is always considered to be the **Insertion** of the muscle; and 
 +  * all other landmarks are considered to be **Tether (Via)** points and are connected in the order they appear in the list box.
  
-From this tab muscles can be created, edited, and deleted.+{{:MuscleDefinition.gif}}
  
-=== Muscle Definition ===+==== Terry Database ====
  
-Muscles are defined as a connect series of linear segments, passing from Landmark to Landmark.+The Terry Database comes from an article by Kepple et al. in 1998. The original dataset can be downloaded [[https://www.has-motion.com/download/Terry_Data.zip|here]].
  
-{{:MuscleDefinition.gif}}\\+The landmarks are stored in ASCII files. The structure of the dataset is described in the files. An excerpt from the femur landmarks is presented here: 
 +  * Description of landmarks digitized on the femur 
 +  * Each landmark is listed in the same order as they appear in the corresponding model files. The model file format is: 
 +    * (landmark #) x y z (# of specimens used to generate norm landmark) 
 +    * x is approximately anterior, y is superior, and z is right 
 +    * units are mm
  
- 
-The user can add or delete the landmarks in the list box. The first landmark is always considered to be the **Origin** of the muscle, and the last landmark is always considered to be the **Insertion** of the muscle. All other landmarks are considered to be **Tether (Via)** points and are connected in the order they appear in the list box. 
- 
-===== Terry Database ===== 
- 
-**Kepple TM, Sommer HJ, Siegel KL, Standhope SJ** (1998) A three-dimensional musculoskeletal database for the lower extremities. Journal of Biomechanics 31, pp 77-80 
- 
-The locations of idealized muscle attachments on the pelvis, both femurs, both tibias and fibulas, and both feet were accurately digitized for 52 dried skeletal specimens....Statistical accumulation and scaling techniques were used to generate highly representative normative models, which were divided into groups and tested for differences based on gender and race....Containing over **12000 anatomical landmarks** digitized from 52 dried skeletons, this study represents an improvement over previous databases by an order of magnitude 
- 
-Note that the limitation of the data set is that because the data collection was from bones, there is little information on muscle path. For example, it was not possible to identify tether (or via) points related to, for example, attachments to the patella. Careful estimation of these via points is possible, but it is difficult to verify the accuracy of these estimates. This challenge is most serious for the estimate of the moment arms around some joints, and for the estimate of length of muscles that are short relative to the actual path. 
- 
-If the purpose the muscle representation is visualization (e.g. mapping EMG to the color of the rendered muscles) these issues are not relevant. 
- 
-\\ 
- 
- 
-The original data set can be downloaded [[https://www.has-motion.com/download/Terry_Data.zip|Here]]. 
- 
-The landmarks are stored in ASCII files. The structure of the data set is described in the files. An excerpt from the femur landmarks is presented here: 
- 
-Description of landmarks digitized on the femur 
-Each landmark is listed in the same order as they appear in the corresponding model files. The model file format is: 
-(landmark #) x y z (# of specimens used to generate norm landmark) 
-x is approximately anterior, y is superior, and z is right 
-units are mm 
 This file contains for each landmark: This file contains for each landmark:
   - landmark number followed by a description of where the landmark is located.   - landmark number followed by a description of where the landmark is located.
Line 50: Line 34:
 === Affine Scaling of a Terry Landmark === === Affine Scaling of a Terry Landmark ===
  
-Sommer H, Miller N, Pihanowske G (1982) Three-dimensional osteometric scaling and normative modeling of skeltal segments. Journal of Biomechanics 15, pp 171-180.+The linear algebra technique described in Sommer, Miller, and Pihanowske (1982), **termed affine scaling**, scales the data based on all measured landmarks and allows for the statistical accumulation of landmark data in order to generate normative models.
  
-The linear algebra technique described in this article, **termed affine scaling**, scales the data based on all measured landmarks and allows for the statistical accumulation of landmark data in order to generate normative models. +Each landmark is defined relative to 3 or 4 landmarks that were selected to be palpable on living subjects. For example, the thigh landmarks are defined relative to the greater trochanter, the lateral epicondyle, and the medial epicondyle.
- +
-Each landmark is defined relative to 3 or 4 landmarks that were selected to be palpable on living subjects (For example, the thigh landmarks are defined relative to the greater trochanter, the lateral epicondyle, and the medial epicondyle).+
  
 === Visual3D Representation of a Terry Landmark === === Visual3D Representation of a Terry Landmark ===
Line 60: Line 42:
 The following Visual3D command is used to define a landmark representing the **Origin of the Right Medial Gastrocnemius Muscle** based on **Affine Scaling** The following Visual3D command is used to define a landmark representing the **Origin of the Right Medial Gastrocnemius Muscle** based on **Affine Scaling**
  
-**Add_Landmark_Using_Affine_Scaling** +<code> 
-///VISUAL3D_LANDMARK_NAME=ORIGIN_RT_GASTROC_MED// +Add_Landmark_Using_Affine_Scaling 
-////+/VISUAL3D_LANDMARK_NAME=ORIGIN_RT_GASTROC_MED 
 /CALIBRATION_FILE=*model.mdh /CALIBRATION_FILE=*model.mdh
 /LINKMODEL_MARKER_NAMES=RGT+RLK+RMK /LINKMODEL_MARKER_NAMES=RGT+RLK+RMK
Line 73: Line 56:
 /SCALE_ML=FALSE /SCALE_ML=FALSE
 /SCALE_AXIAL=TRUE /SCALE_AXIAL=TRUE
-//;// +; 
-Note that the mocap markers/landmarks for the three homologous anatomical points must exist in the model file. +</code>
- +
-LGT= Left Greater Trochanter\\+
  
-LLK= Left Lateral Knee (epicondyle)\\+Note that the motion capture cap markers and/or landmarks for the three homologous anatomical points must exist in the model file.
  
 +<code>
 +LGT= Left Greater Trochanter
 +LLK= Left Lateral Knee (epicondyle)
 LMK= Left Lateral Knee (epicondyle) LMK= Left Lateral Knee (epicondyle)
 +</code>
 +
 In the above example, the Terry information for the thigh segments (femur.txt) required are the following: In the above example, the Terry information for the thigh segments (femur.txt) required are the following:
 +  - most lateral point on greater trochanter
 +    - type:palpable landmark
 +    - muscle:
 +  - most lateral point on lateral epicondyle
 +    - type:palpable landmark
 +    - muscle:
 +  - most medial point on medial epicondyle
 +    - type:palpable landmark
 +    - muscle:
 +  - most superior point on medial condyle
 +    - type: muscle origin
 +    - muscle: origin of Gastrocnemius medial head
  
-1) most lateral point on greater trochanter 
-type:palpable landmark 
-muscle: 
-2) most lateral point on lateral epicondyle 
-type: palpable landmark 
-muscle: 
-3) most medial point on medial epicondyle 
-type: palpable landmark 
-muscle: 
-30) most superior point on medial condyle 
-type: muscle origin 
-muscle: origin of Gastrocnemius medial head 
 The numerical values associated with these locations for a **White Male** are stored in the file femur.mod The numerical values associated with these locations for a **White Male** are stored in the file femur.mod
  
Line 105: Line 91:
 |30   |-26.117|-381.432|-24.205|104.000| |30   |-26.117|-381.432|-24.205|104.000|
  
-=== Example Data Set with Meta Commands and Pipeline ===+==== References ====
  
-This is an [[https://www.has-motion.com/download/examples/TerryDemoBlank.cmo|example data]] set compatible with the Terry Database.+1. **Kepple TM, Sommer HJ, Siegel KL, Standhope SJ** (1998) A three-dimensional musculoskeletal database for the lower extremities. Journal of Biomechanics 31, pp 77-80 [[https://doi.org/10.1016/S0021-9290(97)00107-3|DOI]]
  
-Download the [[https://www.has-motion.com/download/examples/TerryMetaCommands.zip|Meta-Commands]] and place them in a folder labeled Meta-Commands inside the Visual3D plugins folder+The locations of idealized muscle attachments on the pelvis, both femurs, both tibias and fibulas, and both feet were accurately digitized for 52 dried skeletal specimens....Statistical accumulation and scaling techniques were used to generate highly representative normative models, which were divided into groups and tested for differences based on gender and race....Containing over **12000 anatomical landmarks** digitized from 52 dried skeletons, this study represents an improvement over previous databases by an order of magnitude
  
-Download the example [[https://www.has-motion.com/download/examples/TerryExamplePipeline.v3s|Visual3D pipeline]]. Note to download this file, right mouse click on the link and save the link to your computer.+Note that the limitation of the data set is that because the data collection was from bones, there is little information on muscle path. For example, it was not possible to identify tether (or via) points related to, for example, attachments to the patella. Careful estimation of these via points is possible, but it is difficult to verify the accuracy of these estimates. This challenge is most serious for the estimate of the moment arms around some joints, and for the estimate of length of muscles that are short relative to the actual path.
  
-Load the cmo file into Visual3D+If the purpose the muscle representation is visualization (e.g. mapping EMG to the color of the rendered muscles) these issues are not relevant.
  
-Execute the pipeline to create Visual3D representations of a collection of the Terry Database muscle.+2. **Sommer H, Miller N, Pihanowske G** (1982) Three-dimensional osteometric scaling and normative modelling of skeletal segments. Journal of Biomechanics 15, pp 171-180. [[https://doi.org/10.1016/0021-9290(82)90249-4|DOI]] 
 + 
 +Many analytical biomechanics methods require extensive three-dimensional descriptions of anatomical geometry. In particular, researchers requiring the three-dimensional coordinates of specific boney landmarks (e.g. tendon and ligament attachments) are often forced to extrapolate such measurements from an experimental specimen set to their subject geometry. 
 + 
 +This work offers an approach to two problems inherent above; accurate extrapolation of specimen landmark locations to subject homologues and statistical accumulation of normative three-dimensional anatomical landmark data bases. A least squares solution for an affine scaling transformation from specimen to subject is used which incorporates both right-left and same hand comparisons. A two stage technique is formulated to consecutively remove landmark location variation and to size a normative specimen from a set of similar specimens. This ability to statistically represent a specimen set will provide better geometric models for other analytical studies and prosthetic design and evaluation. 
 + 
 +===== Example Data Set with Meta Commands and Pipeline ===== 
 + 
 +This is example demonstrates how to use a dataset compatible with the Terry Database within Visual3D. 
 + 
 +==== Prepare ==== 
 +  - Download the [[https://www.has-motion.com/download/examples/TerryDemoBlank.cmo|example dataset]]. 
 +  - Download the [[https://www.has-motion.com/download/examples/TerryMetaCommands.zip|Meta-Commands]] and place them in a folder labelled [[visual3d:documentation:pipeline:meta_commands:meta_commands_overview|Meta-Commands]] inside the Visual3D plugins folder 
 +  - Download the example [[https://www.has-motion.com/download/examples/TerryExamplePipeline.v3s|Visual3D pipeline]]. Note to download this file, right mouse click on the link and save the link to your computer. 
 + 
 +==== Steps ==== 
 +  - Load the cmo file into Visual3D 
 +  - Execute the pipeline to create Visual3D representations of a collection of the Terry Database muscle.
  
 **Note that the first command of this example pipeline specifies the FOLDER containing the data. You will need to recreate this folder path or specify the path on your computer.** **Note that the first command of this example pipeline specifies the FOLDER containing the data. You will need to recreate this folder path or specify the path on your computer.**
  
-=== Visual3D Meta-Command for a Terry Muscle ===+==== Visual3D Meta-Command for a Terry Muscle ====
  
 As an example, the Gastrocnemius muscle can be defined using the following Meta-Command As an example, the Gastrocnemius muscle can be defined using the following Meta-Command
  
-! BEGIN_META\\ +<code> 
-! META_CMD_NAME=Terry_Rt_Plantar_Flexors_Group\\ +! BEGIN_META 
-! META_PARAM= MODEL_NAME : string ::yes\\ +! META_CMD_NAME=Terry_Rt_Plantar_Flexors_Group 
-! META_PARAM= RIGHT_THIGH_MARKERS : string ::yes\\ +! META_PARAM= MODEL_NAME : string ::yes 
-! META_PARAM= RIGHT_SHANK_MARKERS: string ::yes\\ +! META_PARAM= RIGHT_THIGH_MARKERS : string ::yes 
-! META_PARAM= RIGHT_FOOT_MARKERS: string ::yes\\+! META_PARAM= RIGHT_SHANK_MARKERS: string ::yes 
 +! META_PARAM= RIGHT_FOOT_MARKERS: string ::yes
 ! END_META ! END_META
  
-\\ +! -------------------------------------------------------------
-! -------------------------------------------------------------\\+
 ! Gastrocnemius\\ ! Gastrocnemius\\
-! -------------------------------------------------------------\\ +! ------------------------------------------------------------- 
-**Add_Landmark_Using_Affine_Scaling**\\ +Add_Landmark_Using_Affine_Scaling 
-/VISUAL3D_LANDMARK_NAME=ORIGIN_RT_GASTROC_MED\\ +/VISUAL3D_LANDMARK_NAME=ORIGIN_RT_GASTROC_MED 
-/CALIBRATION_FILE=::MODEL_NAME\\ +/CALIBRATION_FILE=::MODEL_NAME 
-/LINKMODEL_MARKER_NAMES=::RIGHT_THIGH_MARKERS\\ +/LINKMODEL_MARKER_NAMES=::RIGHT_THIGH_MARKERS 
-/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-26.117+-381.432+-24.205\\ +/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-26.117+-381.432+-24.205 
-/SEGMENT_NAME=RTH\\ +/SEGMENT_NAME=RTH 
-/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0\\ +/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0 
-/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=0+-380.878+43.317\\ +/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=0+-380.878+43.317 
-/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=0+-394.841+-43.317\\ +/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=0+-394.841+-43.317 
-! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM=\\ +! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM= 
-/SCALE_ML=FALSE\\ +/SCALE_ML=FALSE 
-/SCALE_AXIAL=TRUE\\ +/SCALE_AXIAL=TRUE 
-;\\ +;
  
-**Add_Landmark_Using_Affine_Scaling**\\ +Add_Landmark_Using_Affine_Scaling 
-/VISUAL3D_LANDMARK_NAME=TETHER_RT_GASTROC_MED\\ +/VISUAL3D_LANDMARK_NAME=TETHER_RT_GASTROC_MED 
-/CALIBRATION_FILE=::MODEL_NAME\\ +/CALIBRATION_FILE=::MODEL_NAME 
-/LINKMODEL_MARKER_NAMES=::RIGHT_THIGH_MARKERS\\ +/LINKMODEL_MARKER_NAMES=::RIGHT_THIGH_MARKERS 
-/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-37.929+-401.247+-20.216\\ +/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-37.929+-401.247+-20.216 
-/SEGMENT_NAME=RTH\\ +/SEGMENT_NAME=RTH 
-/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0\\ +/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0 
-/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=0+-380.878+43.317\\ +/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=0+-380.878+43.317 
-/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=0+-394.841+-43.317\\ +/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=0+-394.841+-43.317 
-! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM=\\ +! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM= 
-/SCALE_ML=FALSE\\ +/SCALE_ML=FALSE 
-/SCALE_AXIAL=TRUE\\+/SCALE_AXIAL=TRUE
 ; ;
  
-**Add_Landmark_Using_Affine_Scaling**\\ +Add_Landmark_Using_Affine_Scaling 
-/VISUAL3D_LANDMARK_NAME=INSERTION_RT_GASTROC_MED\\ +/VISUAL3D_LANDMARK_NAME=INSERTION_RT_GASTROC_MED 
-/CALIBRATION_FILE=::MODEL_NAME\\ +/CALIBRATION_FILE=::MODEL_NAME 
-/LINKMODEL_MARKER_NAMES=::RIGHT_FOOT_MARKERS\\ +/LINKMODEL_MARKER_NAMES=::RIGHT_FOOT_MARKERS 
-/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-0.529+1.120+-0.726\\ +/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-0.529+1.120+-0.726 
-/SEGMENT_NAME=RFT\\ +/SEGMENT_NAME=RFT 
-/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0\\ +/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0 
-/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=85.524+0+-35.699\\ +/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=85.524+0+-35.699 
-/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=88.645+0+35.699\\ +/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=88.645+0+35.699 
-! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM=\\ +! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM= 
-/SCALE_ML=FALSE\\ +/SCALE_ML=FALSE 
-/SCALE_AXIAL=FALSE\\+/SCALE_AXIAL=FALSE
 ; ;
  
-**Add_Landmark_Based_Muscle**\\ +Add_Landmark_Based_Muscle 
-/MUSCLE_NAME=RT_GASTROC_MEDIALIS\\ +/MUSCLE_NAME=RT_GASTROC_MEDIALIS 
-/LANDMARK_ORIGIN=ORIGIN_RT_GASTROC_MED\\ +/LANDMARK_ORIGIN=ORIGIN_RT_GASTROC_MED 
-/LANDMARK_TETHERS=TETHER_RT_GASTROC_MED\\ +/LANDMARK_TETHERS=TETHER_RT_GASTROC_MED 
-/LANDMARK_INSERTION=INSERTION_RT_GASTROC_MED\\ +/LANDMARK_INSERTION=INSERTION_RT_GASTROC_MED 
-/LINK_MODEL_NAME=::MODEL_NAME\\+/LINK_MODEL_NAME=::MODEL_NAME
 ; ;
  
-**Add_Landmark_Using_Affine_Scaling**\\ +Add_Landmark_Using_Affine_Scaling 
-/VISUAL3D_LANDMARK_NAME=ORIGIN_RT_GASTROC_LAT_PLANTARIS\\ +/VISUAL3D_LANDMARK_NAME=ORIGIN_RT_GASTROC_LAT_PLANTARIS 
-/CALIBRATION_FILE=::MODEL_NAME\\ +/CALIBRATION_FILE=::MODEL_NAME 
-/LINKMODEL_MARKER_NAMES=::RIGHT_THIGH_MARKERS\\ +/LINKMODEL_MARKER_NAMES=::RIGHT_THIGH_MARKERS 
-/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-20.936+-373.101+18.664\\ +/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-20.936+-373.101+18.664 
-/SEGMENT_NAME=RTH\\ +/SEGMENT_NAME=RTH 
-/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0\\ +/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0 
-/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=0+-380.878+43.317\\ +/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=0+-380.878+43.317 
-/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=0+-394.841+-43.317\\ +/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=0+-394.841+-43.317 
-! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM=\\ +! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM= 
-/SCALE_ML=FALSE\\ +/SCALE_ML=FALSE 
-/SCALE_AXIAL=TRUE\\+/SCALE_AXIAL=TRUE
 ; ;
  
-**Add_Landmark_Using_Affine_Scaling**\\ +Add_Landmark_Using_Affine_Scaling 
-/VISUAL3D_LANDMARK_NAME=TETHER_RT_GASTROC_LAT_PLANTARIS\\ +/VISUAL3D_LANDMARK_NAME=TETHER_RT_GASTROC_LAT_PLANTARIS 
-/CALIBRATION_FILE=::MODEL_NAME\\ +/CALIBRATION_FILE=::MODEL_NAME 
-/LINKMODEL_MARKER_NAMES=::RIGHT_THIGH_MARKERS\\ +/LINKMODEL_MARKER_NAMES=::RIGHT_THIGH_MARKERS 
-/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-30.662+-390.245+23.209\\ +/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-30.662+-390.245+23.209 
-/SEGMENT_NAME=RTH\\ +/SEGMENT_NAME=RTH 
-/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0\\ +/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0 
-/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=0+-380.878+43.317\\ +/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=0+-380.878+43.317 
-/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=0+-394.841+-43.317\\ +/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=0+-394.841+-43.317 
-! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM=\\ +! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM= 
-/SCALE_ML=FALSE\\ +/SCALE_ML=FALSE 
-/SCALE_AXIAL=TRUE\\+/SCALE_AXIAL=TRUE
 ; ;
  
-**Add_Landmark_Using_Affine_Scaling**\\ +Add_Landmark_Using_Affine_Scaling 
-/VISUAL3D_LANDMARK_NAME=INSERTION_RT_GASTROC_LAT_PLANTARIS\\ +/VISUAL3D_LANDMARK_NAME=INSERTION_RT_GASTROC_LAT_PLANTARIS 
-/CALIBRATION_FILE=::MODEL_NAME\\ +/CALIBRATION_FILE=::MODEL_NAME 
-/LINKMODEL_MARKER_NAMES=::RIGHT_FOOT_MARKERS\\ +/LINKMODEL_MARKER_NAMES=::RIGHT_FOOT_MARKERS 
-/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-0.529+1.120+-0.726\\ +/LANDMARK_LOCATION_IN_LOCAL_COORDINATE_SYSTEM=-0.529+1.120+-0.726 
-/SEGMENT_NAME=RFT\\ +/SEGMENT_NAME=RFT 
-/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0\\ +/MARKER1_IN_LOCAL_COORDINATE_SYSTEM=0+0+0 
-/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=85.524+0+-35.699\\ +/MARKER2_IN_LOCAL_COORDINATE_SYSTEM=85.524+0+-35.699 
-/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=88.645+0+35.699\\ +/MARKER3_IN_LOCAL_COORDINATE_SYSTEM=88.645+0+35.699 
-! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM=\\ +! /MARKER4_IN_LOCAL_COORDINATE_SYSTEM= 
-/SCALE_ML=FALSE\\ +/SCALE_ML=FALSE 
-/SCALE_AXIAL=FALSE\\+/SCALE_AXIAL=FALSE
 ; ;
  
-**Add_Landmark_Based_Muscle**\\ +Add_Landmark_Based_Muscle 
-/MUSCLE_NAME=RT_GASTROC_LATERALIS\\ +/MUSCLE_NAME=RT_GASTROC_LATERALIS 
-/LANDMARK_ORIGIN=ORIGIN_RT_GASTROC_LAT_PLANTARIS\\ +/LANDMARK_ORIGIN=ORIGIN_RT_GASTROC_LAT_PLANTARIS 
-/LANDMARK_TETHERS=TETHER_RT_GASTROC_LAT_PLANTARIS\\ +/LANDMARK_TETHERS=TETHER_RT_GASTROC_LAT_PLANTARIS 
-/LANDMARK_INSERTION=INSERTION_RT_GASTROC_LAT_PLANTARIS\\+/LANDMARK_INSERTION=INSERTION_RT_GASTROC_LAT_PLANTARIS
 /LINK_MODEL_NAME=::MODEL_NAME\\ /LINK_MODEL_NAME=::MODEL_NAME\\
 ; ;
 +</code>
  
 === Pipeline Command for Above Meta-Command === === Pipeline Command for Above Meta-Command ===
  
-A meta-command is a Visual3D pipeline into which **Parameters can be passed** +A meta-command is a Visual3D pipeline into which **parameters can be passed**. The [[visual3d:documentation:pipeline:meta_commands:meta_commands_overview|meta-command]] should be stored in a folder labeled **Meta-Commands**, which is located in the Visual3D **Plugins** Folder.
- +
-The meta-command should be stored in a folder labeled **Meta-Commands**, which is located in the Visual3D **Plugins** Folder.+
  
 The header in the meta-command defines the data that should be passed: The header in the meta-command defines the data that should be passed:
  
 +<code>
 ! BEGIN_META ! BEGIN_META
 ! META_CMD_NAME=Terry_Rt_Plantar_Flexors_Group ! META_CMD_NAME=Terry_Rt_Plantar_Flexors_Group
Line 251: Line 253:
 ! META_PARAM= RIGHT_FOOT_MARKERS: string ::yes ! META_PARAM= RIGHT_FOOT_MARKERS: string ::yes
 ! END_META ! END_META
 +</code>
 +
 This command will appear in the Visual3D Pipeline Dialog list box in a folder labeled **Meta_Commands.** The command will be similar to the following: This command will appear in the Visual3D Pipeline Dialog list box in a folder labeled **Meta_Commands.** The command will be similar to the following:
  
-**Terry_Rt_Plantar_Flexors_Group**+<code> 
 +Terry_Rt_Plantar_Flexors_Group
 /MODEL_NAME= *model.mdh /MODEL_NAME= *model.mdh
 /RIGHT_THIGH_MARKERS= RGT+RLK+RMK /RIGHT_THIGH_MARKERS= RGT+RLK+RMK
Line 259: Line 264:
 /RIGHT_FOOT_MARKERS= RHL+RFT2+RFT1 /RIGHT_FOOT_MARKERS= RHL+RFT2+RFT1
 ; ;
- +</code>
visual3d/documentation/modeling/muscles/muscles_overview.1721231128.txt.gz · Last modified: 2024/07/17 15:45 by sgranger