HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » pipeline » file_commands » Export Polygon C3DFile
visual3d:documentation:pipeline:file_commands:export_polygon_c3dfile

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
visual3d:documentation:pipeline:file_commands:export_polygon_c3dfile [2024/06/26 20:25] – created sgrangervisual3d:documentation:pipeline:file_commands:export_polygon_c3dfile [2024/12/27 13:38] (current) – wikisysop
Line 1: Line 1:
-====== Export_Polygon_C3DFile ======+====== 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 [[Visual3D:Documentation:Pipeline:File_Commands:Export_Polygon_Trunk_Example|Polygon Example Export page]]. Export a file from the Workspace to a C3D file suitable for Vicon's Polygon program. Sample files can be found on the [[Visual3D:Documentation:Pipeline:File_Commands:Export_Polygon_Trunk_Example|Polygon Example Export page]].
Line 7: Line 7:
 ==== Command Syntax ==== ==== Command Syntax ====
  
-**Export_Polygon_C3DFile**\\ +<code> 
- +Export_Polygon_C3DFile 
-**! /OLD_FILE_NAME=** Exports ALL_FILES, TAGS, or Wildcards (*)\\ +! /OLD_FILE_NAME=** Exports ALL_FILES, TAGS, or Wildcards (*)\\ 
- +! /NEW_FILE_NAME=** If NEW_FILE_NAME is empty, SUFFIX is added\\ 
-**! /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|Polygon_Segment_Array]]=**\\ 
-**! /DESTINATION_FOLDER=** If DESTINATION_FOLDER is empty, the user is prompted for a folder\\ +! /V3D_SEGMENT_ARRAY=**\\ 
- +! /SEGMENT_DESCRIPTION=**\\ 
-**! /[[#Polygon_Segment_Array|Polygon_Segment_Array]]=**\\ +! /POLYGON_EVENT_CONTEXT=**\\ 
- +! /POLYGON_EVENT_ICON=**\\ 
-**! /V3D_SEGMENT_ARRAY=**\\ +! /POLYGON_EVENT_NAME=**\\ 
- +! /POLYGON_EVENT_SUBJECT=**\\ 
-**! /SEGMENT_DESCRIPTION=**\\ +! /V3D_EVENT_NAME=**\\ 
- +! /EVENT_DESCRIPTIONS=**\\ 
-**! /POLYGON_EVENT_CONTEXT=**\\ +! /POLYGON_SIGNAL_ITEMS_ARRAY=**\\ 
- +! /V3D_SIGNAL_TYPES_ARRAY=**\\ 
-**! /POLYGON_EVENT_ICON=**\\ +! /V3D_SIGNAL_FOLDERS_ARRAY=**\\ 
- +! /V3D_SIGNAL_NAMES_ARRAY=**\\ 
-**! /POLYGON_EVENT_NAME=**\\ +! /SUFFIX=_** If a new filename is not specified, Visual3D will add the **suffix** to the old filename.\\ 
- +! /[[#Endian_Parameter|Export_Endian]]=2**\\ 
-**! /POLYGON_EVENT_SUBJECT=**\\ +! /REPLACE_POLY_TARGETS=FALSE**\\ 
- +; 
-**! /V3D_EVENT_NAME=**\\ +</code>
- +
-**! /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.\\ +
- +
-**! /[[#Endian_Parameter|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. **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.
Line 84: Line 66:
 ==== Edit Dialog ==== ==== Edit Dialog ====
  
-|{{ExportPolygonDlg.jpg}}  |**Map Visual3D Segments to Polygon Segments**\\ The default Polygon segment names are listed in the drop down menu and should correspond to the correct Visual3D segment names. The default list of Visual3D segment names is listed [[#Default_Segment_Arrays|here]]. The description is a label for the user to identify the segment names.\\ \\ **Map Visual3D Events to Polygon Events**\\ The events used to identify heel strike and toe off in Visual3D should correspond to the default Polygon labels. The default labels in Visual3D are ON/OFF.\\ \\ **Map Visual3D Items to Polygon Items**\\ The Polygon item list should correspond to the name of the relevant signal. For example, the RAnkleAngle will correspond to the ankle angle created in the Compute Model Based dialog. In this case, the Visual3D Type will be "Link_Model_Based", the Visual3D Folders will be "Original" and the Visual3D signals parameter is the signal name (which is user defined).\\   |+|{{:ExportPolygonDlg.jpg}}  |**Map Visual3D Segments to Polygon Segments**\\ The default Polygon segment names are listed in the drop down menu and should correspond to the correct Visual3D segment names. The default list of Visual3D segment names is listed [[#Default_Segment_Arrays|here]]. The description is a label for the user to identify the segment names.\\ \\ **Map Visual3D Events to Polygon Events**\\ The events used to identify heel strike and toe off in Visual3D should correspond to the default Polygon labels. The default labels in Visual3D are ON/OFF.\\ \\ **Map Visual3D Items to Polygon Items**\\ The Polygon item list should correspond to the name of the relevant signal. For example, the RAnkleAngle will correspond to the ankle angle created in the Compute Model Based dialog. In this case, the Visual3D Type will be "Link_Model_Based", the Visual3D Folders will be "Original" and the Visual3D signals parameter is the signal name (which is user defined).\\   |
  
 ==== Segment Scaling ==== ==== Segment Scaling ====
visual3d/documentation/pipeline/file_commands/export_polygon_c3dfile.1719433521.txt.gz · Last modified: 2024/06/26 20:25 by sgranger