Differences

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

--- visual3d:documentation:pipeline:pipeline_commands:conditional_statement [2024/06/18 13:33] – sgranger
+++ visual3d:documentation:pipeline:pipeline_commands:conditional_statement [2026/02/04 16:38] (current) – wikisysop
@@ Line 1: / Line 1: @@
-\\
+====== Conditional Statement ======
 This command was modelled after the [[Visual3D:Documentation:Pipeline:Pipeline_Commands:For_Each_and_End_For_Each|For_Each]] command in the sense that there is a start (Conditional_Statement) and an ending event (Conditional_Statement_End).
-When the pipeline comes to an Conditional_Statement command, it will evaluate the expression using the same syntax as the [[Visual3D:Documentation:Pipeline:Expressions:Overview|Evaluate_Expression]] command. If the expression is TRUE (returns any value other than zero), all of the commands between the Conditional_Statement and Conditional_Statement_End commands will be executed. If the expression is FALSE (returns a zero), all the commands that are between the Conditional_Statement and Conditional_Statement_End commands will be skipped.
+When the pipeline comes to an Conditional_Statement command, it will evaluate the expression using the same syntax as the [[Visual3D:Documentation:Pipeline:Expressions:Expressions_Overview|Evaluate_Expression]] command. If the expression is TRUE (returns any value other than zero), all of the commands between the Conditional_Statement and Conditional_Statement_End commands will be executed. If the expression is FALSE (returns a zero), all the commands that are between the Conditional_Statement and Conditional_Statement_End commands will be skipped.
-The ITERATION_PARAMETER_NAME is used to distinguish between different Conditional_Statement commands so that Conditional_Statement and Conditional_Statement_End commands can be unambiguously associated with each other.
-**NOTE:** If there is more than one active file then the Conditional_Statement command will be skipped. This is because the expression might be TRUE for some files and FALSE for others, leaving Visual3D in an ambiguous place.
-**NOTE:** This command was previously called the Expression_Loop. Scripts referring to this old command name will still work.
-===== Syntax =====
-==== Conditional_Statement ====
+==== Pipeline Command ====
+The **Conditional Statement** command can be found in the Pipeline Workshop within the Pipeline Control folder as so:
+<code>
+Conditional_Statement
 /ITERATION_PARAMETER_NAME=
-/[[Visual3D:Documentation:Pipeline:Expressions:Overview|EXPRESSION]]=
+! /EXPRESSION=
-**;**
+! /AS_INTEGER=TRUE
-==== Conditional_Statement_End ====
+;
+Conditional_Statement_End
 /ITERATION_PARAMETER_NAME=
-**;**
+;
-===== Pipeline Example =====
+</code>
+====Command Parameters====
+The following table shows the command parameters and descriptions:
+|**Parameter**   |**Description**|
+|**Iteration Parameter Name**|The name of the parameter that the conditional statement will apply to (defined before command)|
+|**Expression**|Expression for the operation to be applied to the selected signals|
+|**As Integer**|True or False: Expression value is stored as integer|
+==== Pipeline Example: Processing Walking and Running Trials ====
 This script will prompt the user to specify if walking or running trials are being processed. Based on the user's selection, different processing will be completed. In this example, the pipeline parameter TEST will be set to 1 if the condition is Walk, and set to 2 if the condition is Run.
@@ Line 79: / Line 83: @@
 </code>
+====Notes====
+The ITERATION_PARAMETER_NAME is used to distinguish between different Conditional_Statement commands so that Conditional_Statement and Conditional_Statement_End commands can be unambiguously associated with each other.
+**NOTE:** If there is more than one active file then the Conditional_Statement command will be skipped. This is because the expression might be TRUE for some files and FALSE for others, leaving Visual3D in an ambiguous place.
+**NOTE:** This command was previously called the Expression_Loop. Scripts referring to this old command name will still work.