visual3d:documentation:pipeline:force_commands:fp_auto_baseline
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:documentation:pipeline:force_commands:fp_auto_baseline [2024/07/17 15:42] – removed sgranger | visual3d:documentation:pipeline:force_commands:fp_auto_baseline [2024/11/15 16:36] (current) – sgranger | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== FP Auto Baseline ====== | ||
+ | |||
+ | ==== Introduction ==== | ||
+ | |||
+ | \\ | ||
+ | Setting the [[visual3d: | ||
+ | \\ | ||
+ | **For Visual3D Version 6 we have introduced a new pipeline command: | ||
+ | \\ | ||
+ | |||
+ | |||
+ | |< | ||
+ | ! /FP_NUMBER= | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ; </ | ||
+ | |||
+ | ==== Background ==== | ||
+ | |||
+ | This command does three things: | ||
+ | |||
+ | - Zeros the force signal without having to specify a [[Visual3D: | ||
+ | - Defines the [[Visual3D: | ||
+ | - Looks at the before/ | ||
+ | |||
+ | The [[Visual3D: | ||
+ | |||
+ | |||
+ | ==== Parameters ==== | ||
+ | |||
+ | === FP Number === | ||
+ | |||
+ | \\ | ||
+ | **FP_NUMBER=** An empty parameter will work on all plates in the C3D file. Or you can specify individual plate numbers, separated by a plus sign (ex. / | ||
+ | \\ | ||
+ | |||
+ | |||
+ | === Auto Zero === | ||
+ | |||
+ | \\ | ||
+ | **AUTO_ZERO=** This parameter is used to zero the signal. The value of the zero baseline is stored in the C3D parameter FORCE_PLATFORM:: | ||
+ | \\ | ||
+ | This parameter would be used in place of the [[Visual3D: | ||
+ | \\ | ||
+ | |||
+ | |||
+ | === Auto FP Minimum === | ||
+ | |||
+ | \\ | ||
+ | **AUTO_FP_MINIMUM=** Visual3D determines the [[Visual3D: | ||
+ | \\ | ||
+ | To see what value is picked, after running the command, select an individual C3D file, and go to Force-> Modify Minimum Force Platform Value. The " | ||
+ | \\ | ||
+ | |||
+ | |||
+ | === Reduced FP Minimum Around Force === | ||
+ | |||
+ | \\ | ||
+ | **USE_REDUCED_FP_MINIMUM_AROUND_FORCE=** Visual3D determines when the force platform is loaded, and finds when the signal drops below the specified minimum value (REDUCED_FP_MINIMUM).\\ | ||
+ | \\ | ||
+ | **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.\\ | ||
+ | \\ | ||
+ | |||
+ | |||
+ | |||
visual3d/documentation/pipeline/force_commands/fp_auto_baseline.1721230944.txt.gz · Last modified: 2024/07/17 15:42 by sgranger