visual3d:documentation:pipeline:pipeline_commands:pipeline_control_commands
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:documentation:pipeline:pipeline_commands:pipeline_control_commands [2024/06/19 12:52] – sgranger | visual3d:documentation:pipeline:pipeline_commands:pipeline_control_commands [2024/09/03 13:26] (current) – wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | an important feature of the pipeline is the ability to create and use pipeline parameters. | + | ====== Pipeline Control Commands ====== |
- | a pipeline | + | An important feature of the pipeline is the ability |
- | === set_pipeline_parameter === | + | A Pipeline PARAMETER is a way to store a text string for use in Pipeline commands. In one sense it is similar to specifying a global variable, such as body weight, that could be used in computations. It is actually much more flexible than that in the pipeline. The Visual3D pipeline commands permit multiple entries on a single line, and since the entire line can be represented as a string, a single PIPELINE PARAMETER can represent multiple signals. |
- | pipeline parameters can be created in the pipeline and used as variables in other commands in the same pipeline. | + | == Set_Pipeline_Parameter == |
- | === set_pipeline_parameter_to_folder_path === | + | [[https:// |
- | set a pipeline parameter to be the folder path. | + | Pipeline parameters can be created in the pipeline and used as variables in other commands in the same pipeline. |
- | === set_pipeline_parameter_to_list_of_tagged_files === | + | == Set_Pipeline_Parameter_To_Folder_Path |
- | creates a pipeline parameter containing the names of the tagged files. | + | [[https:// |
- | === set_pipeline_parameter_to_list_of_files === | + | Set a pipeline parameter to be the Folder path. |
- | in order to process multiple files it can be useful to identify all of the files in a folder path and assign the names to a pipeline parameter. | + | == Set_Pipeline_Parameter_To_List_Of_Tagged_Files == |
- | === set_pipeline_parameter_to_list_of_signal_names === | + | [[https:// |
- | in order to process multiple signals it can be useful to identify all of the signals | + | Creates a pipeline parameter containing |
- | === set_pipeline_parameter_to_data_value === | + | == Set_Pipeline_Parameter_To_List_Of_Files |
- | create a pipeline | + | [[https:// |
- | === set_pipeline_parameter_from_expression === | + | In order to process multiple files it can be useful to identify all of the files in a folder path and assign the names to a pipeline parameter. |
- | create a pipeline parameter from an expression | + | == Set_Pipeline_Parameter_To_List_Of_Signal_Names == |
- | === set_pipeline_parameter_from_for_loop === | + | [[https:// |
- | create a pipeline parameter | + | In order to process multiple signals it can be useful |
- | === prompt_for_pipeline_parameter_value === | + | == Set_Pipeline_Parameter_To_Data_Value |
- | prompts a dialog for user to create a pipeline parameter with the specified parameter value. | + | [[https:// |
- | === prompt_for_multiple_pipeline_parameter_values === | + | Create a pipeline parameter with the values of a signal |
- | prompts a dialog for user to create multiple pipeline parameters with the specified parameter values. | + | == Set_Pipeline_Parameter_From_Expression == |
- | === get_pipeline_parameter_count === | + | [[https:// |
- | get a count of the number of parameter values in a parameter | + | Create |
- | === get_pipeline_parameter_index_value === | + | == Set_Pipeline_Parameter_From_For_Loop |
- | create a pipeline parameter containing the value of one component (e.g. index) from another parameter. | + | [[https:// |
- | === for_each and end_for_each === | + | Create a pipeline parameter to mimic a traditional for loop. |
- | executes pipeline commands multiple times for each item in a list of items. it is not identical with a "for loop" or "do loop" in a programming language because the items must be explicitly defined as items in the command. this has some powerful consequences because it means that you can " | + | == Prompt_For_Pipeline_Parameter_Value == |
- | === conditional_statement and conditional_statement_end === | + | [[https:// |
- | executes | + | Prompts a dialog for user to create a pipeline |
- | === halt_pipeline_on_error === | + | == Prompt_For_Multiple_Pipeline_Parameter_Values |
- | another debugging feature of the pipeline workshop is the ability to halt execution of commands on the "first error". when the first error occurs, commands will stop executing and the errors and warnings will appear in the processing results window. | + | [[https:// |
- | === pipeline_breakpoint === | + | Prompts a dialog for user to create multiple pipeline parameters with the specified parameter values. |
- | this command will place a breakpoint in the pipeline that will allow the user to review the results from the previous pipeline commands and resume when you feel you are ready to resume or halt if you are not. | + | == Get_Pipeline_Parameter_Count == |
- | === comment === | + | [[https:// |
- | < | + | Get a count of the number of parameter values in a parameter |
- | < | + | |
- | < | + | |
- | < | + | |
- | ! /comment= | + | == Get_Pipeline_Parameter_Index_Value == |
+ | |||
+ | [[https:// | ||
+ | |||
+ | Create a pipeline parameter containing the value of one component (e.g. index) from another parameter. | ||
+ | |||
+ | == For_Each and End_For_Each == | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | Executes pipeline commands multiple times for each item in a list of items. It is not identical with a "for loop" or "do loop" in a programming language because the items must be explicitly defined as ITEMS in the command. This has some powerful consequences because it means that you can " | ||
+ | |||
+ | == Conditional_Statement and Conditional_Statement_End == | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | Executes pipeline commands that occur between Conditional_Statement and Conditional_Statement_End. The intermediate commands will only be executed if the EXPRESSION in the Conditional_Statement command is TRUE (returns any value other than 0). | ||
+ | |||
+ | == Halt_Pipeline_On_Error == | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | Another debugging feature of the Pipeline Workshop is the ability to halt execution of commands on the "first error" | ||
+ | |||
+ | == Pipeline_Breakpoint == | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | This command will place a breakpoint in the pipeline that will allow the user to review the results from the previous pipeline commands and resume when you feel you are ready to resume or halt if you are not. | ||
+ | |||
+ | == Comment == | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | ! /COMMENT= | ||
**;** | **;** | ||
visual3d/documentation/pipeline/pipeline_commands/pipeline_control_commands.1718801550.txt.gz · Last modified: 2024/06/19 12:52 by sgranger