Differences

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

--- visual3d:documentation:definitions:file_formats:visual3d_ascii_format [2025/03/18 17:45] – [Component String] wikisysop
+++ visual3d:documentation:definitions:file_formats:visual3d_ascii_format [2025/03/18 19:00] (current) – [Component String] Organized information into a table. wikisysop
@@ Line 38: / Line 38: @@
 ===== Component String =====
-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 ROTATION signal to the c3d format and to Visual3D.
+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
-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
+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.
-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.
 Here are the current decisions.
+^ Signal Type ^ Returned Component Strings ^
+| [[visual3d:documentation:c3d_signal_types:target_data_type|TARGET]] | XYZR |
+| [[visual3d:documentation:modeling:landmarks:landmarks_overview|LANDMARK]] | XYZ |
+| [[visual3d:documentation:visual3d_signal_types:force_data_type|FORCE]] | XYZ |
+| [[visual3d:documentation:visual3d_signal_types:cofp_data_type|COFP]] | XYZ |
+| [[visual3d:documentation:visual3d_signal_types:freemoment_data_type|FREEMOMENT]] | XYZ |
+| [[visual3d:documentation:visual3d_signal_types:link_model_based_data_type|LINK_MODEL_BASED]] | XYZ |
+| [[visual3d:documentation:c3d_signal_types:analog_data_type|ANALOG]] | XYZ |
+| [[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
-<code>
-Signal Types
-TARGET
-            Return XYZR
-LANDMARK:
-FORCE:
-COFP:
-FREEMOMENT:
-LINK_MODEL_BASED:
-METRIC:
-ANALOG:
-KINETIC_KINEMATIC:
-BODY
-            Return XYZ
-Now for the uncertain signals as it is not clear from any context what the component should be
-DERIVED
-METRIC
-            if (nMaxElements == 3)
-                 Return XYZ
-            else
-                 Return 0,1,2,.....
-</code>
 ===== Signal Units =====