COMMENTS / ORDER of the workflow 

idea: (1)->(2)->(3) ... 
go from more abstract / scientific/conceptual (1) to more plumbing
workflow (2) to really plumbing workflow (3)

Then: switching to (predefined) design (4)-> then "live" design (5) ->
and the live execution (6).

I could e.g. do (1) and (2), you could do (3), (4), (5), (6).

Bertram

(1)  classifier.xml (GEON Mineral Classification workflow)
- Description: retrieves mineral composition data from a database and
applies a classification alogrithm based on diagrams.
This is an example of reverse engineering a manual scientific WF and
automating it. The whole SWF could be abstracted into a single WS or
web page.

- shows use of 
-- ABSTRACTION (subworkflow), 
-- CUSTOM ACTORS (GetPoint, ...),
-- ITERATION/LOOPS ("drilling down" into diagrams),
-- BROWSER-DISPLAY (SVG)


(2) Composite_R_DataReader_Example.xml
- use of an external program/package (R) via '$' (cmd line)
- use of parameters ('DelimiterValue', editable 'RScript', ..)
- creation of a plot (show with ImageDisplay)

(3) GravityToShape.xml
- don't forget the password!

(4) gravityModel.xml
- example of a conceptual/design workflow, halfway from pure design to
executable workflow
- also an example typical of a scientific domain (comparing gravity
models etc)

(5) design.xml (some simple example)

- Put an expression actor. Name it ... Add ports...
  Continue this until all the actors in the example (designWF.xml)
  is created.
-- Demonsrate use of relations.
--- Demonstrate composite actors by creating a simple hierarchy.

(6) exec.xml (simple exec example)

- Put an expression actor. (e.g. CA highway) Link it to the display.
  Run it under SDF by animation.
-- Demonsrate use of relations by also linking it to an email actor.
--- Demonstrate composite actors by creating a simple hierarchy.


