Whole-Brain-Tractography-Wizard - Revision history

Demian: /* API support for workflows */

2012-01-10T16:59:44Z

API support for workflows

2012-01-10T16:57:19Z

API support for workflows

2012-01-10T16:13:57Z

API support for workflows

2012-01-10T16:09:19Z

API support for workflows

2012-01-10T16:07:55Z

The Idea of a Wizard

2012-01-10T16:06:53Z

Obtaining the input from the Interface

2012-01-10T15:38:34Z

Obtaining the input from the Interface

2012-01-10T15:36:15Z

API support for workflows

2012-01-10T15:32:54Z

The Idea of a Wizard

2012-01-10T15:24:56Z

Obtaining the input from the Interface

← Older revision		Revision as of 16:59, 10 January 2012
Line 21:		Line 21:

	In which the idea is to derive a new class from ctkWorkflowWidgetStep for each step and then add them all to the workflow widget ctkWorkflowStackedWidget making the transition explicit. The class ctkWorkflow is a state machine that controls the sequence of steps that are to be executed. The next figure gives an example of a non-linear workflow that can be implemented through this method:		In which the idea is to derive a new class from ctkWorkflowWidgetStep for each step and then add them all to the workflow widget ctkWorkflowStackedWidget making the transition explicit. The class ctkWorkflow is a state machine that controls the sequence of steps that are to be executed. The next figure gives an example of a non-linear workflow that can be implemented through this method:
−	[[File:workflow_scheme.jpg]]	+	[[File:workflow_scheme.jpg \| thumb \| Example fo non-linear workflow]]

@@ Line 20: / Line 20: @@
 * [http://www.commontk.org/docs/html/classctkWorkflowWidgetStep.html ctkWorkflowWidgetStep]: Base class for each step of the workflow
-In which the idea is to derive a new class from ctkWorkflowWidgetStep for each step and then add them all to the workflow widget ctkWorkflowStackedWidget making the transition explicit
+In which the idea is to derive a new class from ctkWorkflowWidgetStep for each step and then add them all to the workflow widget ctkWorkflowStackedWidget making the transition explicit. The class ctkWorkflow is a state machine that controls the sequence of steps that are to be executed. The next figure gives an example of a non-linear workflow that can be implemented through this method:
 ===Events of each workflow widget step (ctkWorkflowWidgetStep)===

@@ Line 16: / Line 16: @@
 =API support for workflows=
 In order to do this, we use CTK's support for workflows:
-* [http://www.commontk.org/docs/html/classctkWorkflowStackedWidget.html ctkWorkflowStackedWidget]
+* [http://www.commontk.org/docs/html/classctkWorkflow.html ctkWorkflow]: State machine for the workflow
-* [http://www.commontk.org/docs/html/classctkWorkflowWidgetStep.html ctkWorkflowWidgetStep]
+* [http://www.commontk.org/docs/html/classctkWorkflowStackedWidget.html ctkWorkflowStackedWidget]: UI class for the workflow
 In which the idea is to derive a new class from ctkWorkflowWidgetStep for each step and then add them all to the workflow widget ctkWorkflowStackedWidget making the transition explicit

@@ Line 16: / Line 16: @@
 =API support for workflows=
 In order to do this, we use CTK's support for workflows:
-*  ctkWorkflowStackedWidget
+* [http://www.commontk.org/docs/html/classctkWorkflowStackedWidget.html ctkWorkflowStackedWidget]
-*  ctkWorkflowWidgetStep
+* [http://www.commontk.org/docs/html/classctkWorkflowWidgetStep.html ctkWorkflowWidgetStep]
 In which the idea is to derive a new class from ctkWorkflowWidgetStep for each step and then add them all to the workflow widget ctkWorkflowStackedWidget making the transition explicit

@@ Line 12: / Line 12: @@
 * Validate the input
 * Set up the parameters for the next step
 =API support for workflows=

@@ Line 36: / Line 36: @@
 This class:
 * Takes the widget for each step from a UI file generated by the designer
 And requires
 * Each step to be declared as the name of such file

@@ Line 34: / Line 34: @@
    WorkflowConfiguration
-===Declaring the Modules===
+This class:
      step_widget_files = [
          'dicom2nrrd',
@@ Line 42: / Line 49: @@
+     ]
-===Declaring Each Module's Fields===
+====Declaring Each Module's Fields====
      step_widget_fields = {
          'dicom2nrrd':[
@@ Line 68: / Line 75: @@
+     }
-===Validating Data for a Field===
+====Validating Data for a Field====
    def validate_dicom2nrrd(self, step_object, data):
@@ Line 94: / Line 101: @@
              display_error("Error in DICOM to NRRD conversion, please see log")
          return result_status
 ==Details on Each Step's CallBack Implementation==

@@ Line 30: / Line 30: @@
 You can find the example at
    Modules/Scripted/Scripts/DICOM2FullBrainTractography/DICOM2FullBrainTractographyLib/full_tractography_workflow.py
 ===Declaring the Modules===

← Older revision		Revision as of 15:24, 10 January 2012
Line 14:		Line 14:

	==Obtaining the input from the Interface==		==Obtaining the input from the Interface==
		+
		+	You can find the example at
		+	Modules/Scripted/Scripts/DICOM2FullBrainTractography/DICOM2FullBrainTractographyLib/full_tractography_workflow.py

	===Declaring the Modules===		===Declaring the Modules===