Differences

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

--- visual3d:documentation:pipeline:file_commands:file_names [2024/06/19 13:37] – removed sgranger
+++ visual3d:documentation:pipeline:file_commands:file_names [2025/09/18 21:57] (current) – Cleaned up header levels. wikisysop
@@ Line 1: / Line 1: @@
+====== File Names ======
+File names are used throughout Visual3D to specify which files are being considered and where these files exist on disk.
+===== Identifying files in the Workspace =====
+Visual3D identifies files using the full path for the filename. This allows users to use the same filenames for the data trials, distinguishing between files by the folder in which the files are stored.
+Visual3D refers to the filename as the owner of the data associated with that file. When a file is the only ACTIVE_FILE in the Workspace the data tree in the left pane of the Event and Signals Tab contains lists (and provides access to) all of the signals associated with that file.
+==== Display filenames with/without the full path ====
+Visual3D uses full file paths to uniquely identify files. At times this can be a nuisance because very long paths don't fit the graphical interface well. Under the view menu option there is a selection to turn off the long pathnames in the interface.
+{{:longFilenames1.png}}
+{{:longFilenames2.png}}
+===== Identifying Files using a Wildcard =====
+Visual3D uses the asterisk (*) as a wild card for filenames. Multiple wild cards can be used. For example, the file path: c:\Visual3D\Data\subject_walk_001.c3d
+could be represented as:
+  * Data\*1.c3d
+  * walk*.c3d
+Most pipeline commands allow the use of wildcards for a movement file or a calibration file. Our intention is for all commands to allow this, so if you find an instance where a wildcard doesn't seem to work, please contact support@has-motion.ca so that we can update the command.
+===== Errors caused by forgetting to include the path with the filename =====
+Visual3D uses the full pathname to identify files in the Workspace; for example, this allows multiple versions of "trial1.c3d" because presumably they have unique paths.
+The following command does not include the path to the filename.
+<code>
+Assign_Tags_To_Files
+/MOTION_FILE_NAMES=file.c3d
+/TAGS= POST
+;
+</code>
+If the full path is not specified, you will likely see the error message: **ERROR! - FILE_NAME hall0012.c3d must be an open motion file.**