Documentation Site Map Main Page Reference List Motion Capture Visual3D Overview Visual3D Installation License Activation Getting Started Visual3D Documentation Overview Pipeline Commands Reference Expressions Overview CalTester Mode Overview List of Tutorials Visual3D Examples Overview Troubleshooting Sift Sift Overview Installation Getting Started Sift Documentation Overview Knowledge Discovery for Biomechanical Data Tutorial Overview Troubleshooting Inspect3D Inspect3D Overview Inspect3D Installation Overview Inspect3D Getting Started Overview Inspect3D Documentation Overview Knowledge Discovery in Inspect3D Inspect3D Tutorials Overview Troubleshooting DSX Suite DSX Overview DSX Definitions DSX Suite Installation DSX Tutorials DSX Release Notes xManager Overview PlanDSX Overview Surface3D Overview Orient3D Overview CalibrateDSX Overview Locate3D Overview X4D Overview
This is an old revision of the document!
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. by default, normalization is by segment length. ===== model based item ===== cop_model_cog_dlg.jpg ===== pipeline command ===== **compute_model_based_data** /result_name=lcop_cog /function=cop_model_cog /segment=lto /reference_segment= /resolution_coordinate_system=vlb /use_cardan_sequence=false /normalization=false /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. ===== sign convention ===== in order to get the signs of the cop_model_cog 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. ===== normalization ===== the default normalization is relative to length (distance between proximal and distal ends of the segment) of the segment that is assigned to the force vector. a negative axial value means the cop is behind the cog and a positive axial value means the cop is in front of the cog.