This is an old revision of the document!
Table of Contents
Export a file from the Workspace to a C3D file suitable for Vicon's Polygon program. Sample files can be found on the Polygon Example Export page.
NOTE: This is an area in which HAS-Motion and Vicon agree to disagree. A few Visual3D customers have requested that we export C3D files containing information pertinent to Polygon. If it weren't for these requests, we would not have done so because we do not approve of putting PROCESSED data into the C3D file. Polygon requires additional information than that contained in a typical C3D file. Visual3D exports LINK_MODEL_BASED signals, and context dependent EVENT LABELS to POLYGON allowing Kinematic and Kinetic data to be reported in POLYGON. Animating objects in POLYGON requires additional data and an additional file to be created by Visual3D. Visual3D, therefore, creates additional landmarks for defining the position and orientation of a segment, and an MKR file defining which wireframe objects are associated with the segments.
Command Syntax
Export_Polygon_C3DFile
! /OLD_FILE_NAME= Exports ALL_FILES, TAGS, or Wildcards (*)
! /NEW_FILE_NAME= If NEW_FILE_NAME is empty, SUFFIX is added
! /DESTINATION_FOLDER= If DESTINATION_FOLDER is empty, the user is prompted for a folder
! /V3D_SEGMENT_ARRAY=
! /SEGMENT_DESCRIPTION=
! /POLYGON_EVENT_CONTEXT=
! /POLYGON_EVENT_ICON=
! /POLYGON_EVENT_NAME=
! /POLYGON_EVENT_SUBJECT=
! /V3D_EVENT_NAME=
! /EVENT_DESCRIPTIONS=
! /POLYGON_SIGNAL_ITEMS_ARRAY=
! /V3D_SIGNAL_TYPES_ARRAY=
! /V3D_SIGNAL_FOLDERS_ARRAY=
! /V3D_SIGNAL_NAMES_ARRAY=
! /SUFFIX=_ If a new filename is not specified, Visual3D will add the suffix to the old filename.
! /Export_Endian=2
! /REPLACE_POLY_TARGETS=FALSE
;
NOTE: Visual3D NEVER recommends over writing original data files. For this reason the NEW_FILE_NAME parameter should be different from the original file name, or the SUFFIX parameter should be used.
Polygon_Segment_Array
This is linked tightly with V3D_Segment_Array
These parameters contain the name of the Polygon segment (these are hardcoded by Polygon) and the corresponding segment name in Visual3D.
This is needed because Visual3D allows multiple versions of a segment, and it may be that the segment used for Visual3D processing is different than the segment definition needed for Polygon animation.
Note that Polygon doesn't do any substantial processing, so this means that the model based definitions in Visual3D might not be consistent with a signal of the same name computed by Plugin Gait.
V3D_Segment_Array
Default Segment Arrays
Polygon Segment | Visual3D Segment | Visual3D 3 letter acronym |
PEL | Pelvis | RPV |
RFE | Right Thigh | RTH |
RTI | Right Shank | RSK |
RFO | Right Foot | RFT |
LFE | Left Thigh | LTH |
LTI | Left Shank | LSK |
LFO | Left Foot | LFT |
HED | Head | RHE |
RHU | Right Arm | RAR |
RRA | Right Forearm | RFA |
RHN | Right Hand | RHA |
LHU | Left Arm | LAR |
LRA | Left Forearm | LFA |
LHN | Left Hand | LHA |
TRX | Thorax | RTA |