This page (revision-52) was last changed on 10-Sep-2018 12:25 by Jochen Reutelshöfer

This page was created on 17-Dec-2012 15:33 by CarstenWasner

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
52 10-Sep-2018 12:25 4 KB Jochen Reutelshöfer to previous
51 10-Sep-2018 12:24 4 KB Jochen Reutelshöfer to previous | to last
50 10-Sep-2018 12:23 4 KB Jochen Reutelshöfer to previous | to last
49 28-Aug-2018 11:31 4 KB Albrecht Striffler to previous | to last
48 09-Dec-2016 15:57 4 KB Albrecht Striffler to previous | to last
47 09-Dec-2016 15:56 4 KB Albrecht Striffler to previous | to last
46 29-Apr-2016 15:35 4 KB Albrecht Striffler to previous | to last
45 26-Nov-2015 11:35 4 KB Albrecht Striffler to previous | to last
44 04-Feb-2015 10:10 4 KB Albrecht Striffler to previous | to last
43 11-Aug-2014 11:37 4 KB Albrecht Striffler to previous | to last
42 11-Aug-2014 11:36 4 KB Albrecht Striffler to previous | to last
41 11-Aug-2014 11:29 4 KB Albrecht Striffler to previous | to last

Page References

Incoming links Outgoing links
Doc Diaflux
Doc Diaflux

Version management

Difference between version and

At line 1 changed 3 lines
! Definition:\\
Diaflux is a graphical workflow authoring plugin for KnowWE.
It is used to model complex problems in an easy to read and understand fashion.
[{TableOfContents title='Contents'}]
At line 5 removed 3 lines
! Syntax and Semantic:\\
An Diaflux workflow is defined inside the markup __DiaFlux__
Example:
At line 9 changed 7 lines
%%knowledgebase
DiafluxExample
@comment: a simple example
@filename: knowledgebase.d3web
@version: 0.01
@uses: DiafluxExample
/%
!! Definition\\
At line 17 changed 6 lines
%%Question
input
- user_inputs
-- temperature [num] {DEGREES_C}
@package: DiafluxExample
%
Diaflux is a graphical workflow authoring plugin for KnowWE.\\
It is used to model complex problems in an easy to read and understandable fashion.\\
At line 24 removed 8 lines
%%Solution
output
- system_output
-- warm
-- cold
-- just_fine
@package: DiafluxExample
%
At line 10 added 8 lines
!! Syntax and Semantic\\
An Diaflux workflow is defined inside the markup __DiaFlux__\\
! Example
At line 34 changed one line
<flowchart fcid="flow_7184e213" name="ExampleWorkFlow" icon="sanduhr.gif" width="750" height="500" autostart="false" idCounter="15">
<flowchart fcid="flow_7184e213" name="ExampleWorkFlow" icon="sanduhr.gif" width="699" height="380" autostart="true" idCounter="23">
At line 38 changed one line
<position left="57" top="44"></position>
<position left="20" top="31"></position>
At line 43 changed one line
<position left="591" top="379"></position>
<position left="554" top="340"></position>
At line 48 changed 2 lines
<position left="231" top="135"></position>
<decision>"Temperature"</decision>
<position left="194" top="20"></position>
<action markup="KnOffice"><![CDATA[ambient_temperature]]></action>
At line 53 changed 2 lines
<position left="177" top="268"></position>
<decision>warm</decision>
<position left="280" top="118"></position>
<action markup="KnOffice"><![CDATA["warm" = P7]]></action>
At line 58 changed 2 lines
<position left="305" top="268"></position>
<decision>cold</decision>
<position left="159" top="118"></position>
<action markup="KnOffice"><![CDATA["cold" = P7]]></action>
At line 63 changed 2 lines
<position left="565" top="268"></position>
<decision>just_fine</decision>
<position left="544" top="118"></position>
<action markup="KnOffice"><![CDATA["just_fine" = P7]]></action>
At line 52 added 4 lines
<node fcid="#node_16">
<position left="358" top="329"></position>
<action markup="KnOffice"><![CDATA["just_fine" = N7]]></action>
</node>
At line 57 added 11 lines
<node fcid="#node_18">
<position left="478" top="228"></position>
<action markup="KnOffice"><![CDATA["warm" = N7]]></action>
</node>
<node fcid="#node_19">
<position left="591" top="229"></position>
<action markup="KnOffice"><![CDATA["cold" = N7]]></action>
</node>
At line 77 changed one line
<guard markup="KnOffice">"Temperature" > 25</guard>
<guard markup="KnOffice"><![CDATA["ambient_temperature" > 25]]></guard>
<routingPoint x="8" y="0.5" />
At line 83 changed one line
<guard markup="KnOffice">"Temperature" < 25</guard>
<guard markup="KnOffice"><![CDATA["ambient_temperature" < 25]]></guard>
<routingPoint x="1" y="0.5" />
At line 89 changed one line
<guard markup="KnOffice">"Temperature" = 25</guard>
<guard markup="KnOffice"><![CDATA["ambient_temperature" = 25]]></guard>
At line 93 changed 3 lines
<edge fcid="#rule_13">
<origin>#node_11</origin>
<target>#node_3</target>
<edge fcid="#rule_15">
<origin>#node_6</origin>
<target>#node_16</target>
<routingPoint x="0" y="0.86" />
At line 100 changed one line
<target>#node_3</target>
<target>#node_16</target>
At line 104 changed 2 lines
<edge fcid="#rule_15">
<origin>#node_6</origin>
<edge fcid="#rule_17">
<origin>#node_16</origin>
At line 107 removed one line
<routingPoint x="0" y="1" />
At line 112 added 20 lines
<edge fcid="#rule_20">
<origin>#node_11</origin>
<target>#node_18</target>
</edge>
<edge fcid="#rule_21">
<origin>#node_11</origin>
<target>#node_19</target>
</edge>
<edge fcid="#rule_22">
<origin>#node_19</origin>
<target>#node_3</target>
</edge>
<edge fcid="#rule_23">
<origin>#node_18</origin>
<target>#node_3</target>
</edge>
At line 112 removed one line
@package: DiafluxExample
At line 138 added one line
!! Diaflux Editor
At line 118 changed one line
The Diaflux workflow may be edited using the __Visual Editor__.
[{Image src='visual_editor.jpg' width='222' height='99' align='left' }]
\\
[{Image src='visual_editor_edit_nodes.jpg' width='540' height='303' align='left' }]
\\
! Diaflux elements
* __Start node__: entry point for a DiaFlux\\
* __Exit node__: exit point of a DiaFlux\\
* __Action node__: select a question, solution, or other flowchart and model an interaction with this it.\\
* __Comment node__: use this node to provide annotations to transitions or nodes.\\
* __SnapShot node__: used to inhibit the truth maintainance to reverse decisions before this snapshot. (Behaves like a diode.)\\
!Editor tools\\
* __Save flowchart and close editor__\\
* __Revert changes__\\
* __Close editor__ (without saving)\\
* __Delete flowchart__\\
!! Best Practices\\
* A DiaFlux flowchart shall have a unique name.\\
* One flowchart needs to be checked for Autostart. (That is where a session workflow will start.)\\
* Do not overload a single flowchart. Model rather small parts and reference them in a parent flowchart.\\
Rule of thumb: Not more than a monitors field of view.
* Use commend nodes (light blue) to structure flows/arrows.
!Terminology of DiafluxExample
%%knowledgebase
DiafluxExample2
@comment: a simple example
@filename: knowledgebase.d3web
@version: 0.01
/%
%%Question
input
- user_inputs
-- ambient_temperature [num] {°C}
%
%%Solution
output
- system_output
-- warm
-- cold
-- just_fine
%
%%Package
diaflux_example
%
This page (revision-52) was last changed on 10-Sep-2018 12:25 by Jochen Reutelshöfer Top