Differences

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

--- visual3d:documentation:definitions:file_formats:visual3d_ascii_format [2024/07/17 15:45] – created sgranger
+++ visual3d:documentation:definitions:file_formats:visual3d_ascii_format [2025/03/18 19:00] (current) – [Component String] Organized information into a table. wikisysop
@@ Line 16: / Line 16: @@
 |5   |21.0                        |-                                                                                |
-\\
 The file contains data in columns. The first column is the frame number. One file may contain several signals.
 ===== Time Data =====
-Visual3D recognizes three time labels:
+Visual3D recognizes three time labels: time, analog, and derived.
+^ Time Label ^ Description ^
+| TIME | This is a column containing the time at the [[visual3d:documentation:c3d_signal_types:target_data_type|POINT rate]]. |
+| ANALOGTIME | This is a column containing the time at the [[visual3d:documentation:c3d_signal_types:analog_data_type|ANALOG rate]]. |
+| DERIVEDTIME | This is a column containing the time at a DERIVED rate. DERIVED signals can have any sampling rate that is an integer multiple of the POINT rate. Each ASCII file permits only one DERIVEDTIME signal. If there is more than one DERIVEDTIME signal, you will need to import multiple text files; one for each DERIVEDTIME.|
 An example header:
@@ Line 32: / Line 36: @@
 |1   |0.0          |0.0          |0.0          |
-\\
+===== Component String =====
-==== TIME ====
+Deciding what character to use for representing a signal component has resulted in some flip flopping over the years. The final straw in our decision was the introduction of a 4x4 [[visual3d:documentation:c3d_signal_types:rotation_data_type|ROTATION]] signal to the [[visual3d:documentation:c3d_signal_types:c3d_format|C3D format]] and to Visual3D. While X, Y, Z have been synonymous with the first 3 components of any signal, X, Y, Z are not logically the first 3 components of a ROTATION signal
-Thss is a column containing the time at POINT rate
+On the other hand, using numerical values has other controversial issues. For example, Matlab won't read a number as a string and apparently there are .m files that treat the component as a string.
-==== ANALOGTIME ====
+Here are the current decisions.
-This is a column containing the time at ANALOG rate
+^ Signal Type ^ Returned Component Strings ^
+| [[visual3d:documentation:c3d_signal_types:target_data_type|TARGET]] | XYZR |
-==== DERIVEDTIME ====
+| [[visual3d:documentation:modeling:landmarks:landmarks_overview|LANDMARK]] | XYZ |
+| [[visual3d:documentation:visual3d_signal_types:force_data_type|FORCE]] | XYZ |
-This is a column containing the time at DERIVED rate.
+| [[visual3d:documentation:visual3d_signal_types:cofp_data_type|COFP]] | XYZ |
+| [[visual3d:documentation:visual3d_signal_types:freemoment_data_type|FREEMOMENT]] | XYZ |
-DERIVED signals can have any sampling rate that is an integer multiple of the POINT rate. Each ASCII file permits only one DERIVEDTIME signal.
+| [[visual3d:documentation:visual3d_signal_types:link_model_based_data_type|LINK_MODEL_BASED]] | XYZ |
+| [[visual3d:documentation:c3d_signal_types:analog_data_type|ANALOG]] | XYZ |
-It there is more than on DERIVEDTIME signal, you will need to import multiple text files; one for each DERIVEDTIME.
+| [[visual3d:documentation:visual3d_signal_types:kinetic_kinematic_data_type|KINETIC_KINEMATIC]] | XYZ |
+| [[visual3d:documentation:visual3d_signal_types:metric_data_type|METRIC]] (3 components) | XYZ |
+| [[visual3d:documentation:visual3d_signal_types:metric_data_type|METRIC]] (others) | 0, 1, 2, ... |
+| [[visual3d:documentation:visual3d_signal_types:derived_data_type|DERIVED]] (3 components) | XYZ |
+| [[visual3d:documentation:visual3d_signal_types:derived_data_type|DERIVED]] (others) | 0, 1, 2, ... |
+The exception is that Visual3D allows a character to be added to a number. For example C0 instead of 0
 ===== Signal Units =====
 All signals are stored in MKS units.
-===== Exporting Data =====
+===== Importing and Exporting =====
+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]]. One of the constraints on the file import is that the first line of the signal column must match a C3D file in the Visual3D Workspace. This allows Visual3D to recognize which file to add the data to.
 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]]
-===== Importing Data =====
+===== Number of Analog and Point Frames =====
-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 following rules apply for ANALOG and TARGET (POINT) data:
+  * if there are more frames of data in the ASCII file than there are in the C3D file, the ASCII signal is truncated.
-==== First Row ====
+  * 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.
-One of the constraints on the file import is that the first line of the signal column must match a C3D file in the Visual3D Workspace. This allows Visual3D to recognize which file to add the data to.
-===== Number of Analog and Point frames =====
-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.