HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » pipeline » force_commands » FP ZERO
visual3d:documentation:pipeline:force_commands:fp_zero

Differences

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

Link to this comparison view

Next revision		Previous revision
visual3d:documentation:pipeline:force_commands:fp_zero [2024/06/14 17:27] – created sgrangervisual3d:documentation:pipeline:force_commands:fp_zero [2024/07/17 15:45] (current) – created sgranger
Line 1: Line 1:
-|**Language:**|** English**  • [[index.php?title=FP_ZERO/fr&action=edit&redlink=1|français]] • [[index.php?title=FP_ZERO/it&action=edit&redlink=1|italiano]] • [[FP_ZERO/pt|português]] • [[index.php?title=FP_ZERO/es&action=edit&redlink=1|español]] ****| +====== FP ZERO ======
- +
-|===== Contents =====\\ \\ \\ \\ * [[#Exceptions|1 Exceptions]]\\   * [[#Example_1|1.1 Example 1]]\\   * [[#Example_2|1.2 Example 2]]\\   * [[#Example_3|1.3 Example 3]]|+
  
 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]]. 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. 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. In all 3 examples the ZERO parameter should be set to 0,0 so that no inadvertent baseline is removed.
  
-==== Example 1 ====+=== Example 1 ===
  
 1. Subtracting the mean value from several ranges from each analog signal 1. Subtracting the mean value from several ranges from each analog signal
Line 79: Line 77:
 /Iteration_Parameter_Name= SIGNAL_INDEX /Iteration_Parameter_Name= SIGNAL_INDEX
 **;** **;**
-==== Example 2 ====+=== Example 2 ===
  
 Subtracting the mean value from several ranges from each analog signal Subtracting the mean value from several ranges from each analog signal
Line 130: Line 128:
 /ITERATION_PARAMETER_NAME=SIGNAL_INDEX /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 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 /ITERATION_PARAMETER_NAME=SIG
 **;** **;**
- 
-Retrieved from "" 
  
  
visual3d/documentation/pipeline/force_commands/fp_zero.1718386027.txt.gz · Last modified: 2024/06/14 17:27 by sgranger