Differences

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

--- visual3d:documentation:pipeline:force_commands:fp_zero [2024/06/17 18:19] – created sgranger
+++ visual3d:documentation:pipeline:force_commands:fp_zero [2024/07/17 15:45] (current) – created sgranger
@@ Line 1: / Line 1: @@
+====== FP ZERO ======
 This page is about the C3D Parameter FORCE_PLATFORM:ZERO. For Visual3D's ability to track different baseline frames for different force platforms see [[Visual3D:Documentation:Pipeline:Force_Commands:FP_ZEROS|FP_ZEROS]].
@@ Line 12: / Line 10: @@
-===== Exceptions =====
+==== Exceptions ====
 In some cases it is not feasible to use the ZERO parameter to define a BASELINE for each signal. All force platform signals have some drift in the amplifiers, so it isn't a good idea to simply set the ZERO parameter to 0,0 so that no baseline is subtracted. The following two examples demonstrate alternatives to using the ZERO parameter to remove a baseline.
@@ Line 18: / Line 16: @@
 In all 3 examples the ZERO parameter should be set to 0,0 so that no inadvertent baseline is removed.
-==== Example 1 ====
+=== Example 1 ===
 . Subtracting the mean value from several ranges from each analog signal
@@ Line 79: / Line 77: @@
 /Iteration_Parameter_Name= SIGNAL_INDEX
 **;**
-==== Example 2 ====
+=== Example 2 ===
 Subtracting the mean value from several ranges from each analog signal
@@ Line 130: / Line 128: @@
 /ITERATION_PARAMETER_NAME=SIGNAL_INDEX
 **;**
-==== Example 3 ====
+=== Example 3 ===
 Computing mean values for the force platform analog signals in one trial, and then use these values in other trials
@@ Line 207: / Line 205: @@
 /ITERATION_PARAMETER_NAME=SIG
 **;**