# Presentation: 369990

## Virtual Dataand the Chimera System

- Concept by Foster, Deelman, Kesselman, Livny
- Chimera System work of Foster, Voeckler, Wilde, Zhao
- Planner work by Deelman, Mehta, Vahi

- Petascale Data Quest – Argonne, October 1, 2002

## Overview

- Problem
- Managing programs and computations as community resources
- Technology
- Chimera virtual data system
- Applications
- Virtual Data ≠ Virtual Concept!
- Futures
- Research challenges & plans

## Overview

- Problem
- Managing programs and computations as community resources
- Technology
- Chimera virtual data system
- Applications
- Virtual Data ≠ Virtual Concept!
- Futures
- Research challenges & plans

## Programs as Community Resources:Data Derivation and Provenance

- Most [scientific] data are not simple “measurements”; essentially all are:
- Computationally corrected/reconstructed
- And/or produced by numerical simulation
- And thus, as data and computers become ever larger and more expensive:
- Programs are significant community resources
- So are the executions of those programs
- Management of the transformations that map between datasets an important problem

## Motivations (1)

- Transformation

- Derivation

- Data

*product-of*

*execution-of*

*consumed-by/*
*generated-by*

- “I’ve detected a calibration error in an instrument and want to know which derived data to recompute.”

- “I’ve come across some interesting data, but I need to understand the nature of the corrections applied when it was constructed before I can trust it for my purposes.”

- “I want to search an astronomical database for galaxies with certain characteristics. If a program that performs this analysis exists, I won’t have to write one from scratch.”

- “I want to apply an astronomical analysis program to millions of objects. If the results already exist, I’ll save weeks of computation.”

## Motivations (2)

- Data track-ability and result audit-ability
- Universally sought by GriPhyN applications
- Facilitates tool and data sharing and collaboration
- Data can be sent along with its recipe
- Repair and correction of data
- Rebuild data products—c.f., “make”
- Workflow management
- A new, structured paradigm for organizing, locating, specifying, and requesting data products
- Performance optimizations
- Ability to re-create data rather than move it

## Overview

- Problem
- Managing programs and computations as community resources
- Technology
- Chimera virtual data system
- Applications
- Virtual Data ≠ Virtual Concept!
- Futures
- Research challenges & plans

## Virtual data catalog
Transformations, derivations, data
Virtual data language
Catalog Definitions
Query Tool
Applications include browsers and data analysis applications

- Transformations, derivations, data
- Virtual data language
- Catalog Definitions
- Query Tool
- Applications include browsers and data analysis applications

- Chimera Virtual Data System

## Virtual data catalog
Transformations, derivations, data
Virtual data language
Catalog Definitions
Query Tool
Applications include browsers and data analysis applications

- Transformations, derivations, data
- Virtual data language
- Catalog Definitions
- Query Tool
- Applications include browsers and data analysis applications

- Chimera Virtual Data System

## Transformations and Derivations

- Transformation
- Abstract template of program invocation
- Similar to "function definition"
- Derivation
- Formal invocation of a Transformation
- Similar to "function call"
- Store past and future:
- A record of how data products were generated
- A recipe of how data products can be generated
- Invocation (future)
- Record of each Derivation execution

## Virtual Data Catalog Structure

**Notes:**
Feel free to skip.

## Virtual Data Tools

- Virtual Data API
- A Java class hierarchy to represent transformations and derivations
- Virtual Data Language
- Textual for people & illustrative examples
- XML for machine-to-machine interfaces
- Virtual Data Database
- Makes the objects of a virtual data definition persistent
- Virtual Data Service
- Provides a service interface (e.g., OGSA) to persistent objects

## Virtual Data Language: XML

**Notes:**
Feel free to skip.

## Example Transformation

- TR t1( out a2, in a1, none pa = "500", none env = "100000" ) {
-   profile hints.exec-pfn = "/usr/bin/app3";
-   argument = "-p "${pa};
-   argument = "-f "${a1};
-   argument = "-x –y";
-   argument stdout = ${a2};
-   profile env.MAXMEM = ${env};
- }

- $a1

- $a2

- t1

## Example Derivations

- DV d1->t1 (env="20000", pa="600",a2=@{out:run1.exp15.T1932.summary},a1=@{in:run1.exp15.T1932.raw},
- );
- DV d2->t1 (a1=@{in:run1.exp16.T1918.raw},a2=@{out.run1.exp16.T1918.summary}
- );

## Managing Dependencies

- TR tr1( out a2, in a1 ) {
-     profile hints.exec-pfn = "/usr/bin/app1";
-     argument stdin = ${a1};
-     argument stdout = ${a2}; }
- TR tr2( out a2, in a1 ) {
-     profile hints.exec-pfn = "/usr/bin/app2";
-     argument stdin = ${a1};
-     argument stdout = ${a2}; }
- DV x1->tr1( a2=@{out:file2}, a1=@{in:file1});
- DV x2->tr2( a2=@{out:file3}, a1=@{in:file2});

- file1

- file2

- file3

- x1

- x2

**Notes:**
Explicit dependencies.

## Initial “Strawman” Architecture(Use of GriPhyN Virtual Data Toolkit)

- VDLx

- abstract
- planner

- DAX

- DAGMan

- concrete
- planner

**Notes:**
The essence is in the right-most flow.

## Virtual Data Usage Model

- _Transformation designers_ create programmatic abstractions
- Simple or compound; augment with metadata
- _Production managers_ create bulk derivations
- Can materialize data products or leave virtual
- _Users_ track their work through derivations
- Augment (replace?) the scientist’s log book
- Definitions can be augmented with metadata
- The key to intelligent data retrieval
- Issues relating to metadata propagation

## Virtual Data Process

## Overview

- Problem
- Managing programs and computations as community resources
- Technology
- Chimera virtual data system
- Applications
- Virtual Data ≠ Virtual Concept!
- Futures
- Research challenges & plans

## Chimera Application: Sloan Digital Sky Survey Analysis

- Size distribution of
- galaxy clusters?

- Chimera Application: Sloan Digital Sky Survey Analysis

## Cluster-finding Data Pipeline

## Cluster-Finding Pipeline Execution

**Notes:**
This is monitoring through log-file-analysis!

## Small SDSS Cluster-Finding DAG

**Notes:**
43 nodes
Example DAG, smallest case; real monsters of 400+ are NOT fully connected!
Complete stripe is 2000+ nodes

## And Even Bigger:744 Files, 387 Nodes

- 108

- 168

- 60

- 50

## Overview

- Problem
- Managing programs and computations as community resources
- Technology
- Chimera virtual data system
- Applications
- Virtual Data ≠ Virtual Concept!
- Futures
- Research challenges & plans

## Virtual Data Research Issues

- Representation
- Metadata: how is it created, stored, propagated?
- Datasets and Type Model
- What knowledge must be represented? How?
- Capturing notions of data approximation
- VDC as a community resource
- Automating data capture
- Access control, sharing and privacy issues
- Quality control
- Data derivation
- Query estimation and request planning

## Hyperlinked Catalogs

## Virtual Data Research Issues

- “Engineering” issues
- Dynamic (runtime-computed) dependencies
- Large dependent sets
- Extensions to other data models: relational, OO
- Virtual data browsers
- XML vs. relational databases & query languages
- Additional usage modalities
- E.g., meta-analyses, automated experiment generation, “active notebooks”
- Virtual data browsers, editors

## Status of Chimera R&D

- Early virtual data system demonstrated Nov ’01: HEP collision simulations
- Larger scale problems addressed recently: “cluster finding” in SDSS
- First public release in June: Chimera v1.0
- Enhancements planned throughout the summer
- Physics & astronomy applications by SC’02
- Future R&D focus #1: request planning
- Future R&D focus #2: knowledge representation
- Future apps: bioinformatics, earth sciences

## Related Work

- Data provenance
- Materialized views, lineage: Cui, Widom
- Data provenance tracking: Buneman et al.
- Capturing transformations
- ZOO system and conceptual schema
- Data Grid technologies
- GriPhyN, Globus Project, EU DataGrid

## Summary

- _Concept_: Tools to support management of transformations and derivations as community resources
- _Technology_: Chimera virtual data system including virtual data catalog and virtual data language; use of GriPhyN virtual data toolkit for automated data derivation
- _Results_: Successful early applications to CMS and SDSS data generation/analysis
- _Future_: Public release of prototype, new apps, knowledge representation, planning

## For More Information

- GriPhyN project (NSF ITR funded)
- www.griphyn.org
- Chimera virtual data system
- www.griphyn.org/chimera
- “Chimera: A Virtual Data System for Representing, Querying, and Automating Data Derivation,” SSDBM, July 2002
- “Applying Chimera Virtual Data Concepts to Cluster Finding in the Sloan Sky Survey”, SC’02, November 2002.