Differences

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

--- visual3d:documentation:kinematics_and_kinetics:external_forces:force_assignment_quality_assurance [2024/06/19 12:48] – sgranger
+++ visual3d:documentation:kinematics_and_kinetics:external_forces:force_assignment_quality_assurance [2025/09/12 15:26] (current) – [Command] wikisysop
@@ Line 1: / Line 1: @@
-====== background ======
+====== Force Assignment Quality Assurance ======
-force assignments are used throughout visual3d - and it's important to make sure they're correct.
+===== Background =====
-if your force assignments are correct, you know that events created using the automatic gait events command are correct, and your kinetics will be correct.
+Force Assignments are used throughout Visual3D - and it's important to make sure they're correct.
-for information about how force assignments are created, see [[visual3d:documentation:kinematics_and_kinetics:external_forces:force_assignment|here]].
+If your force assignments are correct, you know that events created using the Automatic Gait Events command are correct, and your kinetics will be correct.
-====== command ======
+For information about how force assignments are created, see [[Visual3D:Documentation:Kinematics_and_Kinetics:External_Forces:Force_Assignment|here]].
-**force_assignment_quality_assurance**
+===== Command =====
-! /min_stance_time=0.2
-! /max_stance_time=1.0
-! /min_stance_grf=0.95
-! /max_stance_grf=1.3
-! /max_cop_path_distance=4
-! /delete_temporary_events=true
-! /add_bad_event_on_delete=false
-! /fp_min=40
-**;**
-====== breakdown ======
-this command uses multiple tests to check if the force assignments are created correctly. users should still manually check that force assignments are created correctly.
+<code>
+Force_Assignment_Quality_Assurance
+! /MIN_STANCE_TIME=0.2
+! /MAX_STANCE_TIME=1.0
+! /MIN_STANCE_GRF=0.95
+! /MAX_STANCE_GRF=1.3
+! /MAX_COP_PATH_DISTANCE=4
+! /DELETE_TEMPORARY_EVENTS=TRUE
+! /ADD_BAD_EVENT_ON_DELETE=FALSE
+! /FP_MIN=40
+;
+</code>
+===== Breakdown =====
-==== cop distance test ====
+This command uses multiple tests to check if the force assignments are created correctly. Users should still manually check that force assignments are created correctly.
-force assignments are created when a segment is within a specified distance from the center of pressure. this distance is stored as the [[visual3d:documentation:modeling:segments:segment_to_cofp_distance|segment_to_cofp_distance]] in the model template.
+=== COP Distance Test ===
-it is always recommended to leave this value as 0.2 meters, unless you have a very good reason to change this. for some reason, this value has been set to 20 meters in a lot of user's templates. if you receive this warning, it is recommended to just change the [[visual3d:documentation:modeling:segments:segment_to_cofp_distance|segment_to_cofp_distance]] in your model template to 0.2 meters.
+Force assignments are created when a segment is within a specified distance from the center of pressure. This distance is stored as the [[Visual3D:Documentation:Modeling:Segments:Segment_to_COFP_Distance|Segment_to_COFP_Distance]] in the model template.
-==== filter test ====
+It is always recommended to leave this value as 0.2 meters, unless you have a very good reason to change this. For some reason, this value has been set to 20 meters in a lot of user's templates. If you receive this warning, it is recommended to just change the [[Visual3D:Documentation:Modeling:Segments:Segment_to_COFP_Distance|Segment_to_COFP_Distance]] in your model template to 0.2 meters.
-this check will not modify anything, but a warning will be displayed to ensure your filtering is set up as desired.
+=== Filter Test ===
-since the force, cofp, and freemoment folders are calculated from the analog folder, it is recommended to only filter the analog folder. if you choose to filter the force folder instead, you should make sure to filter the force, cofp, and freemoment folders.
+This check will not modify anything, but a warning will be displayed to ensure your filtering is set up as desired.
-you do not want to filter the analog and the force, cofp, and freemoment folders, because then you are filtering your data twice.
+Since the FORCE, COFP, and FREEMOMENT folders are calculated from the ANALOG folder, it is recommended to only filter the ANALOG folder. If you choose to filter the FORCE folder instead, you should make sure to filter the FORCE, COFP, and FREEMOMENT folders.
-visual3d will only create the force, cofp, and freemoment folders from the processed analog signals if you have specified to use the [[visual3d:documentation:visual3d_signal_types:used_process#process_analog_data|processed analog data]]. a warning will be displayed if you have filtered the analog signals, but have not set visual3d to use the processed analog data.
+You do not want to filter the ANALOG and the FORCE, COFP, and FREEMOMENT folders, because then you are filtering your data twice.
-==== fp zero test ====
+Visual3D will only create the FORCE, COFP, and FREEMOMENT folders from the processed ANALOG signals if you have specified to use the [[Visual3D:Documentation:Visual3D_Signal_Types:Used_Process#Process_Analog_Data|Processed Analog Data]]. A warning will be displayed if you have filtered the ANALOG signals, but have not set Visual3D to use the processed Analog data.
-in your force platform parameters, there is an option to zero the force platforms using a specified frame range. this is specified in your motion capture system, and is called the [[visual3d:documentation:pipeline:force_commands:fp_zero|fp_zero parameter]].
+=== FP Zero Test ===
-a segment is assumed to be on the platform if the projection of the proximal end of the segment falls on the force platform and if the distance from the proximal end of the segment to the force platform is less than the min_seg_height parameter.
+In your force platform parameters, there is an option to zero the force platforms using a specified frame range. This is specified in your motion capture system, and is called the [[Visual3D:Documentation:Pipeline:Force_Commands:FP_ZERO|FP_ZERO parameter]].
-nothing in your file will be modified from this test, but a warning will be displayed for you to check the zero values
+A segment is assumed to be on the platform if the projection of the proximal end of the segment falls on the force platform and if the distance from the proximal end of the segment to the force platform is less than the MIN_SEG_HEIGHT parameter.
-==== remove incomplete assignment test ====
+Nothing in your file will be modified from this test, but a warning will be displayed for you to check the zero values
-you do not want to calculate kinetics using incomplete assignments, so if the trial starts with the segment on the platform or ends with the segment off the platform, the assignment is removed.
+=== Remove Incomplete Assignment Test ===
-==== cop distance test ====
+You do not want to calculate kinetics using incomplete assignments, so if the trial starts with the segment on the platform or ends with the segment off the platform, the assignment is removed.
-uses:
+=== COP Distance Test ===
-  * max_cop_path_distance
+Uses:
-the path distance the cop travels over the force assignment is calculated.
+  * MAX_COP_PATH_DISTANCE
-the signal used internally is normalized to the segment length
+The path distance the COP travels over the force assignment is calculated.
-==== grf max test ====
+The signal used internally is normalized to the segment length
-uses:
+=== GRF Max Test ===
-  * min_stance_grf=0.95
+Uses:
-  * max_stance_grf=1.3
-the maximum grf over each force assignment is calculated.
+  * MIN_STANCE_GRF=0.95
+  * MAX_STANCE_GRF=1.3
-the signal is normalized to the mass of the subject.
+The maximum GRF over each force assignment is calculated.
-==== stance time test ====
+The signal is normalized to the mass of the subject.
-uses:
+=== Stance Time Test ===
-  * min_stance_time=0.2
+Uses:
-  * /max_stance_time=1.0
-the stance time for each force assignment is calculated.
+  * MIN_STANCE_TIME=0.2
+  * /MAX_STANCE_TIME=1.0
-it is expected that the stance time will be above 0.2 seconds and below 1 second. the user should modify this as necessary.
+The stance time for each force assignment is calculated.
-==== segment position test ====
+It is expected that the stance time will be above 0.2 seconds and below 1 second. The user should modify this as necessary.
-for each force assignment, the proximal and distal end of the segment is projected onto the force platform. if the proximal and distal ends are not on the force platform for the entire assignment, the force assignment is removed.
+=== Segment Position Test ===
+For each force assignment, the proximal and distal end of the segment is projected onto the force platform. If the proximal and distal ends are not on the force platform for the entire assignment, the force assignment is removed.