OGSA-DAI Render Demo

1
OGSA-DAIRender Demo

• NeSC Review
• 18 March 2004

2
Description and Aims

• The OGSA-DAI Render demo is intended to
  demonstrate both the Process and Data aspects of
  a Grid
• Flight path data is stored in a relational
  database (MySQL)
• Models are stored in flat files
• With thanks to Andrew Borley, Jonathan Davies,
  Neil Hardman and George Hicken of IBM UK.

3
Initial set-up
Render Node
Render Node
Render Node
Render Node
Flightpath Factory
Models Factory
Flightpaths
Models
Next
4
Data Flow
Render Node
Render Node
Render Node
Render Node
Web Client
Flightpath Factory
Models Factory
GDS
GDS
Models
Flightpaths
Next
5
Data Flow
Render Node
Render Node
Render Node
Render Node
Perform Documents sent to Render Nodes
Web Client
Render Nodes query GDS for the Flightpath
Render Nodes query GDS for the Model
Flightpath Factory
Models Factory
GDS
GDS
Models
Flightpaths
Next
6
Data Flow
Render Nodes process the images
Render Node
Render Node
Render Node
Render Node
Rendered images returned to the Web Client
Web Client
Animator
Flightpath Factory
Models Factory
The Animator Process composes the movie from the
rendered images
GDS
GDS
Models
Flightpaths
Next
7
Conclusions

• OGSA-DAI can be used for both
• Data access
• Process driven environment
• Extensible
• POV Ray process initiated by an OGSA-DAI Activity
• Facilitates the integration of different data
  sources
• Databases
• Files

8
Choosing a model flightpath
9
Editing flightpath

• Load flightpath data from database
• Edit camera path and points
• Save data back to flightpath database
• Models loaded from flat files

10
Rendering scenes

• Dispatch scenes to rendernodes
• Progress notification allows tracking of each
  scenes status

11
RenderNode

• Each RenderNode gets a scene
• Custom written OGSA-DAI activity to start POVRAY
  using data from flightpath and models databases
• After rendering scene, RenderNode sends back data

12
Assemble movie

• Each individual rendered scene is assembled into
  a movie by the web client