Wiki Documentation Site

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » definitions » file_formats » ASCII Format
visual3d:documentation:definitions:file_formats:ascii_format

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:definitions:file_formats:ascii_format [2024/06/19 12:47] – sgrangervisual3d:documentation:definitions:file_formats:ascii_format [2026/03/09 07:41] (current) – Reorganized page and removed references to hidden commands. wikisysop
Line 1: Line 1:
-{{{{{{visual3d reads and writes the c3d data file format developed by andrew dainis and doug mcguire in 1987. the c3d formatted file is a compact binary data file used as a convenient and efficient means for storing 3d coordinate and analog data, with all associated parameters, for a single measurement trial. the [[visual3d:documentation:c3d_signal_types:c3d_format#c3d_parameter_format|c3d format]] is a publicly defined format and is currently implemented by most motion capture vendors.+====== ASCII Format ======
  
-data file stored in formats other than the c3d format must be translated into the c3d format. c-motion provides several plugin for translating data files.+Visual3D reads and writes the [[visual3d:documentation:c3d_signal_types:c3d_format|C3D data file format]] developed by Andrew Dainis and Doug McGuire in 1987. The C3D formatted file is a compact binary data file used as a convenient and efficient means for storing 3D coordinate and analog data, with all associated parameters, for a single measurement trial. The C3D format is a publicly defined format and is currently implemented by most motion capture vendors. See [[https://c3d.org/|C3D.org]] for a full description of the file format and its use by the biomechanics community.
  
-there are a wide variety of ascii formatted data files. visual3d will load many of these files into visual3d; translating them into c3d format in the process.+Data file stored in formats other than the C3D format must be translated, either by the user or internally by Visual3D, into the C3D Format. One popular alternative format is ASCII-formatted text files. There are a wide variety of these ASCII-formatted files and Visual3D will load many of them; translating them into C3D format in the process. It is quite a challenge to read all varieties of ASCII formatted files, but we do our best to accommodate data that our users collect. If Visual3D does not import your formatted files, contact support@has-motion.ca and request that we implement your format. We recognize that the first task to analyze your data is to be able to load the files, so we try hard to make sure that users have their data.
  
-it is quite a challenge to read all varieties of ascii formatted files, but we do our best to accommodate data that our users collect. if visual3d does not import your formatted files, contact support@c-motion.com and request that we implement your format. we recognize that the first task to analyze your data is to be able to load the files, so we try hard to make sure that users have their data.+===== Supported Formats =====
  
-ascii files that can be imported.+There a number of ASCII file formats that are commonly used within the biomechanics community that Visual3D can import.
  
-users that create their own custom file formats may be able to adapt their own file format fairly simply. if a user has an ascii file format that visual3d does not currently import, please contact support@c-motion.com and we will either create a file importer for you, or provide you with an sdk to create your own visual3d plugin.+==== Visual3D ASCII Format ====
  
-a universal ascii file converter may be downloaded from the [[https://www.c-motion.com/products/free-downloads/|c-motion free downloads]] page. documentation for the ascii file converter may be found on the [[index.php?title=file_converter&action=edit&redlink=1|file converter]] wiki page.+The [[visual3d:documentation:definitions:file_formats:visual3d_ascii_format|Visual3D ASCII Format]] is the preferred format for importing and exporting signals. Visual3D exports data into several file formats, this is the simplest and default file format.
  
-==== p2d_format ====+This data file can be exported from Visual3D using [[Visual3D:Documentation:Pipeline:File_Commands:Export_Data_To_ASCII_File|Export_Data_To_ASCII_File]], imported to Visual3D using [[Visual3D:Documentation:Pipeline:File_Commands:Import_Data_From_ASCII_File|Import_Data_From_ASCII_File]], and [[#Export_Data_From_Report_Dialog|exported from the report tab]].
  
-the p2d file format was part of the origin move3d software written by tom kepple in dr. steven stanhope’s laboratory at the united states national institutes of health (nih) (http://pdb.cc.nih.gov). visual3d was the result of the technology transfer of the move3d software.+==== P2D Format ====
  
-==== visual3d_ascii_format ====+The [[visual3d:documentation:definitions:file_formats:p2d_format|P2D file format]] was part of the origin MOVE3D software written by Tom Kepple in Dr. Steven Stanhope’s laboratory at the [[https://pdb.cc.nih.gov|United States National Institutes of Health]] (NIH). Visual3D was the result of the technology transfer of the MOVE3D software.
  
-visual3d ascii file format for importing and exporting signals+==== JSON Format ====
  
-visual3d exports data into several file formats. the simplest and default file format for data export to ascii files is the following:+Signal data can be exported to [[visual3d:documentation:visual_3d_formating:json_formats|JSON format]] (Javascript Object Notation) using the [[visual3d:documentation:pipeline:file_commands:export_data_to_ascii_file|Export_Data_To_ASCII]] pipeline command. Data from a report graph can be exported in JSON format using the [[visual3d:documentation:visual_3d_formating:json_formats#report_graph_export|Export Data From Report Dialog]] option in the report tab.
  
-this data file can be exported from visual3d using the pipeline command [[visual3d:documentation:pipeline:file_commands:export_data_to_ascii_file|export_data_to_ascii_file]]+==== FSV Format ====
  
-this data file can be imported to visual3d using the pipeline command [[visual3d:documentation:pipeline:file_commands:import_data_from_ascii_file|import_data_from_ascii_file]]+The **Import_Fsv_Files** Visual3D plugin is a fairly general ASCII file format translator to C3D, that may be suitable for a variety of ASCII files. The FSV/TSV file formats were originally developed by Manfred Berger from Innovision Systems and are used by Qualisys and Innovision.
  
-report data can be exported from the report tab [[#export_data_from_report_dialog|as described here]].+===== Opening an ASCII File =====
  
-==== fsv_format ====+A Visual3D ASCII file can be opened in the Visual3D workspace directly using the FILE OPEN menu option or the FILE_OPEN command. In order for Visual3D to interpret this standalone file correctly, it is important that a signal be included specifying the time.
  
-the **import_fsv_files** visual3d plugin is a fairly general ascii file format translater to c3d, that may be suitable for a variety of ascii files. the fsv/tsv file formats were originally developed by manfred berger from innovision systems and are currently used by qualisys and innovision.+One of the constraints on the file import is that the first line of the signal column must match an open C3D file. This allows Visual3D to recognize which file to add the data to. For ANALOG and TARGET (POINT) data the following rules apply: If there are more frames of data in the ASCII file than there are in the C3D file, the ASCII signal is truncated. If there are fewer frames of data in the ASCII file than there are in the C3D file, the signal is padded with frames of data containing DATA_NOT_FOUND.
  
-==== json_format ==== +|-   |C:\ExampleData\ExampleWalk.c3d|C:\ExampleData\ExampleWalk.c3d|Filename from which the data came.\\ e.g. Filename withing the Visual3D Workspace| 
- +|-   |ANALOGTIME                    |EMG9                          |Signal Name                                                                      | 
-signal data can be exported to json format (javascript object notation) using the [[index.php?title=export_data_to_ascii&action=edit&redlink=1|export_data_to_ascii]] pipeline command. data from a report graph can be exported in json format using the [[#export_data_from_report_dialog|export data from report dialog]] option in the report tab. see also [[visual3d:documentation:visual_3d_formating:json_formats|json formats]]. +|-   |FRAME_NUMBERS                 |ANALOG                        |Signal Type                                                                      | 
- +|-   |ORIGINAL                      |ORIGINAL                      |Signal Folder (e.g. ORIGINAL, PROCESSED, etc.)                                   | 
-==== kinemetrix ==== +|ITEM|0                             |X                             |Component. (ANALOG signals have channel 0 or channel X                           |
- +
-the import_kinemetrix_files visual3d plugin is an ascii file format translator to c3d. these files are produced by kinemetrics. this is a preliminary importer because we had only one example file to work with. ;-) +
- +
-===== opening a text file ===== +
- +
-a visual3d ascii file can be opened in the visual3d workspace directly using the file open menu option or the file_open command. +
- +
-in order for visual3d to interpret this standalone file correctly, it is important that a signal be included specifying the time. +
- +
-|-   |c:\exampledata\examplewalk.c3d|c:\exampledata\examplewalk.c3d|filename from which the data came.\\ e.g. filename withing the visual3d workspace| +
-|-   |analogtime                    |emg9                          |signal name                                                                      | +
-|-   |frame_numbers                 |analog                        |signal type                                                                      | +
-|-   |original                      |original                      |signal folder (e.g. original, processed, etc.)                                   | +
-|item|0                             |x                             |component. (analog signals have channel 0 or channel x                           |+
 |1   |0.01                          |23.0                          |-                                                                                | |1   |0.01                          |23.0                          |-                                                                                |
 |2   |0.02                          |22.5                          |-                                                                                | |2   |0.02                          |22.5                          |-                                                                                |
Line 58: Line 44:
 |5   |0.05                          |21.0                          |-                                                                                | |5   |0.05                          |21.0                          |-                                                                                |
  
-===== importing data from an ascii file =====+==== Working with DERIVED Data ====
  
-visual3d currently imports signals from an ascii file.+For DERIVED signals all rows are added to the data file within Visual3D without truncation or padding. This is partly because DERIVED signals cannot be exported to the C3D file at this point, so there is no conflict with the C3D file format.
  
-[[visual3d:documentation:pipeline:file_commands:import_data_from_ascii_file|import_data_from_ascii_file]] +===== Exporting Signals to an ASCII File =====
-**/file_name=**c:\exampledata\test command input signals\testinputdata.txt\\+
  
-**;** +There are several methods for exporting data from Visual3D's workspace into an ASCII file.
-visual3d allows the importing of data to a c3d file from an ascii file. see the description of the default ascii file format for visual3d.+
  
-one of the constraints on the file import is that the first line of the signal column must match an open c3d file. this allows visual3d to recognize which file to add the data to. for analog and target (point) data the following rules apply: if there are more frames of data in the ascii file than there are in the c3d file, the ascii signal is truncated. if there are fewer frames of data in the ascii file than there are in the c3d file, the signal is padded with frames of data containing data_not_found. note: for derived signals all rows are added to the data file within visual3d without truncation or padding. this is partly because derived signals cannot be exported to the c3d file at this point, so there is no conflict with the c3d file format.+==== Via the Data Tree ====
  
-==== import ascii signals adds the signals to the derived folder in the data tree ====+{{:DataTreeExportASCII.gif}}
  
-i would like these signals added to the analog folder because i would like to export the c3d file with all of the data combined.==== there are two flavours of importing signals from an ascii file. the first uses the import ascii signals command in the pipeline. this is a legacy command that is used to import signals that have been processed by an external executable (e.g. matlab). these data are always imported as derived signals. the second uses custom import commands to merge the analgo signals with the motion capture signals. there are many varieties of file formats that can be imported, but ascii files are pretty fragile (meaning they can cause system crashes quite easily). if you have signals that you need merged, please contact support@c-motion.com to confirm that your files can be imported. if not, we usually write new filters for importing data at no cost to our customers.+  - Select one of the signals in the data tree using a click of the Left Mouse Button. 
 +  - A dialog appears that contains two tabs. One tab is a graph of the signal, the other tab is a list of the data values. 
 +  - Selecting the Export ASCII button causes a browse window to appear to save the data to a Visual3D ASCII formatted data file.
  
-===== export signals to an ascii file using data tree =====+==== Via Pipeline Command ====
  
-datatreeexportascii.gif\\ +The Visual3D pipeline command [[Visual3D:Documentation:Pipeline:File_Commands:Export_Data_To_ASCII_File|Export_Data_To_ASCII_File]] exports data to one of 2 ASCII-formatted data files: 
-select one of the signals in the data tree using a click of the left mouse button. a dialog appears that contains two tabs. one tab is a graph of the signal, the other tab is a list of the data values.+  - Visual3D ASCII; and 
 +  - P2D.
  
-selecting the export ascii button causes a browse window to appear to save the data to a visual3d ascii formatted data file.+The following dialog appears when the Export_Data_To_ASCII_File command is edited within the [[visual3d:tutorials:pipeline:advanced_pipeline_commands#pipeline_editor|Pipeline Editor Workshop]].
  
-=== pipeline command for exporting signals to an ascii file ===+{{:exportascii.png}}
  
-the visual3d pipeline command exports ascii data to one of 2 formatted data files (visual3d default and p2d). 
  
-for example:+==== From a Report Dialog ====
  
-|**[[visual3d:documentation:pipeline:file_commands:export_data_to_ascii_file|export_data_to_ascii_file]]**|                                                                                                                                                  | +Data can be exported directly from a [[visual3d:documentation:reports:reports_overview|Report graph]] to an ASCII-formatted text file. 
-|/signal_types=analog                                                                                     |signal type                                                                                                                                       | +  - Select one of the graphs in the edit report dialog. A button will appear below the graph list box titled ”Export Selected”. 
-|! /signal_folder=original                                                                                |signal folder                                                                                                                                     | +  - Select this button to pop up a dialog for exporting the data from the graph to an ASCII file, either: 
-|/signal_names=emg8                                                                                       |signal names                                                                                                                                      | +    - a Visual3D ASCII formatted file; or 
-|/file_name=c:\demo files\example1\test.txt                                                               |the filename (including path) for the exported data                                                                                               | +    - a P2D formatted file. 
-|! /signal_components=                                                                                    |signal component. this is a legacy parameter, if using version 5 or later, please use component_sequence.                                         | +  - The options exist to save the raw data (e.g. frame by frame) or to save time normalized data (e.g. a specified number of frames) using the properties of the graph template (e.g. start frame and end frame).
-|/component_sequence=x                                                                                    |signal component                                                                                                                                  | +
-|! /signal_precision=                                                                                     |indicates the number of decimal places                                                                                                            | +
-|! /start_label=                                                                                          |event label indicating the first frame of data to be exported. this is a legacy parameter, if using version 4 or later, please use event_sequence.| +
-|! /end_label=                                                                                            |event label indicating the last frame of data to be exported. this is a legacy parameter, if using version 4 or later, please use event_sequence. | +
-|! /event_sequence=                                                                                       |event sequence the signals should be exported between (ex. lhs+lhs,rhs+rhs)                                                                       | +
-|! /exclude_events=                                                                                       |if an event sequence contains one of the events listed in this parameter (ex. bad,bad) the event sequence will not be exported.                   | +
-|! /use_point_rate=false                                                                                  |analog signals can be exported at either the analog rate or the point rate                                                                        | +
-|! /normalize_data=false                                                                                  |option to time normalize the data                                                                                                                 | +
-|! /normalize_points=101                                                                                  |number of output points from the time normalization                                                                                               | +
-|! /export_mean_and_std_dev=false                                                                         |option to export the mean and standard deviation                                                                                                  | +
-|! /use_p2d_format=false                                                                                  |see the description of p2d files in the documentation.                                                                                            | +
-|! /use_xml_format=false                                                                                  |                                                                                                                                                  | +
-|! /use_json_format=false                                                                                 |                                                                                                                                                  | +
-|! /use_short_filename=false                                                                              |the file path for each c3d file will not be exported when set to true                                                                             | +
-|! /export_empty_signals=false                                                                            |                                                                                                                                                  | +
-|! /export_without_header=false                                                                           |the headers (filename, signal type, signal folder, signal name, signal component) will not be exported when set to true.                          | +
-|**;**                                                                                                    |                                                                                                                                                  |+
  
-the following dialog appears when the export_data_to_ascii_file command has been added to the pipeline and the user double-clicks with the left mouse button on the command.+The picture below shows a highlighted graph and selecting a [[Visual3D:Documentation:Visual_3D_Formating:JSON_Formats|JSON output format]].
  
-exportascii.png+{{:exportreport.png}}
  
-\\+===== Exporting 6 Degree of Freedom Data =====
  
 +It is possible to export [[visual3d:documentation:kinematics_and_kinetics:six_degrees_of_freedom|6 degree of freedom]] pose data to an ASCII-format file as either an ORIGIN and QUATERNION or as an ORIGIN and 3x3 ROTATION MATRIX.
  
-===== export data from report dialog =====+This example file contains the ORIGIN and ROTATION matrix for the [[Visual3D:Documentation:Modeling:Segments:Segment_Overview#Default_Segment_Names|RSK segment]] at the first 5 frames of data. Note that the elements are TAB delimited.
  
-select one of the graphs in the edit report dialog. a button will appear below the graph list box titled ”export selected”. selecting this button will pop up a dialog for exporting the data from the graph to an ascii file; either a visual3d ascii formatted file or a p2d formatted file. the options exist to save the raw data (e.g. frame by frame) or to save time normalized data (e.g. a specified number of frames) using the properties of the graph template (e.g. start frame and end frame). +|    |c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d| 
- +|    |ORIGIN            |ORIGIN            |ORIGIN            |ROTATION          |ROTATION          |ROTATION          |ROTATION          |ROTATION          |ROTATION          |ROTATION          |ROTATION          |ROTATION          | 
-the picture below shows a highlighted graph and selecting a [[visual3d:documentation:visual_3d_formating:json_formats|json output format]]. +|    |KINETIC_KINEMATIC |KINETIC_KINEMATIC |KINETIC_KINEMATIC |KINETIC_KINEMATIC |KINETIC_KINEMATIC |KINETIC_KINEMATIC |KINETIC_KINEMATIC |KINETIC_KINEMATIC |KINETIC_KINEMATIC |KINETIC_KINEMATIC |KINETIC_KINEMATIC |KINETIC_KINEMATIC | 
- +|    |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               | 
-exportreport.png +|ITEM|X                 |Y                 |Z                 |0                 |1                 |2                 |3                 |4                 |5                 |6                 |7                 |8                 |
- +
-===== export 6 degree of freedom data ===== +
- +
-it is possible to export 6 degree of freedom data to an ascii format as either an origin and quaternion or as an origin and 3x3 rotation matrix. +
- +
-exporting the position and orientation of segment rft as an origin and quaternion +
- +
-\\ +
- +
- +
-[[visual3d:documentation:pipeline:file_commands:export_data_to_ascii_file|export_data_to_ascii_file]] +
-! /file_name= +
-/signal_types=frame_numbers+link_model_based+link_model_based +
-/signal_names=time+origin+quaternion +
-/signal_folder=original+rft+rft +
-! /start_label= +
-! /end_label= +
-! /use_point_rate=false +
-! /normalize_data=false +
-! /normalize_points=101 +
-! /export_mean_and_std_dev=false +
-! /use_p2d_format=false +
-; +
- +
-\\ +
-exporting the position and orientation of segment rft as an origin and rotation matrix. visual3d exports the following rotation matrix +
- +
-[[visual3d:documentation:kinematics_and_kinetics:six_degrees_of_freedom#6_dof_tracking|[ xyz local ] = [r2] [xyz global]]] +
- +
-\\ +
- +
- +
-[[visual3d:documentation:pipeline:file_commands:export_data_to_ascii_file|export_data_to_ascii_file]] +
-! /file_name= +
-/signal_types=frame_numbers+link_model_based+link_model_based +
-/signal_names=time+origin+rotation +
-/signal_folder=original+rft+rft +
-! /start_label= +
-! /end_label= +
-! /use_point_rate=false +
-! /normalize_data=false +
-! /normalize_points=101 +
-! /export_mean_and_std_dev=false +
-! /use_p2d_format=false +
-; +
- +
-==== 6 dof ascii format ==== +
- +
-this example file contains the origin and rotation matrix for the [[visual3d:documentation:modeling:segments:segment_overview#default_segment_names|rsk segment]] at the first 5 frames of data. note that the elements are tab delimited. +
- +
-|    |c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d| +
-|    |origin            |origin            |origin            |rotation          |rotation          |rotation          |rotation          |rotation          |rotation          |rotation          |rotation          |rotation          | +
-|    |kinetic_kinematic |kinetic_kinematic |kinetic_kinematic |kinetic_kinematic |kinetic_kinematic |kinetic_kinematic |kinetic_kinematic |kinetic_kinematic |kinetic_kinematic |kinetic_kinematic |kinetic_kinematic |kinetic_kinematic | +
-|    |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               | +
-|item|x                 |y                 |z                 |0                 |1                 |2                 |3                 |4                 |5                 |6                 |7                 |8                 |+
 |1   |0.37046           |0.00863           |0.40545           |0.96567           |0.21640           |-0.14375          |-0.24416          |0.56693           |-0.78675          |-0.08876          |0.79483           |0.60030           | |1   |0.37046           |0.00863           |0.40545           |0.96567           |0.21640           |-0.14375          |-0.24416          |0.56693           |-0.78675          |-0.08876          |0.79483           |0.60030           |
 |2   |0.35441           |0.05135           |0.41706           |0.97954           |0.19208           |-0.05999          |-0.16101          |0.56933           |-0.80619          |-0.12070          |0.79935           |0.58861           | |2   |0.35441           |0.05135           |0.41706           |0.97954           |0.19208           |-0.05999          |-0.16101          |0.56933           |-0.80619          |-0.12070          |0.79935           |0.58861           |
Line 186: Line 101:
 |5   |0.35359           |0.14253           |0.46174           |0.99978           |0.01001           |0.01839           |0.00611           |0.70059           |-0.71353          |-0.02002          |0.71349           |0.70038           | |5   |0.35359           |0.14253           |0.46174           |0.99978           |0.01001           |0.01839           |0.00611           |0.70059           |-0.71353          |-0.02002          |0.71349           |0.70038           |
  
-or in the following format+Or in the following format
  
 > >
  
-|    |c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d|c:\data\mvc002.c3d| +|    |c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d|c:\Data\mvc002.c3d| 
-|    |origin            |origin            |origin            |rotation          |rotation          |rotation          |rotation          |rotation          |rotation          |rotation          |rotation          |rotation          | +|    |ORIGIN            |ORIGIN            |ORIGIN            |ROTATION          |ROTATION          |ROTATION          |ROTATION          |ROTATION          |ROTATION          |ROTATION          |ROTATION          |ROTATION          | 
-|    |link_model_based  |link_model_based  |link_model_based  |link_model_based  |link_model_based  |link_model_based  |link_model_based  |link_model_based  |link_model_based  |                  |                  |                  | +|    |LINK_MODEL_BASED  |LINK_MODEL_BASED  |LINK_MODEL_BASED  |LINK_MODEL_BASED  |LINK_MODEL_BASED  |LINK_MODEL_BASED  |LINK_MODEL_BASED  |LINK_MODEL_BASED  |LINK_MODEL_BASED  |                  |                  |                  | 
-|    |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               |lsk               | +|    |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               |LSK               | 
-|item|x                 |y                 |z                 |0                 |1                 |2                 |3                 |4                 |5                 |6                 |7                 |8                 |+|ITEM|X                 |Y                 |Z                 |0                 |1                 |2                 |3                 |4                 |5                 |6                 |7                 |8                 |
 |1   |0.37046           |0.00863           |0.40545           |0.96567           |0.21640           |-0.14375          |-0.24416          |0.56693           |-0.78675          |-0.08876          |0.79483           |0.60030           | |1   |0.37046           |0.00863           |0.40545           |0.96567           |0.21640           |-0.14375          |-0.24416          |0.56693           |-0.78675          |-0.08876          |0.79483           |0.60030           |
 |2   |0.35441           |0.05135           |0.41706           |0.97954           |0.19208           |-0.05999          |-0.16101          |0.56933           |-0.80619          |-0.12070          |0.79935           |0.58861           | |2   |0.35441           |0.05135           |0.41706           |0.97954           |0.19208           |-0.05999          |-0.16101          |0.56933           |-0.80619          |-0.12070          |0.79935           |0.58861           |
Line 201: Line 116:
 |5   |0.35359           |0.14253           |0.46174           |0.99978           |0.01001           |0.01839           |0.00611           |0.70059           |-0.71353          |-0.02002          |0.71349           |0.70038           | |5   |0.35359           |0.14253           |0.46174           |0.99978           |0.01001           |0.01839           |0.00611           |0.70059           |-0.71353          |-0.02002          |0.71349           |0.70038           |
  
-===== other ascii formats =====+==== Example: Export as ORIGIN and QUATERNION ====
  
-the following ascii commands read slightly different flavors of ascii signals. the names are derived from the customers that have requested the importer. if c-motion provided you with information on the command, you can make the call using the command name you were givin; even though you may not see the command listed in the pipeline.+The command below will export the position and orientation of segment RFT as an ORIGIN and Quaternion.
  
-\\ +<code> 
-**import_frappier_analog_signals**\\ +Export_Data_To_ASCII_File 
-**import_ntnu_analogsignals**\\ +! /FILE_NAME= 
-**import_cresswell_analogsignals**\\ +/SIGNAL_TYPES=FRAME_NUMBERS+LINK_MODEL_BASED+LINK_MODEL_BASED 
-**import_natick_analogsignals**+/SIGNAL_NAMES=TIME+ORIGIN+QUATERNION 
 +/SIGNAL_FOLDER=ORIGINAL+RFT+RFT 
 +! /START_LABEL= 
 +! /END_LABEL= 
 +! /USE_POINT_RATE=FALSE 
 +! /NORMALIZE_DATA=FALSE 
 +! /NORMALIZE_POINTS=101 
 +! /EXPORT_MEAN_AND_STD_DEV=FALSE 
 +! /USE_P2D_FORMAT=FALSE 
 +; 
 +</code>
  
-\\ +==== Example: Export as ORIGIN and ROTATION ====
-this command was written for frappier acceleration products but has been modified to accomodate many different flavors of ascii files from our customers. the command has several aliases as you can see from the list. as of visual3d version 3.20, all of these commands are hidden in the pipeline, until we have a convenient way in our licensing scheme to make it visible only to a specific user with a specific name. each command is slightly different, but the differences are recognized automatically. this may not alway be the case, so we have given each lab their own command name, that would allow us to modify the processing if necesary.+
  
-the name of the ascii file containing the analog signals is expected to have the same name as the c3d file; eg. trial1.c3d and trial1.anc+The command below will export the position and orientation of segment RFT as an ORIGIN and ROTATION matrix. 
  
-the basic format of the file is: +<code> 
- +Export_Data_To_ASCII_File 
-\\ +! /FILE_NAME= 
- +/SIGNAL_TYPES=FRAME_NUMBERS+LINK_MODEL_BASED+LINK_MODEL_BASED 
- +/SIGNAL_NAMES=TIME+ORIGIN+ROTATION 
-|file_type: |analog     |          |    |    |    |    | +/SIGNAL_FOLDER=ORIGINAL+RFT+RFT 
-|board_type:|pci-mio-64e|          |    |    |    |    | +! /START_LABEL= 
-|trial_name:|test       |#channels:|6   |    |    |    | +! /END_LABEL= 
-|name       |fx1        |fy1       |fz1 |mx1 |my1 |mz1 | +! /USE_POINT_RATE=FALSE 
-|rate       |1000       |1000      |1000|1000|1000|1000| +! /NORMALIZE_DATA=FALSE 
-|0.000      |1003       |997       |1009|1009|1006|1023| +! /NORMALIZE_POINTS=101 
-|0.001      |1003       |997       |1009|1009|1006|1023| +! /EXPORT_MEAN_AND_STD_DEV=FALSE 
- +! /USE_P2D_FORMAT=FALSE 
-[[+; 
 +</code>
  
-===== example =====+**NOTE**: Visual3D exports the following rotation matrix:
  
-specifying a root folder and a list of subject folders. each subject folder contains a set of c3d files. for example, +<code> 
-subject1 +[ XYZ local ] = [R2] [XYZ global] 
-trial16.c3d +</code>
-subject2 +
-trial16.c3d +
-subject3 +
-trial16.c3d +
-and so on ... +
-open each c3d file and export a signal to a filename whose prefix is the same as the c3d file.+
  
-}}}}}} 
visual3d/documentation/definitions/file_formats/ascii_format.1718801248.txt.gz · Last modified: by sgranger