h1. %{color:darkred}Managing processing% |{width:4000px;text-align:left;border-color:transparent}. !/attachments/download/19/fr_FR.png! [[Fr_computreegui_stepmanager|...version française de cette page]]| h1. Step Manager p<>. The *steps tree* is managed in the *Step Manager*. This component allows you to create a valid step hierarchy. Once processing is performed, each step contains also the results it has created. p<>. _*Step Manager*after creating a *steps tree*, but before processing_: !step_manager_1.png! p<>. _*Step Manager* during the processing of the *steps tree*_: !step_manager_2.png! p<>. _*Step Manager* after the end of processing_: !step_manager_3.png! p<>. *The first column* contains the *name of the steps*, with arrows at left to collapse the hierarchy affiliated with each step. p<>. After processing, it also contains the name of the results produced. p<>. *The second column* contains a *progress bar* to monitor the progress of processing. notice<>. Some multi-threaded steps do not monitor progress, and remain at 0 % throughout processing, and then suddenly go to 100 % at the end of execution. p<>. *The third column* stores *processing time* of steps (updated at the same time that the progress bar). p<>. *In the case of results*, this column contains a checkbox. Checking this box, allows you to "send" the result to *Model Manager*. This has the effect of displaying the *OUT result model* of the step in the *Model Manager* (which will manage its display, as discussed in section [[Fr_computreegui_items|Displaying items]]). p<>. *The fourth column* allows for steps to enable *debug mode*. {{collapse(details on debug mode) p<>. When the step was designed in this way, and the *debug mode* is enabled, you can perform processing step by step, and see the result in transitory states. p<>. *The debug mode* is managed using the buttons on the main *toolbar*: !debug.png! p<>. The *first button* is used to start the execution of the *next iteration* of the step. p<>. *The second button* will jump n iterations, where n is determined by the value that follows. }} tip<>. Each step is uniquely identified (number in parentheses). p<>. *To start the execution* of the steps tree you must click on the button !{width: 24px}play.png!. It can also suspend using the button !{width:24px}Stop.png!. p<>. *To export the tree steps* as a *script*, you must click on the button !{width:24px}media-floppy.png!. Scripts can then be loaded using the button !{width:24px}folder_add_32.png!. h1. Initialization of the steps tree p<>. To initiate a sequence of steps, we must first insert an *initial step*. p<>. It can be inserted: * A *Load File Step* using the button !{height:24px}folder_add_32.png!. In this case, a file selection window opens, and loads data, once the file selection has been validated. * An *Initial Step*, using the button !{height:24px}add.png!. In this case you must select the step in the plugins sub-menu that contains it. This step type allows for more complex loading (multiple files of different types, settings before loading, data creation...). !canbeaddedfirst.png! h1. Adding children steps p<>. Once inserted a starting point, adding other steps is done using the *context menu*: Right-click on a step for which you want to add a *child step*. notice<>. Child step addition can only be done by right-clicking on a step but not on a result. !menu_contextuel_etape.png! *Elements of the step context menu* : p<>. The first part of the menu allows modifying the current step: * *Run*: starts the processing * *Step Information*: opens a window with detailed information about the step. This is the same window with the menu button _Help / About plugins / Information about step_ (see [[En_computreegui_intro#Help menu|General organization of the interface / Help menu]]). However from here *OUT result models* are available even for copy results. * *Configure input results*: change the results taken into account for input, in the case where several candidates are valid. * *Configure*: opens the box for setting the current step parameters. * *Delete*: delete step (and all its children steps). warning<>. *In case of reconfiguration of *input results* or of change of step parameters, an *asterisk* now precede the name of the step in the *steps tree*. This means that the launch of processing will lead to re-run the step and all its children. All relevant results will be erased before being recalculated. p<>. The second part of the menu contains a sub-menu *for each plugin loaded*. This sub-menu contains the list of steps for the considered plugin. Those in *gray*are not compatible with the results produced by the current step. The others can be added. By leaving the mouse for a moment, a tool tip briefly describing the function of the step is obtained. By clicking, the step is added, what causes the display of the configuration window for *input results* (if necessary), then the *window* for setting step parameters of the new child step. h1. Configuring a step p<>. Once added, the step is (most of the time) to be configured. p<>. First step *analyzes the results of the parent step* (or even the entire hierarchy, if the recursive search is active for the considered IN result model). This analysis selects result( s) consistent as input. p<>. This selection works by comparing the *IN results models* of the added step with *OUT results models* of candidates results. p<>. In the case where multiple results are valid, the window *to configure the input results* is open: !config_resultin_1.png! p<>. *The left side* lists *candidates* results, sorted by searched *IN results models* of the step. The number of the step bearing each result is shown in parentheses. p<>. *Double-clicking on a result* will transfer the selected result as a validated correspondence to the right side (you can also drag the result from the left side to the right side). !config_resultin_2.png! p<>. The right side displays the *results matches* validated above. On the right-bottom part, it is possible to select alternatives items / groups levels, if more than one possibility is valid. {{collapse(Explanation of the concept of Turns) p<>. On the right part of the window, we see a tab *Turn 1* and a tab with a +. + Adds the other turns. p<>. *Each added turn* (by default there is only one) is used to configure the step with different candidates results. In this case, the step will be executed once for each turn added. p<>. The results produced by all turns will all be added to the step. warning<>. Managing multiple turns is not always taken into account by plugin developers. This can lead to application crash, if the step was not designed accordingly. If this happens, thank you to report by a demand in the plugin project page on http://rdinnovation.onf.fr. }} p<>. *Once all choices done*, simply click *OK* to validate the configuration if *input results*. p<>. Then, if necessary, the window for setting step parameters opens. It contains all the adjustable parameters of the algorithm to run. For example their are the parameters for the _OE_StepExtractSoil03_ step: !config_oe_stepextractsoil03.png! p<>. Once the parameters are selected and approved, the step is actually added in the *steps tree*. _____ |[[En_computreegui_intro|Previous (General Organization of the interface)]]|[[En_computreegui|Back to GUI summary]]|[[En_computreegui_items|Next (Displaying items)]]|