Export Polygon C3DFile
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.
- ! /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
- ! /Polygon_Segment_Array=
- ! /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.
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.
Default Segment Arrays
|Polygon Segment||Visual3D Segment||Visual3D 3 letter acronym|
Map Visual3D Segments to Polygon Segments
In Polygon the segment graphic is scaled based on the length of the segment. The length of the segment in Visual3D is determined by the distance between the proximal and distal ends of the segment.
Polygon defines the trunk differently from the other segments. If you export from Visual3D into Polygon, and the trunk appears upside down, backwards and scaled larger than expected, the following steps can be used to modify the trunk orientation and scale.
Upside Down Trunk
In Visual3D user's are free to define segments using their own convention, however, many users define the proximal end of the trunk as the end closest to the shoulders. Polygon defines the proximal end of the trunk as the end closest to the waist. The Polygon convention will need to be followed when exporting to Polygon.
In Visual3D user's are free to define segments using their own convention, however, many users define the lateral side of the trunk as the RIGHT side. Polygon defines the lateral side of the trunk as LEFT side. The Polygon convention will need to be followed when exporting to Polygon.
In Visual3D user's are free to define segments using their own convention, however, many users define the ends of the trunk from the shoulders to the waist. Polygon defines the ends of the trunk from the shoulders to the abdomen (bottom of the ribs). The Polygon convention will need to be followed when exporting to Polygon.
To define a trunk segment which follows the normal convention and will appear correctly in the Polygon skeleton viewer you will need to:
- Modify to the definition of the trunk segment:
- Define the proximal end of the trunk at the mid thorax
- Define the distal end at the shoulders
- Define the lateral side of the trunk as the left side
- In the Segment Properties tab, modify the segment coordinate system to follow the convention of the other segments
NOTE: Modifying the trunk coordinate system in the Segment Properties tab will not affect the orientation of the trunk in Polygon. This step is necessary to calculate any kinematics/kinetics involving the trunk segment.
An Example (with sample files) can be found here.