Differences

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

--- visual3d:documentation:definitions:file_formats:ascii_format [2024/06/18 13:27] – sgranger
+++ visual3d:documentation:definitions:file_formats:ascii_format [2025/01/17 16:20] (current) – [ASCII Format] wikisysop
@@ Line 1: / Line 1: @@
+====== ASCII Format ======
 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.
@@ Line 13: / Line 15: @@
 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.
-==== P2D_Format ====
+=== P2D_Format ===
-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.
+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 United States National Institutes of Health (NIH) (http://pdb.cc.nih.gov). Visual3D was the result of the technology transfer of the MOVE3D software.
-==== Visual3D_ASCII_Format ====
+=== Visual3D_ASCII_Format ===
-Visual3D ASCII file format for importing and exporting signals
+[[visual3d:documentation:definitions:file_formats:visual3d_ascii_format]] for importing and exporting signals
 Visual3D exports data into several file formats. The simplest and default file format for data export to ASCII files is the following:
@@ Line 29: / Line 31: @@
 Report data can be exported from the report tab [[#Export_Data_From_Report_Dialog|as described here]].
-==== FSV_Format ====
+=== FSV_Format ===
 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.
-==== JSON_Format ====
+=== JSON_Format ===
 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]].
-==== Kinemetrix ====
+=== Kinemetrix ===
 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 =====
+==== 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.
@@ Line 58: / Line 60: @@
 |5   |0.05                          |21.0                          |-                                                                                |
-===== Importing data from an ASCII file =====
+==== Importing data from an ASCII file ====
 Visual3D currently imports signals from an ASCII file.
@@ Line 70: / Line 72: @@
 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.
-==== Import ASCII signals adds the signals to the DERIVED folder in the data tree ====
+=== Import ASCII signals adds the signals to the DERIVED folder in the data tree ===
 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.
-===== Export Signals to an ASCII file Using Data Tree =====
+==== Export Signals to an ASCII file Using Data Tree ====
-{{DataTreeExportASCII.gif{{/images/a/a5/DataTreeExportASCII.gif?617x402}}\\
+{{:DataTreeExportASCII.gif}}\\
 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.
-=== Pipeline Command for Exporting Signals to an ASCII File ===
+== Pipeline Command for Exporting Signals to an ASCII File ==
 The Visual3D pipeline command exports ASCII data to one of 2 formatted data files (Visual3D default and P2D).
@@ Line 113: / Line 115: @@
 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.
-{{exportascii.png}}
+{{:exportascii.png}}
 \\
-===== Export Data From Report Dialog =====
+==== Export Data From Report Dialog ====
 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).
@@ Line 124: / Line 126: @@
 The picture below shows a highlighted graph and selecting a [[Visual3D:Documentation:Visual_3D_Formating:JSON_Formats|JSON output format]].
-{{exportreport.png{{/images/7/7d/exportreport.png?643x354}}
+{{:exportreport.png}}
-===== Export 6 degree of freedom data =====
+==== 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.
@@ Line 171: / Line 173: @@
 ;
-==== 6 DOF ASCII FORMAT ====
+=== 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.
@@ Line 201: / Line 203: @@
 |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 =====
+==== Other ASCII Formats ====
 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.
@@ Line 231: / Line 233: @@
 [[
-===== Example =====
+==== Example ====
 Specifying a ROOT FOLDER and a list of subject folders. Each subject folder contains a set of C3D files. For example,