Differences

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

--- visual3d:documentation:pipeline:force_commands:fp_auto_baseline [2026/07/02 18:42] – [Example: Defining Auto Baseline for FP Under Left Foot] wikisysop
+++ visual3d:documentation:pipeline:force_commands:fp_auto_baseline [2026/07/02 18:51] (current) – [Important notes when using FP_Auto_Baseline with noisy analog data:] wikisysop
@@ Line 56: / Line 56: @@
 </code>
-====Important notes when using FP_Auto_Baseline with filtered analog data:====
+====Important notes when using FP_Auto_Baseline with noisy analog data:====
-When
+Visual3D estimates the baseline force using a clustering algorithm to find the most representative force. This approach uses only the force signal to identify the minimum force and does not include center of pressure or free moment signals in its calculation. \\ \\ The baseline values for the COP and FREEMOMENT are specified by the frame number at which the representative force is found. As the representative force is a statistical measure, it can vary with the data set (i.e. the frame of data for the representative force could be different for different ranges of frames). \\ \\ For filtered data, the COP and FREEMOMENT signals at the representative FORCE frame are usually consistent across different ranges of frames. For unfiltered noisy data spurious noise at the representative force frame will result in an incorrect COP and FREEMOMENT. \\ \\ As such, when using FP_Auto_Baseline with noisy signals we recommend using the filtered analog signals (this can be done in settings) and first filtering the signals and recalcing before using FP_Auto_Baseline.