Report from Working Group C-2

Michael WrightPete BeckmanReagan Moore

Jorge MoréJim Myers

Michael O’KeefeGary Roediger

Vicky WhiteChristine Yang

We learned a lot!

Whether or not we have produced anything of value to the rest of the group, we each have a much better understanding for ourselves of how the components of the DOE2000 program fit together and how they have many common needs.

Recurring Theme in Discussions

To collaborate (or interoperate) we need information. Our biggest barrier is the difficulty of finding all the relevant information we need in order to use a tool or to work together ourselves.

Integration, Integration, Integration

Integration is going to require that we make metadata generated by the various tools generally available in a common manner outside of / between tools.

Use Cases

Validate large data sets using information on software tools and signed test datasets in libraries

Alert users of a dataset of a new “limitation” based on new discoveries about software used in processing it

Graphically link several tools to create/analyze/visualize/record data

Route data for signatures, validation, and automatically route from notebook to library

Similar needs exist for component software development

What are capabilities of a component in terms of platform, expected error, scaling, memory, performance characteristics

What are effects of code modifications on above capabilities

This is much more than just a version control system

Information Workflow (metadata categories)

Data Workflow CCA, CPSEs

Software Workflow Software development Data Validation

Records/Legal Workflow Notebooks Digital Libraries

Collaboration Workflow session setup business workflow

Scientific Workflow processing history CPSEs

Metadata Middleware

Metadata definition attributes relationships (e.g. collections) notifications

Metadata extractionMetadata translationMetadata discovery (e.g. agents)Metadata Engine/RepositoryMetadata driven tools

(new tools, integration of existing tools)

(Graphical) Workflow definition tools

Recommended actions

Formalize development of metadata middleware in a new group/metagroup

Metadata definition projects for data, software, records, …

Verify that groups are working together

Support

Not everything should be deployed and supported, but

Research ->PrototypeReview PrototypeIf yes, fund pilot deploymentReview pilotIf yes, fund deployment/supportAssumed - feedback to researchers at

each stage of development

Other needs we identified, some current, some new

Common Component Architecture Automatic differentiation tools

tools for computing derivatives, sensitivity, …

Visualization framework need data descriptors

Algorithm development Preconditioning interfacesEquation solver interface

Collaboration Issues from Point of View of a Potential User

Collaborative visualizationKeeping track of data sets

later annotations to data sets as people use them for research

Unencumbered softwareVideoconferencing deployment should be

integrated into tools

Tool deploymentIndexing/directory service to locate

metadata/datapersistence of data -> how to handle?

Important topics for impact on user community

Facilitate deployment install, support, licensing, platforms interfaces to other tools

Security enable access legal aspects (notebooks) need something stable and supportable single security context

The tools needed for DOE2000 are useful for SSI but need to be enhanced to provide:development / hardeningdeployment / supporthigher performance versions

processing speed large scale data sets

MICS SSI/CSET Research Hardened Tools

Q: What can support SSI?A: Lots of things!

DOE 2000 can supply to SSI:

Tools forbuilding more sophisticated applications

components, not monolithic

data management, information handling abstractions security infrastructure where does data live

Visualization framework

Interaction with other agencies

See last two slides from Group M-2!

Quote from Group A-1: “Interagency cooperation works best from the

bottom up rather than the top down.”