Differences

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

--- visual3d:documentation:pipeline:general_information:pipeline_introduction [2024/06/26 20:26] – created sgranger
+++ visual3d:documentation:pipeline:general_information:pipeline_introduction [2024/07/17 15:45] (current) – created sgranger
@@ Line 1: / Line 1: @@
-====== Pipeline_Introduction ======
+====== Pipeline Introduction ======
 **THIS PAGE IS UNDER CONSTRUCTION! So it's still being developed, and is a combination of the following wiki pages:**
@@ Line 21: / Line 21: @@
 ===== Pipeline Workshop =====
-You can open the pipeline workshop by going to Pipeline -> Workshop or clicking on the button on the [[Visual3D:Overview:Toolbar#Visual3D_Pipeline|toolbar]].
+You can open the pipeline workshop by going to Pipeline -> Workshop or clicking on the button on the [[Visual3D:Getting_Started:Toolbar#Visual3D_Pipeline|toolbar]].
 **The pipeline workshop has three sections:**
-|{{PipelineWorkshop.png}}  |* **Left:**\\   * List of available commands\\ * **Center:**\\   * Main Pipeline\\   * List of commands being used\\ * **Right:**\\   * Preview of selected command  |
+|{{:PipelineWorkshop.png}}  |* **Left:**\\   * List of available commands\\ * **Center:**\\   * Main Pipeline\\   * List of commands being used\\ * **Right:**\\   * Preview of selected command  |
 Commands can be moved into the Main Pipeline by using the Add **>>** button. Command can be reordered in any sequence using the up/down arrows. Pipelines can be saved to be used again so processing is consistent between subjects.
@@ Line 31: / Line 31: @@
 ==== Editing a Command ====
-|{{PipelineWorkshop_EditGUI.png}}      |When you highlight a command in the **Main Pipeline** and click **Edit** a dialog will appear to edit the command.    |
+|{{:PipelineWorkshop_EditGUI.png}}      |When you highlight a command in the **Main Pipeline** and click **Edit** a dialog will appear to edit the command.    |
-|{{PipelineWorkshop_TextEdit.png}}  |When you highlight a command in the **Main Pipeline** and click **Text** a text box will appear to edit the command.  |
+|{{:PipelineWorkshop_TextEdit.png}}  |When you highlight a command in the **Main Pipeline** and click **Text** a text box will appear to edit the command.  |
 ===== Pipeline Command =====
@@ Line 92: / Line 92: @@
 ===== Expressions =====
-The [[Visual3D:Documentation:Pipeline:Expressions:Overview|Evaluate_Expression]] command allows you to type out an expression using mathematical operators. It's probably the most powerful pipeline command in Visual3D, but it takes time to learn the syntax. The full syntax available within [[Visual3D:Documentation:Pipeline:Expressions:Overview|Evaluate_Expression]] is described [[Visual3D:Documentation:Pipeline:Expressions:Overview|here]].
+The [[Visual3D:Documentation:Pipeline:Expressions:Expressions_Overview|Evaluate_Expression]] command allows you to type out an expression using mathematical operators. It's probably the most powerful pipeline command in Visual3D, but it takes time to learn the syntax. The full syntax available within [[Visual3D:Documentation:Pipeline:Expressions:Expressions_Overview|Evaluate_Expression]] is described [[Visual3D:Documentation:Pipeline:Expressions:Expressions_Overview|here]].
-Many commands have pipeline parameters that accept expressions using the same syntax as the [[Visual3D:Documentation:Pipeline:Expressions:Overview|Evaluate_Expression]] command.
+Many commands have pipeline parameters that accept expressions using the same syntax as the [[Visual3D:Documentation:Pipeline:Expressions:Expressions_Overview|Evaluate_Expression]] command.
 ==== Signal Names ====
@@ Line 100: / Line 100: @@
 === Signal Names as Expressions ===
-**In an [[Visual3D:Documentation:Pipeline:Expressions:Overview|expression]], a signal is referenced by Signal Type, Signal Folder, Signal Name, and component.**
+**In an [[Visual3D:Documentation:Pipeline:Expressions:Expressions_Overview|expression]], a signal is referenced by Signal Type, Signal Folder, Signal Name, and component.**
 **Signals are referenced by SIGNAL_TYPE::SIGNAL_FOLDER::SIGNAL_NAME**
-|**This signal would be referenced DERIVED::INVERSE_KINEMATICS::LFT_Rot1**\\ \\ If you look at the data tree in Signals and Events, you will see the highest level folders are the Signal Type. The Type is defined in Visual3D, and you cannot create your own Type. Example: DERIVED\\ \\ The sub folder is the Signal Folder. For most Types you can defined your own folder names (as opposed to the default, ex. Event_Label can only have the Folder ORIGINAL). Example: INVERSE_KINEMATICS\\ \\ Each folder contains signals, they're considered the Signal Name. Example: LFT_Rot1|{{DataTree_Pipeline.png}}|
+|**This signal would be referenced DERIVED::INVERSE_KINEMATICS::LFT_Rot1**\\ \\ If you look at the data tree in Signals and Events, you will see the highest level folders are the Signal Type. The Type is defined in Visual3D, and you cannot create your own Type. Example: DERIVED\\ \\ The sub folder is the Signal Folder. For most Types you can defined your own folder names (as opposed to the default, ex. Event_Label can only have the Folder ORIGINAL). Example: INVERSE_KINEMATICS\\ \\ Each folder contains signals, they're considered the Signal Name. Example: LFT_Rot1|{{:DataTree_Pipeline.png}}|
 **Important:** You will notice there are two colons in between the type, folder and signal name. Two colons are also used to represent a pipeline parameter, but they mean different things.