visual3d:documentation:definitions:file_formats:visual3d_ascii_format
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:documentation:definitions:file_formats:visual3d_ascii_format [2025/02/07 18:47] – Clean up page. wikisysop | visual3d:documentation:definitions:file_formats:visual3d_ascii_format [2025/03/18 19:00] (current) – [Component String] Organized information into a table. wikisysop | ||
---|---|---|---|
Line 37: | Line 37: | ||
+ | ===== 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 [[visual3d: | ||
+ | |||
+ | 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. | ||
+ | |||
+ | Here are the current decisions. | ||
+ | |||
+ | ^ Signal Type ^ Returned Component Strings ^ | ||
+ | | [[visual3d: | ||
+ | | [[visual3d: | ||
+ | | [[visual3d: | ||
+ | | [[visual3d: | ||
+ | | [[visual3d: | ||
+ | | [[visual3d: | ||
+ | | [[visual3d: | ||
+ | | [[visual3d: | ||
+ | | [[visual3d: | ||
+ | | [[visual3d: | ||
+ | | [[visual3d: | ||
+ | | [[visual3d: | ||
+ | |||
+ | The exception is that Visual3D allows a character to be added to a number. For example C0 instead of 0 | ||
===== Signal Units ===== | ===== Signal Units ===== | ||
visual3d/documentation/definitions/file_formats/visual3d_ascii_format.1738954067.txt.gz · Last modified: 2025/02/07 18:47 by wikisysop