VLAM Virtual Laboratory AMsterdam

1
VLAMVirtual Laboratory AMsterdam
A collaborative analysis environment for applied
experimental science
2
Objectives

• Designing middlewarebridge gap beween Grid- and
  application-layer
• Enable VL users to define, execute, and monitor
  their experiments
• Provide to VL users
• location independent experimentation,
• familiar experimentation environment
• assistance during his experiment

3
VLAM Functional View
DNA Arraygenomeexpression
Material Ana
Application
Others
Micro beamFTIR, ...
Domains
VLAM Science Portal Workbench
VLAM RTS
Grid Fabric (Farms, microscope, etc.)
4
(No Transcript)
5
Experimental Workflow
Information gathering
Interpretation
Experimentation
Access todevices
Access todata
Access to information
Grid accessible infra apparatus, systems, network
6
The VL Architecture
7
VL-AM Kernel DB

• Stores user support information
• experiment topology definitions
• module descriptions
• user information
• Provides cross-links to application annotations
• Based on object-oriented database technology
• Extends resource directories now used in Grid

8
Application Domain DB

• Characteristics of typical application
• Scientist(s) performing the experiment
• On objects and preexisting information data
• On which processes operate
• That use apparatus with specific properties
• Resulting in new data and information
• A domain-specific flow of processes

Examples Expressive, MACS, EFC, ...
Expressive
MACS
EFC
9
VL Experimentation Environment Data Model
Common aspects of an experiment
Process and data flow in an experiment
Annotations on an experiment
10
(No Transcript)
11
MacsLab Experiment
12
VL-AM Front End
13
VL Run Time System

• Features
• Data-flow-like experiments with modules
• Control parameters read state
• Interact with the Grid layer
• Interaction with VL RTS?
• Module developers API
• End-users None (transparent)

14
Module Skeleton API

• Principles
• Module core shared lib. with entry points
• Init()
• Run()
• Module Skeleton Services
• I/O stream lib. (port' based)
• Data-type interface lib.
• Parameter state access lib.

15
Communications
FIFO Stream
User code
User code
16
Communications
VL-AM RTS
GridFTP enabled HPSS
User code
User code
17
Vlab Testbed
XXXX
External DB
AMOLF
SARA
XXXX
NIKHEF
Other DB
18
Status of the VL Prototype

• VL-AM RunTime System
• Module skeleton and manager available
• Communication via sockets and GridFTP
• VL Front End
• VL assistant
• VL graphical editor

19
Conclusions

• VLAM a science portal for exp. analysis
• Workflow support forBio-informatics, Materials
  Scienceand Biomedical Simulation Visualisation
• Seamless access to distributed resources and
  content
• Resource Management based on Globus
• Content Management VLAM middleware
• Current status integrating first prototypes