Differences

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

--- visual3d:documentation:kinematics_and_kinetics:external_forces:forces_faq [2024/06/19 12:48] – sgranger
+++ visual3d:documentation:kinematics_and_kinetics:external_forces:forces_faq [2024/07/17 15:45] (current) – created sgranger
@@ Line 1: / Line 1: @@
-===== faqs =====
+====== Forces FAQ ======
-**question**: i’m doing **inverse dynamic analyses** but in some trials my participant has **two feet on one force platform** at the same time, and in others **one of their feet is simultaneously in contact with two different force platforms**. what should i do?\\
+==== FAQs ====
+**Question**: I’m doing **inverse dynamic analyses** but in some trials my participant has **two feet on one force platform** at the same time, and in others **one of their feet is simultaneously in contact with two different force platforms**. What should I do?\\
-**answer** (click to expand)
-if two feet are on the same force platform at the same time, visual3d has no way of parsing the force data into two separate parts, one for each foot. this means that inverse dynamic calculations are invalid and shouldn’t be carried out. conversely, one foot contacting two platforms isn’t a problem. visual3d automatically ‘assigns’ segments to forces based on the distance of the cofp from the segments in the model. put simply, the nearest segment to the cofp is assigned to the force. there is a threshold value that the separation distance must be within (0.2m), and we don’t advise altering this without good reason. this assignment means that inverse dynamics are still calculated when a foot ‘straddles’ two platforms. also, most people aren’t aware that automatic_gait_events are based on force assignments, so bad or absent assignments can create issues with these. we advise that force assignment should always be checked carefully. see [[http://c-motion.com/v3dwiki/index.php?title=force_assignment|force assignments]]
+**Answer** (click to expand)
+If two feet are on the same force platform at the same time, Visual3D has no way of parsing the FORCE data into two separate parts, one for each foot. This means that inverse dynamic calculations are invalid and shouldn’t be carried out. Conversely, one foot contacting two platforms isn’t a problem. Visual3D automatically ‘assigns’ segments to forces based on the distance of the COFP from the segments in the model. Put simply, the nearest segment to the COFP is assigned to the force. There is a threshold value that the separation distance must be within (0.2m), and we don’t advise altering this without good reason. This assignment means that inverse dynamics are still calculated when a foot ‘straddles’ two platforms. Also, most people aren’t aware that Automatic_Gait_Events are based on force assignments, so bad or absent assignments can create issues with these. We advise that force assignment should always be checked carefully. See [[http://c-motion.com/v3dwiki/index.php?title=Force_Assignment|Force Assignments]]
@@ Line 12: / Line 14: @@
-**question**: when i look at **“data values”** in a force signal, within the signals and events tree, what are the **x sub, y sub and z sub** values?\\
+**Question**: When I look at **“Data Values”** in a FORCE signal, within the Signals and Events tree, what are the **X SUB, Y SUB and Z SUB** values?\\
-**answer** (click to expand)
+**Answer** (click to expand)
 \\
-many people collect analog data at a higher rate than their motion capture data, which is the point rate. this is fine, as long as the higher rate is an integer multiple of the point rate. when force data are applied to a model, the resulting link_model_based data are at point rate. this is because forces applied to segments cannot be calculated where the segment location is unknown (between point frames), i.e. there are no target data to generate segment locations for the ‘extra’ analog frames. however, the force data retain the analog data rate. these ‘extra’ sample points are displayed as sub frames within the point rate. other link_model_based data, which are based on segments, are also sampled at the point rate, since segmental data can only ever be calculated at point rate.
+Many people collect analog data at a higher rate than their motion capture data, which is the point rate. This is fine, as long as the higher rate is an integer multiple of the point rate. When force data are applied to a model, the resulting Link_Model_Based data are at point rate. This is because forces applied to segments cannot be calculated where the segment location is unknown (between point frames), i.e. there are no target data to generate segment locations for the ‘extra’ analog frames. However, the FORCE data retain the analog data rate. These ‘extra’ sample points are displayed as SUB frames within the point rate. Other Link_Model_Based data, which are based on segments, are also sampled at the point rate, since segmental data can only ever be calculated at point rate.
@@ Line 24: / Line 26: @@
-**question**: how do **force assignments** work?\\
+**Question**: How do **force assignments** work?\\
-**answer** (click to expand)
+**Answer** (click to expand)
-for all segments, except ‘kinematic only’ segments, visual3d automatically calculates the distance between each segmental centre of mass and the centre(s) of pressure. in order to assign forces to segments, visual3d automatically compares the locations of segments’ centre of mass with the location of the centre of pressure. during a contact with a force platform the segment that has its centre of mass closest to the centre of pressure for the longest time is assumed to be the segment that is in contact with the force platform. put simply, the nearest segment to the centre of pressure is assigned to the force. there is a threshold value that the separation distance must be within, which usually excludes most segments within a model. this threshold value can be altered from its default setting, which is 0.2m, however we have found this default value to work best in most circumstances, therefore we don’t advise altering this without good reason. force assignment means that link model based items can be generated for left and right forces, centre of pressure position and free moments without the user imputing which foot contacted which force platform and even when a foot ‘straddles’ two platforms. automatic_gait_events are based on force assignments, so bad or absent assignments can create issues with these. we strongly advise that force assignment should always be checked carefully (especially when using instrumented treadmills) and, if incorrect, altered manually. see [[http://c-motion.com/v3dwiki/index.php?title=force_assignment|force assignments]]
+For all segments, except ‘kinematic only’ segments, Visual3D automatically calculates the distance between each segmental centre of mass and the centre(s) of pressure. In order to assign forces to segments, Visual3D automatically compares the locations of segments’ centre of mass with the location of the centre of pressure. During a contact with a force platform the segment that has its centre of mass closest to the centre of pressure for the longest time is assumed to be the segment that is in contact with the force platform. Put simply, the nearest segment to the centre of pressure is assigned to the force. There is a threshold value that the separation distance must be within, which usually excludes most segments within a model. This threshold value can be altered from its default setting, which is 0.2m, however we have found this default value to work best in most circumstances, therefore we don’t advise altering this without good reason. Force assignment means that link model based items can be generated for left and right forces, centre of pressure position and free moments without the user imputing which foot contacted which force platform and even when a foot ‘straddles’ two platforms. Automatic_Gait_Events are based on force assignments, so bad or absent assignments can create issues with these. We strongly advise that force assignment should always be checked carefully (especially when using instrumented treadmills) and, if incorrect, altered manually. See [[http://c-motion.com/v3dwiki/index.php?title=Force_Assignment|Force Assignments]]
@@ Line 35: / Line 37: @@
-**question**: what does **caltester** do?\\
+**Question**: What does **CalTester** do?\\
-**answer** (click to expand)
+**Answer** (click to expand)
-the cofp signal is created by transferring the centre of pressure calculated inside the force platform’s coordinate system into the global, laboratory coordinate system. this transfer is based on the location of the force platform’s corners and the offset between the top of the force sensors and the top of the platform’s surface. the correct position of the cofp is key to accurate inverse dynamic calculations. put simply, caltester allows you to compare the position of the cofp, which has been transformed from the force platform’s coordinate system into the global, laboratory coordinate system with how that position is represented using motion capture data. we can do this because we know where the end of the calibrated caltester rod is in space, and can compare this to the calculated position of the cofp. the two can then be ‘calibrated’ to bring them closer together by altering the force platform location parameters. in order to ensure best results it is important to follow a few simple steps. always begin the data capture with the caltester rod not in contact with the force platform, but make sure the base plate is in situ. this allows visual3d to calculate a baseline zero for all the force platform channels. once the rod is in contact with the base plate, the caltester should be the only thing that comes in contact with the force platform. ensure the rod is loaded longitudinally with a load of at least 200 n and that, during the data collection, the angle of the rod is no more than about 20 degrees. this will maximise accuracy of cofp calculation from the kinetic data and prevent the caltester rod’s tip sliding away from the bottom of the dimple in the base plate and being elevated. see [[https://www.c-motion.com/v3dwiki/index.php/caltester|caltester]]
+The COFP signal is created by transferring the centre of pressure calculated inside the force platform’s coordinate system into the global, laboratory coordinate system. This transfer is based on the location of the force platform’s corners and the offset between the top of the force sensors and the top of the platform’s surface. The correct position of the COFP is key to accurate inverse dynamic calculations. Put simply, CalTester allows you to compare the position of the COFP, which has been transformed from the force platform’s coordinate system into the global, laboratory coordinate system with how that position is represented using motion capture data. We can do this because we know where the end of the calibrated CalTester rod is in space, and can compare this to the calculated position of the COFP. The two can then be ‘calibrated’ to bring them closer together by altering the force platform location parameters. In order to ensure best results it is important to follow a few simple steps. Always Begin the data capture with the CalTester rod not in contact with the force platform, but make sure the base plate is in situ. This allows Visual3D to calculate a baseline zero for all the force platform channels. Once the rod is in contact with the base plate, the CalTester should be the only thing that comes in contact with the force platform. Ensure the rod is loaded longitudinally with a load of at least 200 N and that, during the data collection, the angle of the rod is no more than about 20 degrees. This will maximise accuracy of COFP calculation from the kinetic data and prevent the CalTester rod’s tip sliding away from the bottom of the dimple in the base plate and being elevated. See [[https://www.c-motion.com/v3dwiki/index.php/CalTester|CalTester]]