Differences

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

--- visual3d:documentation:pipeline:force_commands:modify_force_platform_parameters [2024/06/19 12:50] – sgranger
+++ visual3d:documentation:pipeline:force_commands:modify_force_platform_parameters [2024/09/10 20:39] (current) – wikisysop
@@ Line 1: / Line 1: @@
-{{a common challenge for a manufacturer creating c3d formatted datafiles is the declaration of the force platform properties in the parameter section of the file. these parameters specify how the analog signals stored in the c3d file should be transformed into the grf, cofp, and freemoment signals that you see in visual3d. the following minimal set of force platform parameters is assumed to exist in the c3d file.
+====== Modify Force Platform Parameters ======
-parameters:force_platform:
+A common challenge for a manufacturer creating C3D formatted datafiles is the declaration of the Force Platform properties in the parameter section of the file. These parameters specify how the ANALOG signals stored in the C3D file should be transformed into the GRF, COFP, and FREEMOMENT signals that you see in Visual3D. The following minimal set of force platform parameters is assumed to exist in the C3D File.
-used= number of force platforms used
-type= types of force platforms (1=default, 2= amti,bertec, 3= kistler)
-zero= the range of frames for which a background noise level is calculated and then subtracted from each of the analog channels
-channel= an array containing the analog channels associated with the force platform
-origin= the origin of the force platform in the force platform coordinate system (see the force platform manufacturer specifications.
-corners= the (x,y,z) coordinates of the force platform corners in the laboratory coordinate system. note that there is a specific ordering of the four corners.
-there are several minor inconsistencies in the way that manufacturers create c3d files. visual3d currently uses script commands to "fix" these inconsistencies. please contact c-motion to determine if you need to process the c3d files that have been produced by your motion capture system.
-===== modify_force_platform_parameters command =====
+<code>
+PARAMETERS:FORCE_PLATFORM:
+USED= number of force platforms used
+TYPE= types of force platforms (1=default, 2= AMTI,Bertec, 3= Kistler)
+ZERO= the range of frames for which a background noise level is calculated and then subtracted from each of the analog channels
+CHANNEL= an array containing the ANALOG channels associated with the force platform
+ORIGIN= The origin of the force platform in the force platform coordinate system (see the force platform manufacturer specifications.
+CORNERS= The (x,y,z) coordinates of the force platform corners in the laboratory coordinate system. Note that there is a [[visual3d:documentation:pipeline:force_commands:fp_corners|specific ordering of the four corners]].
+There are several minor inconsistencies in the way that manufacturers create C3D files. Visual3D currently uses script commands to "FIX" these inconsistencies. Please contact HAS-Motion to determine if you need to process the C3D files that have been produced by your motion capture system.
+</code>
+==== Modify_Force_Platform_Parameters Command ====
-**modify_force_platform_parameters**
+<code>
-! /[[visual3d:documentation:pipeline:force_commands:fp_used|fp_used]]=
+Modify_Force_Platform_Parameters
-! /[[visual3d:documentation:pipeline:force_commands:fp_type|fp_type]]=
+! /[[Visual3D:Documentation:Pipeline:Force_Commands:FP_USED|FP_USED]]=
-! /fp_channel=
+! /[[Visual3D:Documentation:Pipeline:Force_Commands:FP_TYPE|FP_TYPE]]=
-! /fp_origin=
+! /FP_CHANNEL=
-! /fp_calmatrix=
+! /FP_ORIGIN=
-! /store_calmatrix=byrow
+! /FP_CALMATRIX=
-! /[[visual3d:documentation:pipeline:force_commands:fp_zero|fp_zero]]=
+! /STORE_CALMATRIX=BYROW
-! /[[visual3d:documentation:pipeline:force_commands:fp_zeros|fp_zeros]]=
+! /[[Visual3D:Documentation:Pipeline:Force_Commands:FP_ZERO|FP_ZERO]]=
-! /fp_corner1=
+! /[[Visual3D:Documentation:Pipeline:Force_Commands:FP_ZEROS|FP_ZEROS]]=
-! /fp_corner2=
+! /FP_CORNER1=
-! /fp_corner3=
+! /FP_CORNER2=
-! /fp_corner4=
+! /FP_CORNER3=
-! /fp_cop_polynomial=
+! /FP_CORNER4=
-! /fp_cop_translation=
+! /FP_COP_POLYNOMIAL=
-! /fp_cop_rotation=
+! /FP_COP_TRANSLATION=
-/[[visual3d:documentation:pipeline:file_commands:update_c3d_file|update_c3d_file]]=false
+! /FP_COP_ROTATION=
-! /modify_cal_file=false
+/Update_C3D_File=FALSE
-**;**
+! /MODIFY_CAL_FILE=FALSE
-note that fp_used refers to the number of platforms in the c3d file.
+;
+</code>
-==== modify a subset of the parameters ====
+Note that FP_Used refers to the number of platforms in the c3d file.
-note that it is possible to modify a single parameters. for example, to modify only the corners.
+=== Modify a subset of the parameters ===
-**modify_force_platform_parameters**
+Note that it is possible to modify a single parameters. For example, to modify only the corners.
-/fp_corner1=0+100+0
-/fp_corner2=100+100+0
-/fp_corner3=100+0+0
-/fp_corner4=0+0+0
-**;**
-==== modify fpzero using endoffile ====
-if all trials start with the force platform loaded, but end the file with the force platform unloaded, you can specify the last 10 frames of data as follows:
+<code>
+Modify_Force_Platform_Parameters
+/FP_CORNER1=0+100+0
+/FP_CORNER2=100+100+0
+/FP_CORNER3=100+0+0
+/FP_CORNER4=0+0+0
+;
+</code>
+=== Modify FPZero using EndOfFile ===
-**modify_force_platform_parameters**
+If all trials start with the force platform loaded, but end the file with the force platform unloaded, you can specify the last 10 frames of data as follows:
-/fp_used=2
+<code>
-/fp_zero=eof-10+eof
+Modify_Force_Platform_Parameters
-/fp_zeros=eof-10+eof+eof-10+eof
+/FP_USED=2
-**;**
+/FP_ZERO=EOF-10+EOF
-where eof refers to the last frame of data (e.g. **e**nd **o**f **f**ile)
+/FP_ZEROS=EOF-10+EOF+EOF-10+EOF
+;
+</code>
+where EOF refers to the last frame of data (e.g. **E**nd **O**f **F**ile)
-==== original vs processed ====
+=== ORIGINAL vs PROCESSED ===
-many users have commented that modifying the force platform parameters doesn't seem to have any affect. this is often caused by the presence of processed force, center of pressure, and free moment signals.
+Many users have commented that modifying the force platform parameters doesn't seem to have any affect. This is often caused by the presence of PROCESSED Force, Center of Pressure, and Free Moment signals.
-modifying the parameters affects the original signals. if there are processed signals, they are unaffected, and need to be processed again.
+Modifying the parameters affects the ORIGINAL signals. If there are PROCESSED signals, they are unaffected, and need to be processed again.
-[[visual3d:documentation:visual3d_signal_types:used_process#why_filter_the_analog_vs_force_data|however, we do not recommend filtering the force/cofp/freemoment signals.]]
+[[Visual3D:Documentation:Visual3D_Signal_Types:Used_Process#Why_filter_the_ANALOG_vs_Force_Data|However, we do NOT recommend filtering the Force/COFP/Freemoment signals.]]
-===== modify_force_platform_parameters command dialog =====
+==== Modify_Force_Platform_Parameters Command Dialog ====
-it is also possible to modify force platform parameters via the graphical interface's dialog located in visual3d's force menu. the dialog provides you with an overview of all the current force platform parameter values and allows you to edit and save these values.
+It is also possible to modify force platform parameters via the graphical interface's dialog located in Visual3D's Force menu. The dialog provides you with an overview of all the current force platform parameter values and allows you to edit and save these values.
+{{:Amti4.png}}
-amti4.png
-}}