Differences

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

--- visual3d:documentation:definitions:file_formats:ascii_format [2025/01/17 16:20] – [ASCII Format] wikisysop
+++ visual3d:documentation:definitions:file_formats:ascii_format [2025/05/20 20:53] (current) – WORK IN PROGRESS. 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.
+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.
-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.
+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.
-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.
+===== Supported Formats =====
-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.
+There a number of ASCII file formats that are commonly used within the biomechanics community that Visual3D can import.
-ASCII files that can be imported.
+==== P2D_Format ====
-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.
-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 ===
 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: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:
-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]]
-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]]
-Report data can be exported from the report tab [[#Export_Data_From_Report_Dialog|as described here]].
-=== 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.
+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.
+  * 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]]
+  * 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]]
+  * Report data can be exported from the report tab [[#Export_Data_From_Report_Dialog|as described here]].
-=== JSON_Format ===
+==== FSV_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]].
+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.
-=== Kinemetrix ===
+==== JSON_Format ====
-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. ;-)
+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.
-==== 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.