visual3d:documentation:pipeline:file_commands:file_names
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| visual3d:documentation:pipeline:file_commands:file_names [2024/06/18 13:30] – sgranger | visual3d:documentation:pipeline:file_commands:file_names [2024/07/17 15:45] (current) – created sgranger | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== Identifying files in the Workspace | + | ====== File Names ====== |
| + | |||
| + | === 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 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. | ||
| Line 5: | Line 7: | ||
| 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. | 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/ | + | === Display filenames with/ |
| To identify files uniquely, Visual3D uses the full path to the file. 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. | To identify files uniquely, Visual3D uses the full path to the file. 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}}\\ | + | {{:longFilenames1.png}}\\ |
| - | {{longFilenames2.png}} | + | {{:longFilenames2.png}} |
| - | ==== Identifying Files using a Wildcard | + | === Identifying Files using a Wildcard === |
| Visual3D uses the asterisk (*) as a wild card for filenames. Multiple wild cards can be used. | Visual3D uses the asterisk (*) as a wild card for filenames. Multiple wild cards can be used. | ||
| Line 30: | Line 32: | ||
| 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' | 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' | ||
| - | ==== Errors caused by forgetting to include the path with the filename | + | === 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 " | Visual3D uses the full pathname to identify files in the Workspace; for example, this allows multiple versions of " | ||
visual3d/documentation/pipeline/file_commands/file_names.1718717443.txt.gz · Last modified: 2024/06/18 13:30 by sgranger