visual3d:documentation:pipeline:general_information:signal_names
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| visual3d:documentation:pipeline:general_information:signal_names [2024/06/19 12:51] – sgranger | visual3d:documentation:pipeline:general_information:signal_names [2026/09/09 21:00] (current) – Cleaned up page. richard | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | / | + | ====== Signal Names ====== |
| - | or | + | |
| - | / | + | |
| - | the names of the signals used by the pipeline command. | + | |
| - | the + symbol | + | This is a common parameter in pipeline commands, allowing the user to specify which specific signals to be evaluated as input. Signal names are the third (bottom) level of the [[visual3d: |
| - | for example, to specify the three signals rft1, rft2, and rft3 | + | The parameter will appear in commands as / |
| - | / | + | ===== Multiple Input ===== |
| - | many commands allow signal_names to be blank | + | |
| - | / | + | The + symbol |
| - | in the cases that this is allowed, this indicates that visual3d should use all signals | + | |
| + | < | ||
| + | / | ||
| + | </ | ||
| + | ===== Empty Input ===== | ||
| + | |||
| + | Some commands allow empty input for this parameter, for example: | ||
| + | |||
| + | < | ||
| + | / | ||
| + | </ | ||
| + | |||
| + | In these cases, this indicates that Visual3D should use all signals of the specified [[Visual3D: | ||
| + | |||
| + | ===== See Also ===== | ||
| + | |||
| + | The Signal_Type parameter is often accompanied by two other parameters: | ||
| + | * [[visual3d: | ||
| + | * [[visual3d: | ||
| + | |||
| + | Together these three parameters represent the application-wide [[visual3d: | ||
visual3d/documentation/pipeline/general_information/signal_names.1718801466.txt.gz · Last modified: by sgranger
