Rough Transcription of Access Grid/PSE Joint Discussion

**Stevens:** On the Access Grid side: layer of structure that is open
\-\-- sort of a sketch of an architecture that would take the grid model
and blow it up. At the low level: support for devices and immersive
hardware; on top of that a set of services that allows capabilities
available to high-end systems to be made accessible to desktop systems
and builds up a structure for management. At the upper level work flow
management that includes electronic meeting support across multiple
sites that includes floor control...who can address the group taking
component technologies like steering and integrating them to with floor
control management of multiple data streams in a coherent way. Goal is
to define and implement a way of building up a more integrated
structure. It touches on a lot of the technology projects that people
have been working on and encapsulating them as layers either by putting
object faces on them or something else. Quick (3months) plan and quick
(3 month) implementation.

**Ruwart:** Key getting apps to run in distributed environment. Using
distributed output devices. Need to do one as test case and then
everyone will say oh that's what we want to do...

**Stevens:** Key couple dozen projects have run on Globus testbeds but
not at a production level. Arch that has emerged from those experiments
reflects understanding....only test track miles not cross country miles.
Need cross country mileage.

**Reed:** If you have non-distributed system for code development, to
succeed in the Grid environment, you need to get all the pieces of that
system working in some distributed way

**Schwan:** Interface tech is not there yet. Stuff missing. For instance
a way of defining the dynamic variance of quality acceptable. Look at
high-end and low-end case to see what happens and look at the
technological implications. Tie together very different visualization
approaches. It's too soon to commit to a concrete architecture

**Reed**: Must be non-committal for initial implementation to shed light
on whether architecture implementation is good or not.

**Stevens:** Research into how to get it right...on the alliance side
we're funded to do development and deployment not research. Doesn't have
to be best, just has to work and be tested by someone who actually cares
about it. Has to be deployed. There are lots of venues. Trying to
collaborate creates a natural context for us to try to debug the access
grid. We'll be the critics of the architecture. Move from individual
groups building pieces to teams integrating infrastructure. Transition
has to be put on schedule and commitments must be made to getting work
done. Framework from which to share results and have partners with which
to refine.

**DeFanti:** Wheless and Hibbard aren't doing production. In demos the
QOS required for production tools is not there. For instance users can't
interact with databases at the same time. Getting the data into the
computation is an open issue.

**Stevens:** Plus we're not using collaborative technologies to manage
and mediate collaborative sessions.

**DeFanti:** Right now we want, for instance, to easily plug in HDF. We
need to use HDF in a way that understands how to send data that doesn't
confuse the real-time interactive stuff we're doing.

**Reed:** Wants QoS

**DeFanti**: should be many stories that are missing 2 or 3 pieces from
being ideal

**Stevens:** Open issue is to what extent we need low-level platform
inclusion

**DeFanti:** High end not coupled with Java

**Reed:** Someone has to be able to see this stuff on laptop

**Stevens:** Some of the tech that will solve the problems exists but is
not integrated

**Ruwart:** Major pieces are there, it's a matter of putting them all
together and making them consistently reliable. i.e. ATM connection is a
hit and miss thing most of the time. vBNS connection is flaky

**Reed:** Why does data have to be moved

**Ruwart:** There has to be some data movement. We are trying to
implement terabyte dataset visualization and analysis. To interactive
software to run a volume renderer on remote machine and send it back or
running locally and moving data back. Video conferencing software that
links together and gives control

**Stevens:** What is the infrastructure we need to make it work in
distributed environment.

**DeFanti:** You need video teleconferencing - a piece of software
enabling a group to talk about dataset, look at dataset. Now we don't
have software to do it. Outcome of this meeting will be motivator to do
it

**Hibbard:** Low-level tools exist....written in Java and performance
sucks...loves Java; distributed objects move complex software easily.

**Reed:** Down sample data so that all that shows on low fidelity
display is subset that has the most important features

**Ivan:** Need to publish a representative set of what we have built \--
a taxonomy of what we have and then wire protocols subcomponents
parceled out to PCs that

**DeFanti:** Sun Java 3-D video mix outputs to get them on the same
screen frustrates idea of being able to do this stuff on laptop in
office.

**Stevens:** Go where vendors fear to tread. Higher end composite
end.... Use capability to synthesize what can't be done on desktops
local channels for viz separated from logical channels for collaboration
and communication. Synthetic prototype to play with and integrate before
they bring it down to the desktop.

**Ivan:** we have a different goal than vendors.

**DeFanti:** Voice control allows you not to have to manage a bunch of
different input devices for different channel managers

**Stevens:** Build active space concept. Audio environments and
interaction control with same amount of precision. Most people don't
want to work in a cave 8 hours a day. Build an environment in which you
want to do both real work and demo.

**Schwan:** 1. Outsource computations to other places where they weren't
before to deal w/ bad communication; 2. Migrate computations -- we need
arch to do this; 3. Adjust to different resolution requirements. Mental
model of services is fine but objects don't give us this level of
capability

**Stevens:** Comp grid service model QoS brokered access. Imagine the
next level of services on top of grid services....

**Reed:** every person access and high level support presents a tension

**Stevens:** Low level is off our radar screen. We can compete is in
specialized domains where industry won't go.

**Schwan:** Still need to give laptop users the ability to integrate
with high level solution.

**Reed:** Try to make at least some of those interaction modalities
available to someone with only a laptop

**Stevens:** We can be successful even if we require users to access
high-end stuff. Long term agenda to downscale to low end. We can waste a
lot of time trying to make the absolute scaling issue work. What's
really interesting is that groups can be effective as groups using
high-end technologies

**DeFanti:** We have a niche in creating a class of things that money
can't buy a solution for. We provide the software to blend the stuff
together.

**Schwan:** The key is recognizing that we can't optimize for the
desktop. The best we can do is provide reasonable access from desktop
where users can do something even if it's not as much as if they were
using a high-end system.

**Stevens:** PSE stuff.... Bounce it around. In some sense its trying to
harness the problem by leveling all the resources that we have access
to. And putting those in a package that application groups can use to
quickly assemble the software that they need to do their work. AT teams
are building their own environments without substantial leverage from ET
teams. Get ET teams to architect stuff that they can easily take
advantage of.

**DeFanti:** Cosmology and Environmental Hydrology are intertwined with
ET teams.

**Stevens:** EC and Bio workbench aren't leveraged.

**Reed:** Pick two scenarios that we will use in both groups one for
collaboration and one for problem solving.

**Tafti:** CE workbench uses ET C Habanero and Globus. What they want to
do is keep workbench as interface to Globus. It would use Globus
facilities underneath.

**Stevens:** SCIrun could be packaged as an intermediate layer to allow
CE workbench to take advantage of it's viz capabilities.

**??** Don't want to know that Globus exists.

**Stevens:** VisAD integration w/ Habanero could be viewed as just such
a building block approach. We haven't made an all out effort to pkg.
upper layers so that they can be viewed/used as toolkits

**??** In short term: Crutcher has radio astronomy workbench equivalent
in production mode that works. Crutcher won't want to stop using what he
has. What comes out should be general and that is the most important
thing. It won't happen in 6 months.

**Stevens:** Trying to have a more formal process where AT teams can
express their needs and requirements and we can tell them how what we're
doing can help. Part of it is making them aware and encouraging them to
use it as it fits their needs.

**??:** More applications people need to be included...lets define what
a workbench needs in a very general sense.

**Reed:** Organize an ET/AT meeting to find out what kinds of high-level
needs they have. What can we package for them. There are a variety of
ways that you can split that up.

**Hibbard:** level above delivering bytes or cycles. It is delivering
data models, delivering events...there can be display models...models
and implementations are largely what these PSEs are about.

**Fowler:** Team A mtg. people got to know each other. Kicked around the
idea of putting together a workshop. He volunteered to host ET/AT
meeting in Houston. Have to bring a couple of teams of committed people
together and not try to do it all online. Make sure this process
includes a requirements analysis, set of white papers, distill what the
problems and approaches are, redirect certain individuals into new
directions and ID people who are not currently involved with the
analysis. If Jim Browne doesn't find something to do within the
Alliance, he'll give up budget and move on. Need offline homework before
we can attack the problems. Need mtg. half past March?

**Toole:** We want a mtg. sooner.

**Schwan:** Everything could be inside a PSE.

**Fox:** Immediately drill down on AT teams

**??:** A PSE is a portal to the Grid

**Fox:** You give a talk on the 15th and tell us all about AT
requirements

**Reed:** We should come up with a couple of scenarios to drive
discussion: One that tries to get at access grid collaboration and one
that tries to get at the PSE aspect

**DeFanti:** We have collaboration. We are doing a collaborative demo
with people at NCSA and Princeton and Minn. where everyone is working on
one dataset.

**Stevens:** Site Visit is a scenario that maps against the access grid
the fact that you want to demo a 4-way scientific visualization
application. What we haven't done is something in the context of a real
activity

**Schwan:** Don't want to think of the data as being used in such a
scenario as static. NCSA is very focused on the computation being
generated and changed as we study it.

**DeFanti:** There are different views as to how you look at real work
being done on big computer

**Stevens:** site visit demos: process of quick configuration is part of
making this work

1 presentation

2 demos

3.open group discussion

4.private group discussions

**Hibbard:** Environmental Hydrology presents a multidisciplinary
application. A configurable model would be the beginning of the
workbench. It uses Globus and VisAD. It could use Habanero. It has data
fusion. The dataset includes information on rainfall. This application
incorporates multiple sub-disciplines, real-time output that is fused
for the purpose of visualization, and it requires collaboration. The
question of how to do fusion could be a collaborative software
development effort.

**von Laszewski:** CMT application is not a Team activity it is a demo

**Schwan:** Another case study could be a distributed learning
environment teaching students how to use the Access Grid. An online,
interactive class. Should be a plug and play environment providing a
tutorial on how to bring up new site. Could include a group of
competitive applications. Offer it to users who have to use a
problem-solving environment.

  ----------------------------------- -----------------------------------
  PSE                                 Access Grid

  Multidisciplinary models, coupling, Site Visit: collaborative
  fused viz, distributed              presentations, demonstrations, open
  collaboration, collaborative SW     group discussions, private
  development and software            discussions prep and post analysis
  development mode: Information       
  archives.                           
  ----------------------------------- -----------------------------------

**PSEs -** To come up with pairwise combinations of interoperability
that would enable new kinds of workbenches, we'll decompose existing
solutions - for instance the Biology Workbench - to see how extant tools
could be used to deliver services required. Define interfaces to
existing Alliance ET tools to construct workbenches in a more systematic
way. Goal to allow users to access these existing services and
components in the most flexible and easily-used manner possible. Point
solutions can work as long as each point solution is built upon a
generalized block of toolkits.

**Preliminary decomposition of the Biology Workbench:**

Natural web interface to a composition of services - tools for searching
different protein structures and getting info back into workbench. Each
program and each database becomes a resource, need Jini or Netsolve to
allow you to find out which software is available on which machines
through agents. Generally not very compute intensive, primarily a
database type of tool. Has submit button that currently goes to
Webserver with CGI scripts that provide a standard interface to
databases Need to define a CORBA facility. Data is an important part but
computations can be very complex and can run for days. Cosmology
crunches data for years. One of the deterrents to doing very large
computations is how do you look at all the data. Tafti would rather do a
small computation where I can get some data and look at it and
understand it. Biology workbench takes data retrieved through database
searches and names them. Perform various computations and matching using
backend computational tools - 1 machine -- resource allocation.
Displayed using standard client side visualization tools ?Rasmin?, a
molecular visualization tool - a Netscape plugin that renders molecules
and displays in 3D. Does protein matching. It enables workflow - data
going from one code into another.

> It has 2 big advantages:
>
> 1\. Didn't have to install it
>
> 2\. Imposed standardization on data formats providing a mechanism
> enforcing of a set of standards for the discipline -- using the
> standard, you can plug in new analysis tools.
>
> Need to support multiple visualization services. Data format is going
> to be application specific. No generic data formats.
>
> Metadata management
>
> Proximate string matching
>
> Domain-specific desktop visualization

**PSE Components Toolkit Entries: should distinguish between ET and
services**

<table>
<colgroup>
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 14%" />
<col style="width: 15%" />
<col style="width: 12%" />
<col style="width: 14%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>Name</strong></td>
<td><strong>Computing Model</strong></td>
<td><strong>Data Model</strong></td>
<td><strong>Displ Model</strong></td>
<td><strong>Collab Model</strong></td>
<td><strong>Web Access</strong></td>
<td><strong>Domain</strong></td>
<td><strong>Function</strong></td>
<td><strong>Description</strong></td>
<td><strong>URL</strong></td>
<td><strong>Contact</strong></td>
</tr>
<tr class="even">
<td>Akenti</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Enables the secure creation and distribution of instructions
authorizing access to distributed resources</td>
<td>Akenti makes access control decisions based on a set of digitally
signed documents that represent the authorization instructions and the
relevant user characteristics. Public-key infrastructure and secure
message protocols provide confidentiality, message integrity, and user
identity authentication, during and after the access decision
process.</td>
<td><a
href="http://www-itg.lbl.gov/Akenti">http://www-itg.lbl.gov/Akenti</a></td>
<td><p><a
href="mailto:pkidev@george.lbl.gov">pkidev@george.lbl.gov</a></p>
<p>William E. Johnston</p>
<p>Lawrence Berkeley National Laboratory</p>
<p>wejohnston@lbl.gov</p>
<p>510-486-5014</p></td>
</tr>
<tr class="odd">
<td>Adifor</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Auto differentiation Service</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Atlas</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>CAVE AV</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>CAVERN</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Immersive Visualization</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>CORBA</td>
<td>Distributed Objects</td>
<td>Distributed Objects</td>
<td>None</td>
<td>Async Shared Access</td>
<td>N/A</td>
<td>All</td>
<td>Object Management</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Datorr</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>DAGH</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Enables parallel implementation of adaptive mesh refinement
algorithms for solution of partial differential equations.</td>
<td>DAGH is an infrastructure for parallel implementation of adaptive
mesh refinement (AMR) algorithms for solution of partial differential
equations. DAGH (Directed Acyclic Hierarchy of Grids) implements
definition, declaration and operations on families of structured grids.
A full set of operations for implementation of Berger-Oliger AMR is
provided including refinement and coarsing, application of stencils,
maintenance of shadow hierarchies, etc. DAGH also provides an extensive
set of operations for parallel implementation of multigrid
algorithms.</td>
<td><a
href="http://www.cs.utexas.edu/users/dagh/ch4.html">http://www.cs.utexas.edu/users/dagh/ch4.html</a></td>
<td><p>Jim Browne, University of Texas at Austin</p>
<p><a
href="mailto:browne@cs.utexas.edu">browne@cs.utexas.edu</a></p></td>
</tr>
<tr class="even">
<td>DRST</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><strong>Name</strong></td>
<td><strong>Computing Model</strong></td>
<td><strong>Data Model</strong></td>
<td><strong>Displ Model</strong></td>
<td><strong>Collab Model</strong></td>
<td><strong>Web Access</strong></td>
<td><strong>Domain</strong></td>
<td><strong>Function</strong></td>
<td><strong>Description</strong></td>
<td><strong>URL</strong></td>
<td><strong>Contact</strong></td>
</tr>
<tr class="even">
<td>Emerge</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Common search mechanism across data types</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Globus</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Metacomputing Toolkit</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Habanero</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Shared event Java collaboration system</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>HDF</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Data Format description and I/O library</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Jini</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><p>Resource registration and discovery.</p>
<p>Jini technology enables spontaneous networking of a wide variety of
hardware and software - anything that can be connected.</p></td>
<td>The Jini technology is potentially very useful in the construction
of scientific workbenches and other problem solving environments (PSEs).
First, Jini is runs on any platform that supports a Java VM. Second,
Jini's service-based architecture can give PSEs great flexibility. A PSE
could use any service it could discover and access, so its functionality
is easily made dynamic. Then, services developed for one purpose could
be used elsewhere, so redundant development is reduced. Finally, Jini
could be used to make existing legacy programs visible and usable over
the network.</td>
<td><a
href="http://java.sun.com/products/jini">http://java.sun.com/products/jini</a></td>
<td></td>
</tr>
<tr class="odd">
<td>Moss</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Enables analysts to steer computations using external
agents…Near-object steering system</td>
<td>Toolkit for instrumenting and remotely steering scientific
applications.</td>
<td><a
href="http://www.cc.gatech.edu/systems/projects/MOSS/">http://www.cc.gatech.edu/systems/projects/MOSS/</a></td>
<td><p>Karsten Schwan</p>
<p>Georgia Institute of Technology</p>
<p><a
href="mailto:schwan@cc.gatech.edu">schwan@cc.gatech.edu</a></p></td>
</tr>
<tr class="even">
<td>MPI-IO</td>
<td>Distributed w/Message Passing</td>
<td>Distributed</td>
<td>N/A</td>
<td></td>
<td></td>
<td></td>
<td>Parallel I/O</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Neos</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Web-based (network) optimization service</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>NetSolve</td>
<td>Network Server w/agents</td>
<td>Xmitted from client</td>
<td></td>
<td>Not</td>
<td>Yes</td>
<td>Linear Algebra</td>
<td>Network Server for Linear Algebra</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Numerical Libraries</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 14%" />
<col style="width: 15%" />
<col style="width: 12%" />
<col style="width: 14%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>Name</strong></td>
<td><strong>Computing Model</strong></td>
<td><strong>Data Model</strong></td>
<td><strong>Displ Model</strong></td>
<td><strong>Collab Model</strong></td>
<td><strong>Web Access</strong></td>
<td><strong>Domain</strong></td>
<td><strong>Function</strong></td>
<td><strong>Description</strong></td>
<td><strong>URL</strong></td>
<td><strong>Contact</strong></td>
</tr>
<tr class="even">
<td>PETSc</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><p>Numerical Library</p>
<p>Parallel software libraries for application developers porting legacy
serial Fortran 77 or C codes or constructing new applications.</p></td>
<td>The PETSc library offers a powerful means to exploit
state-of-the-art algorithms and parallel computing. Porting a full PDE
application code to the distributed-memory parallel environment can
require multiple person-months. However, parallel software libraries can
ease this transition for porting codes and for constructing new
applications. The Portable, Extensible Toolkit for Scientific
Computation (PETSc) has evolved rapidly and many serial codes can now be
ported to distributed-memory architectures using this library. Much of
the application-specific portions of numerical simulations, representing
the highest value of legacy serial codes in Fortran 77 or C, can be
carried over without serious modification.</td>
<td></td>
<td><p>William Gropp</p>
<p>Argonne National Laboratory</p>
<p>630-252-4318</p>
<p><a href="mailto:gropp@mcs.anl.gov">gropp@mcs.anl.gov</a></p></td>
</tr>
<tr class="odd">
<td>SCALAPAK</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Numerical Library</td>
<td>ScaLAPACK is a library of high-performance linear algebra routines
for distributed-memory message-passing MIMD computers and networks of
workstations supporting PVM or MPI. It contains routines for solving
systems of linear equations, least squares problems, and eigenvalue
problems. The goals are efficiency, scalability, reliability (including
error bounds), , flexibility (enabling new routine construction from
well-designed parts), and ease-of-use.</td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><strong>Name</strong></td>
<td><strong>Computing Model</strong></td>
<td><strong>Data Model</strong></td>
<td><strong>Displ Model</strong></td>
<td><strong>Collab Model</strong></td>
<td><strong>Web Access</strong></td>
<td><strong>Domain</strong></td>
<td><strong>Function</strong></td>
<td><strong>Description</strong></td>
<td><strong>URL</strong></td>
<td><strong>Contact</strong></td>
</tr>
<tr class="odd">
<td>Security Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Tango</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Shared event Java collaboration system</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>VisAD</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Numerical display model of distributed objects</td>
<td>VisAD is a Java Class Library for developing collaborative and
interactive applications for visualizing and analyzing numerical data.
VisAD features a flexible data model that can be applied to virtually
any numerical data, and support for distributed computing via Java RMI.
Together these make it easy to share data between different computers,
between different data sources and between different disciplines. They
also make it easy for geographically remote users to share user
interfaces for collaborative visualization and analysis. VisAD is
designed to empower developers to easily create distributed numerical
applications.</td>
<td><a
href="http://www.ssec.wisc.edu/~billh/visad.html">http://www.ssec.wisc.edu/~billh/visad.html</a></td>
<td><p>William Hibbard</p>
<p>University of Wisconsin</p>
<p>608-263-4427</p>
<p><a
href="mailto:whibbard@macc.wisc.edu">whibbard@macc.wisc.edu</a></p></td>
</tr>
<tr class="even">
<td>WebFlow</td>
<td>Distributed objects</td>
<td></td>
<td>Java Applet</td>
<td>Yes</td>
<td>Yes</td>
<td>Distrib. Method Comp.</td>
<td>Distributed Computing with dataflow</td>
<td>The WebFlow framework is a Web browser based interface and a uniform
point of interactive control for cross-platform computational modules
and applications. Distributed meta-applications can be composed
dynamically from reusable components by clicking on visual module icons,
dragging them into the active WebFlow editor area, and drawing the
required connection lines. Modules are executed using Globus-optimized
components or commodity services</td>
<td><a
href="http://www.npac.syr.edu/users/haupt/WebFlow/demo.html">http://www.npac.syr.edu/users/haupt/WebFlow/demo.html</a></td>
<td>Tomasz Haupt</td>
</tr>
</tbody>
</table>

**Chem Viz -- EOT uses it; Chemical Eng. uses same CGI code form Bio
Workbench; BIMA software AIPS++, data analysis, remote control feedback
loops, metadata archives; UMinn viz pkg. LCSE viz pkg ;Nanomaterials;
CAVE 5D; Cactus; Streamed Dataflow; Moss**

**Tafti:** PSE has to be app specific because each app has different
req. the PSE enables each app to do what it wants to do. Has to be
simple to use, low overhead in trying to figure out what going on. The
questions we must answer are: What is app interface.....What are
building blocks?

**Elder:** There may be missing, lower level abstractions.... Is there a
lower level display abstraction that we need to bring up the ability for
a PDE to support various display platforms?

**Reed:** Sure for instance there is no QOS that would trade audio for
video.

The PSE should for instance take an application wrapped in CORBA or Java
and sit between it and the lower levels of the Grid. Facilitate workflow
going from one code to another. Data from one code would go into the
other

**Reed:** We need to make concrete progress.

**Hibbard:** ORBs and Java -- Frequency and cost of using such tools set
limitations on their usage.

**Fox:** By separating the need to do something and the doing of it you
can implement in Java even things that require moving lots of data
around

**Elder:** Produce a web page summarizing the tools and their
capabilities: go to each AT team and ask how one could build a
portal/PSE for that application.

**Fox:** On back end there are dataset compute services, which are
abstracted as distributed objects, and then there are a lot of compute
services and viz services.... Need a serious viz system.

Level Below: documentation of all the APIs if you want people to build
new services you want them to build them of composable components

1\. Get everyone talking the same arch

2\. Build in a set of services

3\. What toolkits and services are needed to build applications?

**Elder:** Want to build a web page that tells when which tool is most
appropriate and what it does well

Accounting mechanisms are missing

**Fox:** Have 4 talks on tech: Visualization; Distributed Objects;
Backend service

**Elder:** How do you know when you have a whole PSE. What are the
common services that are available?

**Fowler:** There was a need identified in Houston for determining how
you go about capturing expertise so that experts are connected with the
process without having to interact with each person needing to tap his
knowledge.

**Tafti:** If we try to do everything at once it could go on forever. In
the short term, should we take something that is there and do more with
it?

Chemical Engineering workbench is starting to do interesting things with
Globus. To see something happening in the short term something like that
would be good to show off. Bill Hibbard is in Team C and Environmental.
Hydrology

**Fox:** Need a fancy named strategy defined in a document and then need
to map these various toolkit components into the strategy

***Interface Working Group*** -- evaluate existing combinations of PSE
components to distill elements of extant interfaces that work well and
could potentially be generalized. Apply that knowledge in proposing a
specification of a generalized PSE interface.

+-----+--------------+----------+---------+-------+----+-----+------+
|     | **Vision &   | **S      | **Archi | **    | *  | *   | **Ev |
|     | Concept**    | cenarios | tecture | Techn | *I | *Ap | alua |
|     |              | and      | and     | ology | nt | pli | tion |
|     |              | Requir   | D       | Dev   | eg | cat | and  |
|     |              | ements** | esign** | elopm | ra | ion | Doc  |
|     |              |          |         | ent** | ti | Dem | umen |
|     |              |          |         |       | on | ons | tati |
|     |              |          |         |       | a  | tra | on** |
|     |              |          |         |       | nd | tio |      |
|     |              |          |         |       | T  | n** |      |
|     |              |          |         |       | es |     |      |
|     |              |          |         |       | ti |     |      |
|     |              |          |         |       | ng |     |      |
|     |              |          |         |       | ** |     |      |
+-----+--------------+----------+---------+-------+----+-----+------+
| Re  | Gregor von   | 1\.      | 1\.     | 1     | M  | H   |      |
| spo | Laszewski    | Private  | Object  | Group | ay | DF, |      |
| nsi |              | needs    | model   | b     |  - | Vis |      |
| ble | Bill Hibbard | analysis |         | uilds | Au | AD, |      |
| P   |              | in       | 2\.     | API   | gu | and |      |
| art | Thomas Haupt | cons     | Objects |       | st | M   |      |
| ies |              | ultation | have to | 2     |    | oss |      |
|     | Beth Plale   | with AT  | c       | An    |    | in  |      |
|     |              | groups.  | onnect: | other |    | teg |      |
|     | Danesh Tafti |          | int     | group |    | rat |      |
|     | for AT       | 2\.      | erfaces | puts  |    | ion |      |
|     | nominee to   | Evaluate | match   | wra   |    | and |      |
|     | be named     | existing | so that | ppers |    | int |      |
|     | later        | comb     | the     | a     |    | erf |      |
|     |              | inations | right   | round |    | ace |      |
|     | HDF draftee  | of PSE   | info    | API   |    | de  |      |
|     |              | co       | rmation |       |    | vel |      |
|     | Rob Fowler   | mponents | per     | 3     |    | opm |      |
|     | for Team A   | to       | colates | Third |    | ent |      |
|     |              | distill  | both up | group |    | in  |      |
|     |              | elements | and     | con   |    | the |      |
|     |              | of       | down.   | nects |    | c   |      |
|     |              | extant   |         | ap    |    | ont |      |
|     |              | in       | 3\.     | plica |    | ext |      |
|     |              | terfaces | S       | tions |    | of  |      |
|     |              | that     | eparate | to    |    | E   |      |
|     |              | work     | co      | wra   |    | nvi |      |
|     |              | well and | mponent | ppers |    | ron |      |
|     |              | could    | w       |       |    | men |      |
|     |              | pot      | rapping | Evol  |    | tal |      |
|     |              | entially | from    | ution |    | Hyd |      |
|     |              | be       | const   | of    |    | rol |      |
|     |              | gene     | ruction | point |    | ogy |      |
|     |              | ralized. | of the  | solu  |    | wor |      |
|     |              |          | w       | tions |    | kbe |      |
|     |              | 3\.      | rappers | must  |    | nch |      |
|     |              | Apply    | and the | lead  |    |     |      |
|     |              | that     | use of  | to    |    |     |      |
|     |              | k        | wrapped | ge    |    |     |      |
|     |              | nowledge | com     | neral |    |     |      |
|     |              | in       | ponents | solut |    |     |      |
|     |              | p        | to      | ions. |    |     |      |
|     |              | roposing | build   |       |    |     |      |
|     |              | a        | PSEs    |       |    |     |      |
|     |              | speci    |         |       |    |     |      |
|     |              | fication |         |       |    |     |      |
|     |              | for a    |         |       |    |     |      |
|     |              | gen      |         |       |    |     |      |
|     |              | eralized |         |       |    |     |      |
|     |              | PSE      |         |       |    |     |      |
|     |              | in       |         |       |    |     |      |
|     |              | terface. |         |       |    |     |      |
+-----+--------------+----------+---------+-------+----+-----+------+
| C   | A living     |          |         |       |    |     |      |
| omm | document     |          |         |       |    |     |      |
| uni | outlining    |          |         |       |    |     |      |
| cat | interface    |          |         |       |    |     |      |
| ion | sp           |          |         |       |    |     |      |
| P   | ecifications |          |         |       |    |     |      |
| lan | being        |          |         |       |    |     |      |
|     | proposed,    |          |         |       |    |     |      |
|     | guidelines   |          |         |       |    |     |      |
|     | for          |          |         |       |    |     |      |
|     | integrating  |          |         |       |    |     |      |
|     | component    |          |         |       |    |     |      |
|     | technology & |          |         |       |    |     |      |
|     | building     |          |         |       |    |     |      |
|     | workbenches. |          |         |       |    |     |      |
+-----+--------------+----------+---------+-------+----+-----+------+
| Do  | Draft Due by | How do   |         |       |    |     |      |
| cum | March 15     | we make  |         |       |    |     |      |
| ent |              | things   |         |       |    |     |      |
| P   |              | work     |         |       |    |     |      |
| rep |              | together |         |       |    |     |      |
| P   |              | allowing |         |       |    |     |      |
| lan |              | openness |         |       |    |     |      |
|     |              | yet      |         |       |    |     |      |
|     |              | defining |         |       |    |     |      |
|     |              | a        |         |       |    |     |      |
|     |              | top-down |         |       |    |     |      |
|     |              | f        |         |       |    |     |      |
|     |              | ramework |         |       |    |     |      |
|     |              | so that, |         |       |    |     |      |
|     |              | as new   |         |       |    |     |      |
|     |              | tools    |         |       |    |     |      |
|     |              | appear,  |         |       |    |     |      |
|     |              | they can |         |       |    |     |      |
|     |              | be       |         |       |    |     |      |
|     |              | absorbed |         |       |    |     |      |
|     |              | into the |         |       |    |     |      |
|     |              | infrast  |         |       |    |     |      |
|     |              | ructure? |         |       |    |     |      |
+-----+--------------+----------+---------+-------+----+-----+------+
| M   | ET/AT        | Fox is   |         |       |    |     |      |
| eet | meeting in   | hosting  |         |       |    |     |      |
| ing | Early April  | a        |         |       |    |     |      |
| p   |              | meeting  |         |       |    |     |      |
| lan | 1\. Quick    | Feb. 15  |         |       |    |     |      |
|     | p            | &16 to   |         |       |    |     |      |
|     | resentations | get      |         |       |    |     |      |
|     | describing   | c        |         |       |    |     |      |
|     | extant       | onsensus |         |       |    |     |      |
|     | tools,       | as to    |         |       |    |     |      |
|     | functions,   | what     |         |       |    |     |      |
|     | and contacts | open     |         |       |    |     |      |
|     |              | in       |         |       |    |     |      |
|     | 2\. Quick AT | terfaces |         |       |    |     |      |
|     | team         | should   |         |       |    |     |      |
|     | p            | be       |         |       |    |     |      |
|     | resentations | su       |         |       |    |     |      |
|     | on workbench | pported. |         |       |    |     |      |
|     | specs        |          |         |       |    |     |      |
|     |              |          |         |       |    |     |      |
|     | 3\. Present  |          |         |       |    |     |      |
|     | Document --  |          |         |       |    |     |      |
|     | how          |          |         |       |    |     |      |
|     | components   |          |         |       |    |     |      |
|     | will be      |          |         |       |    |     |      |
|     | integrated,  |          |         |       |    |     |      |
|     | interface    |          |         |       |    |     |      |
|     | arch         |          |         |       |    |     |      |
|     | description  |          |         |       |    |     |      |
|     | and          |          |         |       |    |     |      |
|     | i            |          |         |       |    |     |      |
|     | llustration. |          |         |       |    |     |      |
|     | Response to  |          |         |       |    |     |      |
|     | AT teams     |          |         |       |    |     |      |
|     | specs.       |          |         |       |    |     |      |
|     |              |          |         |       |    |     |      |
|     | 4\. Working  |          |         |       |    |     |      |
|     | groups on    |          |         |       |    |     |      |
|     | interfaces   |          |         |       |    |     |      |
|     | and          |          |         |       |    |     |      |
|     | workbenches  |          |         |       |    |     |      |
+-----+--------------+----------+---------+-------+----+-----+------+
| Sc  | Complete     |          |         |       |    |     |      |
| hed | document     |          |         |       |    |     |      |
| ule | revision and |          |         |       |    |     |      |
| of  | start        |          |         |       |    |     |      |
| eve | im           |          |         |       |    |     |      |
| nts | plementation |          |         |       |    |     |      |
|     | of interface |          |         |       |    |     |      |
|     | by May 1.    |          |         |       |    |     |      |
|     | Prototype    |          |         |       |    |     |      |
|     | im           |          |         |       |    |     |      |
|     | plementation |          |         |       |    |     |      |
|     | with         |          |         |       |    |     |      |
|     | Hydrology    |          |         |       |    |     |      |
|     | application  |          |         |       |    |     |      |
|     | in mid April |          |         |       |    |     |      |
+-----+--------------+----------+---------+-------+----+-----+------+
| Ap  | All AT teams |          |         |       |    |     |      |
| pli | during       |          |         |       |    |     |      |
| cat | interface    |          |         |       |    |     |      |
| ion | sp           |          |         |       |    |     |      |
| p   | ecification. |          |         |       |    |     |      |
| art | E            |          |         |       |    |     |      |
| ici | nvironmental |          |         |       |    |     |      |
| pat | Hydrology    |          |         |       |    |     |      |
| ion | for point    |          |         |       |    |     |      |
|     | case.        |          |         |       |    |     |      |
+-----+--------------+----------+---------+-------+----+-----+------+
| Add | Integration  |          |         |       |    |     |      |
| Res | of ET and AT |          |         |       |    |     |      |
| our | activities.  |          |         |       |    |     |      |
| ces | Need a clear |          |         |       |    |     |      |
| &   | process for  |          |         |       |    |     |      |
| Exp | advertising  |          |         |       |    |     |      |
| ert | what's       |          |         |       |    |     |      |
| ise | possible for |          |         |       |    |     |      |
|     | AT           |          |         |       |    |     |      |
+-----+--------------+----------+---------+-------+----+-----+------+

###### White Board Notes

##### Tasks

Look at Jini to see how useful it is

Divide into subgroups

Develop webpage

Initiate distributed training in PSE toolkits

##### Decisions

1\. Basic Architecture: Object Model (interface, wrap, PSE)

2\. ET/AT Discussions to deconstruct what is working now and education
regarding current technology

3\. Demonstrate a point solution using the general model

4\. Develop the general model -- a strategy for process of developing
component technology

5\. Drill down on point examples

##### Short Term

Lower level services supporting application specific functionality
(dataflow, viz, software install, data standardization)

Structural and semantic

Missing: security, charging, other accounting, the ability to capture
"institutional expertise"

Services: scheduling, compilation

##### PSE Scenario

1\. Multidisciplinary models

2\. coupling

3\. Fused visualizations

4\. Distributed collaboration

5\. Collaborative software development plus woftware development mode
(PSEs)

6\. Information archives