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 [2024/07/17 15:45] (current) – created sgranger
@@ 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
+**Force_Assignment_Quality_Assurance**
-! /min_stance_grf=0.95
+! /MIN_STANCE_TIME=0.2
-! /max_stance_grf=1.3
+! /MAX_STANCE_TIME=1.0
-! /max_cop_path_distance=4
+! /MIN_STANCE_GRF=0.95
-! /delete_temporary_events=true
+! /MAX_STANCE_GRF=1.3
-! /add_bad_event_on_delete=false
+! /MAX_COP_PATH_DISTANCE=4
-! /fp_min=40
+! /DELETE_TEMPORARY_EVENTS=TRUE
+! /ADD_BAD_EVENT_ON_DELETE=FALSE
+! /FP_MIN=40
 **;**
-====== breakdown ======
+===== 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.
+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.
-==== cop distance test ====
+=== COP Distance Test ===
-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.
+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.
-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.
+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.
-==== filter test ====
+=== Filter Test ===
-this check will not modify anything, but a warning will be displayed to ensure your filtering is set up as desired.
+This check will not modify anything, but a warning will be displayed to ensure your filtering is set up as desired.
-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.
+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.
-you do not want to filter the analog and the force, cofp, and freemoment folders, because then you are filtering your data twice.
+You do not want to filter the ANALOG and the FORCE, COFP, and FREEMOMENT folders, because then you are filtering your data twice.
-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.
+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.
-==== fp zero test ====
+=== FP Zero Test ===
-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]].
+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]].
-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.
+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.
-nothing in your file will be modified from this test, but a warning will be displayed for you to check the zero values
+Nothing in your file will be modified from this test, but a warning will be displayed for you to check the zero values
-==== remove incomplete assignment test ====
+=== Remove Incomplete Assignment 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.
+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.
-==== cop distance test ====
+=== COP Distance Test ===
-uses:
+Uses:
-  * max_cop_path_distance
+  * MAX_COP_PATH_DISTANCE
-the path distance the cop travels over the force assignment is calculated.
+The path distance the COP travels over the force assignment is calculated.
-the signal used internally is normalized to the segment length
+The signal used internally is normalized to the segment length
-==== grf max test ====
+=== GRF Max Test ===
-uses:
+Uses:
-  * min_stance_grf=0.95
+  * MIN_STANCE_GRF=0.95
-  * max_stance_grf=1.3
+  * MAX_STANCE_GRF=1.3
-the maximum grf over each force assignment is calculated.
+The maximum GRF over each force assignment is calculated.
-the signal is normalized to the mass of the subject.
+The signal is normalized to the mass of the subject.
-==== stance time test ====
+=== Stance Time Test ===
-uses:
+Uses:
-  * min_stance_time=0.2
+  * MIN_STANCE_TIME=0.2
-  * /max_stance_time=1.0
+  * /MAX_STANCE_TIME=1.0
-the stance time for each force assignment is calculated.
+The stance time for each force assignment is calculated.
-it is expected that the stance time will be above 0.2 seconds and below 1 second. the user should modify this as necessary.
+It is expected that the stance time will be above 0.2 seconds and below 1 second. The user should modify this as necessary.
-==== segment position test ====
+=== 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.
+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.