HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » pipeline » model_based_data_commands » COP Path
visual3d:documentation:pipeline:model_based_data_commands:cop_path

Differences

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

Link to this comparison view

Next revision		Previous revision
visual3d:documentation:pipeline:model_based_data_commands:cop_path [2024/06/14 17:28] – created sgrangervisual3d:documentation:pipeline:model_based_data_commands:cop_path [2024/11/05 16:06] (current) – Clean up page and brought it in line with the Model-Based Item template. wikisysop
Line 1: Line 1:
-|**Language:**|** English**  • [[index.php?title=COP_Path/fr&action=edit&redlink=1|français]] • [[index.php?title=COP_Path/it&action=edit&redlink=1|italiano]] • [[COP_Path/pt|português]] • [[index.php?title=COP_Path/es&action=edit&redlink=1|español]] ****|+===== COP Path =====
  
-|===== Contents =====\\ \\ \\ \\ * [[#Model_Based_Item|1 Model Based Item]]\\ * [[#Pipeline_Command|2 Pipeline Command]]\\ * [[#Resolution_Coordinate_System|3 Resolution Coordinate System]]\\ * [[#Sign_Convention|4 Sign Convention]]\\ * [[#Normalization|5 Normalization]]\\ * [[#Example:_a_foot_segment_parallel_to_the_floor|6 Example: a foot segment parallel to the floor]]|+Creating a [[visual3d:documentation:visual3d_signal_types:link_model_based_data_type|LINK_MODEL_BASED]] signal called the COP_PATH is a general way to compute the center of pressure. This command checks all [[Visual3D:Documentation:Kinematics_and_Kinetics:External_Forces:Force_Assignment|force assignments to the specified segment]] and all force platforms, then resolves the resulting signal into the specified local coordinate system.
  
-Creating a LINK_MODEL_BASED signal called the COP_PATH is a more general way to compute the center of pressure. The command checks all [[Visual3D:Documentation:Kinematics_and_Kinetics:External_Forces:Force_Assignment|force assignments to the specified segment]] and any force platform. The signal is then transformed (or resolved) into the specified local coordinate system). All occurrences (eg. all force platforms) are included to determine if the segment has been assigned to the force signal.+For example, to calculate the center of pressure path for the left foot with respect to the left virtual foot, choose LFT as your segment and Left Virtual Foot as your resolution coordinate system:
  
-By default, normalization is by segment width and length.+{{:ModelBasedCop_Path.png}}
  
-===== Model Based Item =====+==== Normalization ====
  
-[[File:ModelBasedCop_Path.png|{{/images/d/de/ModelBasedCop_Path.png?594x322}}]] +Four options exist to normalize the computed value for the joint moment.
-===== Pipeline Command =====+
  
-**Compute_Model_Based_Data** +  - Normalization Off: The computed value is not normalized. 
-/RESULT_NAME=RT_COP +  - Normalize using default normalization: The computed value is normalized according to the segment width and length. 
-/FUNCTION=COP_PATH +  - Normalize to local file metric value: The user specifies the METRIC value in the local file with which to normalize the computed value. 
-/SEGMENT=RFT +  - Normalize to global metric value: The user specifies the METRIC value in the GLOBAL workspace with which to normalize the computed value.
-/REFERENCE_SEGMENT= +
-/RESOLUTION_COORDINATE_SYSTEM=RFT +
-/USE_CARDAN_SEQUENCE=FALSE +
-/NORMALIZATION=TRUE +
-/NORMALIZATION_METHOD=DEFAULT_NORMALIZATION +
-/NORMALIZATION_METRIC= +
-! /NEGATEX=FALSE +
-! /NEGATEY=FALSE +
-! /NEGATEZ=FALSE +
-! /AXIS1=X +
-/AXIS2=Y +
-! /AXIS3=Z +
-**;** +
-===== Resolution Coordinate System =====+
  
-The coordinate system used by the model based items is precisely the coordinate system you see in the animation viewer. The length of the segment is defined from the proximal end to the distal end of the segment regardless of what axis you call this, and the proximal and distal radius are defined by the segment definition.+Note that the default normalization is relative to length (distance between proximal and distal ends of the segment) and width (distal radius) of the segment that is assigned to the force vector. If the foot segment defined from the ankle to the metatarsals is assigned to the force, then the range of motion might be on the order -1 to 2 in the axial direction, which may seem strange for a normalized value. In this case a negative axial value means the COP is behind the ankle and a positive axial value means the COP is in front of the ankle joint center. An axial value greater than 1 would mean that the COP was more distal than the metatarsals (e.g. under the toes)
  
-===== Sign Convention =====+==== The Right-Hand Rule ====
  
-As mentioned in the previous answer you can't really set up Abd and ExtRot so they have the same sign on both sides because Visual3D strictly follows the right hand rule. (This is done by design because some Visual3D users analyse things other than people/animals and thus the terms flexion/extension, ab/aduction and axial rotation have no meaning to them. Thus we simply always following the right hand rule to supply consistency for all users.)+It is not quite possible to set up model-based items so that their components have the same sign on both sides of the body because Visual3D strictly follows the right hand rule. This is done by design because some Visual3D users analyse things other than people/animals where the terms flexion/extension, ab/aduction and axial rotation have no specific meaning.
  
-In order to get the signs of the COP_PATH to be consistent between the left and right leg (e.g. how to get around the fact that Visual3D enforces the right hand rule), you can select the check boxes in the dialog to negate one or more components.+In order to get the signs of the COP_PATH to be consistent between the left and right leg, i.e., to get around the fact that Visual3D enforces the right-hand rule, you can select the check boxes in the dialog to negate one or more components. This process is described in [[Visual3D:Tutorials:Kinematics_and_Kinetics:Model_Based_Computations#Understanding_the_Knee_Angle_Signal|the tutorial explaining Knee Angle Signals]].
  
-This is described in this tutorial:+==== Example: a foot segment parallel to the floor ====
  
-[[Visual3D:Tutorials:Kinematics_Kinetics:Model_Based_Computations#Understanding_the_Knee_Angle_Signal|Tutorial:_Model_Based_Computations#Understanding_the_Knee_Angle_Signal]] +Commonly the center of pressure is computed relative to a "special" foot coordinate system. A virtual foot is created that lies flat on the floor during the standing trial. The center of pressure is often scaled to the length and width of the foot segment. The following process can be used to create this signal:
-===== Normalization =====+
  
-The standard normalization is relative to length (distance between proximal and distal ends of the segment) and width (distal radius) of the segment that is assigned to the force vector.+Given a Left Foot gegment defined as:
  
-If the foot segment is assigned to the force, and the foot segment is defined from the ankle to the metatarsals, that range of motion might be on the order -1 to 2 in the axial direction, which may seem strange for a normalized value.+<code> 
 +Segment Name= Left Foot
  
-A negative axial value means the COP is behind the ankle and a positive axial value means the COP is in front of the ankle joint center. 
- 
-An axial value greater than 1 would mean that the COP was more distal than the metatarsals (e.g. under the toes) 
- 
-===== Example: a foot segment parallel to the floor ===== 
- 
-Commonly the center of pressure is computed relative to a ”r;special” foot coordinate system. A virtual foot is created that lies flat on the floor during the standing trial. The center of pressure is often scaled to the length and width of the foot segment. The following process can be used to create this signal: 
- 
-Given a Left Foot Segment defined as: 
- 
-Segment Name= Left Foot 
 Define Proximal Joint and Radius Define Proximal Joint and Radius
 Lateral= LLA Joint= none Medial= LMA Lateral= LLA Joint= none Medial= LMA
 +
 Define Distal Joint and Radius Define Distal Joint and Radius
 Lateral= LMET5 Joint= none Medial= LMET1 Lateral= LMET5 Joint= none Medial= LMET1
 +
 Extra Target To Define Orientation (if needed) Extra Target To Define Orientation (if needed)
 Location Lateral= none Location Lateral= none
-Select Tracking Markers +Select Tracking Markers: LFT1 LFT2 LFT3 
-LFT1 LFT2 LFT3 +</code> 
-\\ + 
-'**Create Landmarks** by projecting the anatomical markers used to define the foot onto the floor of the laboratory.+Create [[visual3d:documentation:modeling:landmarks:landmarks_overview|landmarks]] by projecting the anatomical markers used to define the foot onto the floor of the laboratory.
  
 +<code>
 Landmark Name= LLA_FLOOR Landmark Name= LLA_FLOOR
 Define Orientation Using Define Orientation Using
Line 77: Line 54:
 X= LLA::X Y= LLA::Y Z= 0 X= LLA::X Y= LLA::Y Z= 0
 Calibration Only Landmark= Checked Calibration Only Landmark= Checked
 +
 Landmark Name= LMA_FLOOR Landmark Name= LMA_FLOOR
 Define Orientation Using Define Orientation Using
Line 84: Line 62:
 X= LMA::X Y= LMA::Y Z= 0 X= LMA::X Y= LMA::Y Z= 0
 Calibration Only Landmark= Checked Calibration Only Landmark= Checked
-\\ 
- 
  
 Landmark Name= LMET5_FLOOR Landmark Name= LMET5_FLOOR
Line 94: Line 70:
 X= LMET5::X Y= LMET5::Y Z= 0 X= LMET5::X Y= LMET5::Y Z= 0
 Calibration Only Landmark= Checked Calibration Only Landmark= Checked
-\\ 
- 
  
 Landmark Name= LMET1_FLOOR Landmark Name= LMET1_FLOOR
Line 104: Line 78:
 X= LMET1::X Y= LMET1::Y Z= 0 X= LMET1::X Y= LMET1::Y Z= 0
 Calibration Only Landmark= Checked Calibration Only Landmark= Checked
-\\+</code>
  
  
-**Virtual Foot Segment**+Define the virtual foot segment as follows:
  
 +<code>
 Segment Name= Left Virtual Foot Segment Name= Left Virtual Foot
 +
 Define Proximal Joint and Radius Define Proximal Joint and Radius
 Lateral= LLA_FLOOR Joint= none Medial= LMA_FLOOR Lateral= LLA_FLOOR Joint= none Medial= LMA_FLOOR
 +
 Define Distal Joint and Radius Define Distal Joint and Radius
 Lateral= LMET5_FLOOR Joint= none Medial= LMET1_FLOOR Lateral= LMET5_FLOOR Joint= none Medial= LMET1_FLOOR
 +
 Extra Target To Define Orientation (if needed) Extra Target To Define Orientation (if needed)
-Location Lateral =none +Location Lateral= none 
-Select Tracking Markers +Select Tracking Markers: LFT1 LFT2 LFT3 
-LFT1 LFT2 LFT3 +</code>
-\\ +
- +
- +
-Create the Center of Pressure signal as shown in the dialog above. +
- +
-Assuming the left foot segment has been assigned to a force platform. The segment is specified as the LFT. Visual3D interprets this as finding the contacts of the LFT segment on any of the force platforms. The resolution coordinate system is defined as the ”r;Left Virtual Foot” segment coordinate system, which is flat on the ground during standing posture. Normalization scales the COP_PATH signal to the length and width of the foot. This signal will appear in the data tree in the LINK_MODEL_BASED folder, and is available for graphing in the report. +
- +
- +
-Retrieved from "" +
  
 +Create the Center of Pressure signal as shown in the dialog above. Assuming the left foot segment has been assigned to a force platform and that the segment is specified as the LF,. Visual3D interprets this as finding the contacts of the LFT segment on any of the force platforms. The resolution coordinate system is defined as the "Left Virtual Foot" segment coordinate system, which is flat on the ground during standing posture. Normalization scales the COP_PATH signal to the length and width of the foot. This signal will appear in the data tree in the LINK_MODEL_BASED folder, and is available for graphing in the report.
visual3d/documentation/pipeline/model_based_data_commands/cop_path.1718386087.txt.gz · Last modified: 2024/06/14 17:28 by sgranger