Differences

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

--- visual3d:documentation:kinematics_and_kinetics:external_forces:force_overview [2024/07/12 13:28] – removed sgranger
+++ visual3d:documentation:kinematics_and_kinetics:external_forces:force_overview [2025/02/21 18:10] (current) – wikisysop
@@ Line 1: / Line 1: @@
+===== Force Overview =====
+This page provides a useful jumping off point to learn about how [[visual3d:documentation:kinematics_and_kinetics:external_forces:force_representation||external forces are represented]] within Visual3D and how these
+forces are included in the [[Visual3D:Documentation:Kinematics_and_Kinetics:Inverse_Dynamics|inverse dynamics]] calculations.
+If you are searching for the computation of forces and moments, see the section on [[Visual3D:Documentation:Kinematics_and_Kinetics:Inverse_Dynamics|Inverse Dynamics]].
+==== Force Platforms ====
+The traditional method for measuring external force for [[Visual3D:Documentation:Kinematics_and_Kinetics:Inverse_Dynamics|inverse dynamics]] of gait analysis is a [[visual3d:tutorials:kinematics_and_kinetics:force_platforms|force platform]]. In recent years, force sensors have been incorporated into a variety of structures, such as Steps and Treadmills. Visual3D treats these forces as [[Visual3D:Documentation:Kinematics_and_Kinetics:External_Forces:Force_Structures|force structures]], which are really structures attached to force platforms or to contiguous force platforms spaced in a grid.
+There are additional considerations for modelling [[visual3d:tutorials:kinematics_and_kinetics:instrumented_treadmills|instrumented treadmills]] and [[visual3d:documentation:kinematics_and_kinetics:external_forces:dynamic_force_platforms|dynamic force platforms]] with Visual3D. This is a result of the C3D file format being set up to handle static force platforms only, but both of these sensors can be modelled.
+A PDF slide package for a [[https://www.has-motion.com/download/examples/Introduction_to_Force_Platforms2.pdf|lecture on force platforms]] is available for download.
+==== Force Assignment ====
+In order to include a force in the [[Visual3D:Documentation:Kinematics_and_Kinetics:Inverse_Dynamics|inverse dynamics]] calculations it is necessary to [[visual3d:documentation:kinematics_and_kinetics:external_forces:force_assignment | assign the force to a segment]]. In many cases, force platforms or force structures, Visual3D attempts to [[visual3d:documentation:kinematics_and_kinetics:external_forces:force_assignment|assign the forces automatically]]. Forces can also be defined by the user, and assigned to a segment. Whether forces are assigned automatically or manually, it is important to verify that these assignments are correct. Incorrect force assignments will inevitably propagate into your subsequent analysis leading to, for example, [[visual3d:tutorials:kinematics_and_kinetics:bad_force_assignments_causing_bad_gait_events|bad gait events]].
+As of Visual3D version 4, a colour scheme is used for animating forces to indicate whether or not the force is assigned:
+  - A red arrow is an unassigned force from a Force Platform.
+  - A blue arrow is a Force Assignment (not necessarily related to a force platform) to a segment.
+  - A yellow arrow is a force on a Force Structures (e.g. a step).
+=== Model-based Items ===
+There are two [[visual3d:documentation:visual3d_signal_types:link_model_based_data_type|model-based items]] of interest for assigned forces:
+  - [[Visual3D:Documentation:Pipeline:Model_Based_Data_Commands:GRF_DATA|GRF_DATA]]
+  - [[Visual3D:Documentation:Pipeline:Model_Based_Data_Commands:COP_Path|COP Path]]
+==== Using Processed Forces for Segment to Force Assignments ===
+Visual3D includes options to [[visual3d:documentation:visual3d_signal_types:link_model_based_data_type#using_processed_signals|use processed analog, target, and force signals]] for subsequent analysis. In most situations, you want “Use Processed Analogs” and “Use Processed Targets” set to TRUE and Use “Processed Forces” set to FALSE. A discussion about why we recommend filtering analog signals over force signals can be found [[https://has-motion.com/wiki/doku.php?id=visual3d:documentation:visual3d_signal_types:used_process#why_filter_the_analog_vs_force_data|on this wiki]] as well as in this fascinating conversation on [[https://biomch-l.isbweb.org/forum/biomch-l-forums/general-discussion/33371-filtering-issue-of-grf-data|biomch-l]].
+==== CalTester Mode ====
+Visual3D's [[caltester:caltester_mode_overview|CalTester Mode]] allows users to properly calibrate their lab in terms of the positions of the force platform(s) and cameras in the laboratory coordinate system. Any errors in the parameter settings or calibration measurements will lead to incorrect values of kinetic calculations that rely on the force data. This is important to understand as accurate and reliable kinematics and kinetics data are essential to the appropriate analysis of movement data.
+Using a computational method based on static equilibrium, it is possible to independently measure the rod's orientation and tip position during the movement trial, using force platform derived data exclusively, and to compare these estimates to rod orientation and tip position estimates derived exclusively from the motion capture component. The degree of spatial and temporal agreement between these two sets of data provides an assessment of the joint working status of the kinetic and kinematic systems. A small number of variable are calculated and presented for inspection&emdash;these enable the user to detect the presence of errors from a large number of potential sources.