Differences

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

--- visual3d:documentation:pipeline:force_commands:fp_auto_baseline [2024/06/19 14:00] – created sgranger
+++ visual3d:documentation:pipeline:force_commands:fp_auto_baseline [2024/11/15 16:36] (current) – sgranger
@@ Line 1: / Line 1: @@
-===== Introduction =====
+====== FP Auto Baseline ======
+==== Introduction ====
 \\
-Setting the [[https://www.c-motion.com/v3dwiki/index.php/FP_ZERO|Force Platform Zero]] parameters for Instrumented Treadmills can be quite challenging because the unloaded frames aren't readily identified automatically, and one would prefer to use all of the unloaded frames for determining the zero range.\\
+Setting the [[visual3d:documentation:pipeline:force_commands:fp_zero]] parameters for Instrumented Treadmills can be quite challenging because the unloaded frames aren't readily identified automatically, and one would prefer to use all of the unloaded frames for determining the zero range.\\
 \\
 **For Visual3D Version 6 we have introduced a new pipeline command:**\\
@@ Line 8: / Line 10: @@
-|<code>\\ FP_Auto_Baseline\\ ! /FP_NUMBER=\\ ! /AUTO_ZERO=TRUE\\ ! /AUTO_FP_MINIMUM=TRUE\\ ! /USE_REDUCED_FP_MINIMUM_AROUND_FORCE=TRUE\\ ! /REDUCED_FP_MINIMUM=5.0\\ ;\\ </code>  |{{FP_Auto_Baseline1.png}}  |
+|<code>FP_Auto_Baseline
+ ! /FP_NUMBER=
+ ! /AUTO_ZERO=TRUE
+ ! /AUTO_FP_MINIMUM=TRUE
+ ! /USE_REDUCED_FP_MINIMUM_AROUND_FORCE=TRUE
+ ! /REDUCED_FP_MINIMUM=5.0
+ ; </code> |{{:FP_Auto_Baseline1.png}}  |
-===== Background =====
+==== Background ====
 This command does three things:
@@ Line 21: / Line 29: @@
-===== Parameters =====
+==== Parameters ====
-==== FP Number ====
+=== FP Number ===
 \\
@@ Line 30: / Line 38: @@
-==== Auto Zero ====
+=== Auto Zero ===
 \\
@@ Line 39: / Line 47: @@
-==== Auto FP Minimum ====
+=== Auto FP Minimum ===
 \\
@@ Line 48: / Line 56: @@
-==== Reduced FP Minimum Around Force ====
+=== Reduced FP Minimum Around Force ===
 \\
@@ Line 55: / Line 63: @@
 **REDUCED_FP_MINIMUM =** Used when USE_REDUCED_FP_MINIMUM_AROUND_FORCE parameter is set to TRUE\\
 \\
-**Why is this parameter so important?** When there are two platforms in the treadmill there may be times when one foot is on two platforms (the other foot is not). The transitions from one foot on one platform to two platforms (or vice-versa) often causes an artifact (sudden change) in the force signal that is about the magnitude of the minimum force threshold. This artifact is most commonly seen with a front to back treadmill than a side to side. This parameter is used to resolve this discontinuity by using an alternate minimum force surrounding known contiguous force intervals to include relevant force readings that may be below the noise threshold, but still rising or lowering from the REDUCED_FP_MINIMUM value. This avoids the FP Minimum value discontinuity when FP transitions occur and combines the two signals into one force and cop signal, then reapplies the force minimum threshold.\\
+**Why is this parameter so important?**
+When there are two platforms in the treadmill there may be times when one foot is on two platforms (the other foot is not). The transitions from one foot on one platform to two platforms (or vice-versa) often causes an artifact (sudden change) in the force signal that is about the magnitude of the minimum force threshold. This artifact is most commonly seen with a front to back treadmill than a side to side. This parameter is used to resolve this discontinuity by using an alternate minimum force surrounding known contiguous force intervals to include relevant force readings that may be below the noise threshold, but still rising or lowering from the REDUCED_FP_MINIMUM value. This avoids the FP Minimum value discontinuity when FP transitions occur and combines the two signals into one force and cop signal, then reapplies the force minimum threshold.\\
 \\