# Presentation: 116061

## MEAD

- Modeling Environment for Atmospheric Discovery

**Co-Leads**
**Sara Graves**
**Bob Wilhelmson**

- _[http://www.](http://www.ncsa.uiuc.edu/expeditions/MEAD/)__[ncsa](http://www.ncsa.uiuc.edu/expeditions/MEAD/)__[.](http://www.ncsa.uiuc.edu/expeditions/MEAD/)__[uiuc](http://www.ncsa.uiuc.edu/expeditions/MEAD/)__[.](http://www.ncsa.uiuc.edu/expeditions/MEAD/)__[edu](http://www.ncsa.uiuc.edu/expeditions/MEAD/)__[/expeditions/MEAD/](http://www.ncsa.uiuc.edu/expeditions/MEAD/)_

## The Six Expeditions

- Performance Engineering for Clusters and Grids
- 	a)  node performance tuning
- 	b)  parallel system performance
- 	c)  grid performance optimization
- Community Application Codes
- 	a)  AIPS++
- 	b)  Galaxy Quest
- 	c)  Gromacs++
- 3)  Petascale Data Quest
- 	a)  Radio Astronomy
- 	b)  Bioinformatics
- 	c)  Virtual Astronomy
- 	d)  GriPhyN Applications
-  	e)  MEAD

## The Six Expeditions

- 4)  Scientific Portals
- 	a)  core portal technology
- 	b)  chemical engineering
- 	c)  MEAD
- 	d)  radio astronomy
- 5)  Scientific Workspaces
- 	a)  collaborative problem solving
- 	b)  large scale scientific visualization
- 	c)  software integration
- 6)  MEAD
- 	a)  workflow
- 	b)  data management
- 	c)  ensemble services

## MEAD Workshop Presentations

- _[Expedition Overview](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/MEADintro.ppt)_ (Wilhelmson)
- _[Scientific Scenarios](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/Mead0902-Jewett.ppt)_ (_Jewett_)
- _[Ensemble Evaluation](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/ensemble.ppt)_ (_Ramamurthy_)
- _[DTF and ETF](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/ETF-for-MEAD.ppt)_ (Towns)
- _[WRF/IA64 Update](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/WRFIA64Update.ppt)_ (Straka)
- _[ROMS/Coupling](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/ROMS/MEAD_Fall02.ppt)_ (Haidvogel)
- _[ROMS/SMS](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/ROMS/mead_kickoff.ppt)_ (Schaffer/Henderson)
- _[Performance/Scheduling](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/anirban-mead-final.ppt)_ (Mandal/Fowler)
- _[Prophesy: Performance Analysis & Modeling](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/Prophesy.ppt)_ (*Taylor*)
- _[The Model Coupling Toolkit](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/MCToverview.ppt)_ (Jacob)
- _[WRF architecture](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/WRFarch.ppt)_ (Michalakes)
- _[HDF5](http://verbena.ncsa.uiuc.edu/MEAD)_ (McGrath/Yang/Folk)
- _[NCOMMAS](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/NCOMMAS.pdf)_ (Anderson)
- _[Fault Tolerant Computing](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/NCSA-MEAD-Wkshop-9-18-02.ppt)_ (Woodward)

- Portal Interface (Weber)
- Workflow (*Rossi*)
- _[Data Management](http://www.ncsa.uiuc.edu/expeditions/MEAD/meeting2002/XMLDMWS1.ppt)_ (*Hampton*)
- Petascale Data Quest Expedition (*Hefedova/Foster*)
- ESML/Feature Detection (Graves)
- D2K (Welge)
- ADaM (Graves)
- _High Dimensional Machine Learning_ (York/Isbell/Husbands)
- Volume Visualization (*Porter*)
- Wall/Stereo/Visbench Visualization (Semeraro)
- _NCL/NCAR Graphics_ (Don Middleton)
- Education (_Bramer_)
- _Collaborative Science_ (*Stevens*)

**Notes:**
Red are MEAD Alliance funded personnel
Italics are Alliance funded personnel from other expeditions
Underlined are NCSA Faculty Fellow and EOT funded participants

## MEAD Participant Locations

## MEAD Meeting 9/18-19/2002

## Community Models

**WRF Model (Weather Research and Forecasting)**
**ROMS Model (Regional Ocean Modeling System)**
**Coupled WRF/ROMS Model**
**D2K (Data to Knowledge)**
**ADaM (Algorithm Development and Modeling System)**
**Visualization Engines**

## Scientific Scenarios:   Storm Interaction Study

*Jacksonville, IL tornado (F2)*

- Real World

- Model

- Real World

*1 km MM5, real data initialization*

- Jewett and Wilhelmson

_**April 1996 Tornado Outbreak**_

## Simulation Suite

*Looking north*

*1 km MM5*

***232 simulations: storm positions***

- This suite explores only *one*set of parameters defining cell interaction.

*Not*:
- Cell age
- Cell size
- Cell intensity
- Cell rotation

- secondary cell position varies as shown

## Simple Analysis: Comparison of Pairs of Runs

*Looking north*

*1 km MM5*

*2 km rainwater (fill), vorticity (contour)*

## Simple Analysis: Properties of All Runs

*Looking north*

*1 km MM5*

## Scientific Scenarios:  Hurricane Ensembles

- Cost to evacuate populated coastline:*$1 million per mile*.
- Hurricane Floyd resulted in the largest peacetime evacuation in U. S. history
- The USWRP estimates that a 20% reduction in coastline warning area would save $80 million in preparation costs.

- Ramamurthy and Jewett

## What is an Ensemble?

**A set of multiple predictions valid at the **
**same time***** ***
***generated from reasonably different initial conditions and/or with various credible versions of models***
***improves skill through averaging among the forecasts, which eliminates non-predictable components ***
***provides reliable information on forecast uncertainties (e.g., probabilities) from the spread (diversity) amongst ensemble members**** *

## Determining Possible Scenarios

- Initial uncertainty
- = distribution of possible initial states

**Best single deterministic forecast**

**verification**

**Ensemble members**

- Forecast uncertainty
- = distribution of possible forecast states

**Determining Possible Scenarios**

## Selected Ensemble Members

## Workflow

## Grid Computing Environment  Client

-   	The GCE client is primarily used to set up computational jobs, submit the jobs to be run on grid-enabled hosts, and monitor running jobs. It is designed to launch transient web services, coined “Application Manager Web Services”, as the environment for the job to be run on a grid enabled host.

## Application Manager Web Service

## Project Repository Service

** **
**Interface for dealing with Project/Run/Document data and metadata.  The current design of the infrastructure relies heavily on the information store in this repository.   All information about the status of Runs, input/output files, and user preferences flows into and of the repository.  The current implementation uses an XML database for managing the passed in XML data. **

## MEAD Organization & Working Groups

**Modeling **
_**coupling and I/O**_
_**performance/fault tolerance**_
_**Workflow and portal interface**_
**itineraries (fixed, changeable, push and pull)**
**user functionality (e.g. setting model parameters)**
_**Metadata and data management**_** **
**finding data**
**publishing data**
**handling file formats**
**Ensemble services**
_**data mining and machine learning**_
_**visualization**_
_**Education**_

- Working groups are underlined

## Working Groups Co-Leads

**Coupling and I/O (Moore and Michalakes)**
**Workflow and portal interface (Hampton and Weber)**
**Metadata and data management (Alameda and Tanner)**
**Data mining and machine learning (York and Welge)**
**Model and Performance (Taylor and Woodward)**
**Visualization (Porter and Semeraro)**
**Education (Lathrop and Bramer)**

- Co-leads are tentative

## Project Repository Issues

**Use Case Common Themes**
**Registering an executable with a run or set of runs (project).**
**Associating input/output data with a run or project.**
**Must be able to process data which already exists on network disk farms and MSS**
**Must have an automated mechanism for accomplishing the above for future runs**
**Allow for user specified queries ( “Show me all the runs I did last week that had parameter A=15” )**
**Design Goals**
**Easy set-up and administration to allow repository to be set up by research groups.**
**XML In / XML Out**

## Initial Portal/Workflow/Metadata Design

** ****The Run ID is sent to the Broker**
** ****The Broker retrieves the Run Description, selects the  **
**  ****Resources and submits the Run to the Factory**
** ****The Factory requests an Application Manager be created  **
**  ****and submits the Run as requested**
** ****An Application Manager processes the Run and begins  **
**  ****executing the workflow**
** ****The Runtime Monitor handles the output streams**
** ****Output files are stored in a Mass Storage System, the     **
**  ****Application Manager creates Metadata and Location data**
**  ****for the files and registers it with the Repository**
** ****Everything sends Events when necessary**
** ****Everything can listen for Events**** **

**Initial Portal/Workflow/Metadata Design**

**Initial Portal/Workflow/Metadata Design**

## Output From a Nested Grid Storm Model Suite

**All variables in a tile (full and partial tiles) – 12 or more**
**All tiles at a given time – 16 to 64**
**All nests - 3**
**All times – 200 to 500**
**All runs - 100**
**Selected visualizations/animations - ?**
**Selected analysis - ?**
**Additional documentation and use published analysis, datamining results, visualizations, and documentation (e.g., a scientific notebook)**
**1 domain – 256 x 256 x 50 x 12 = **_**39 M Words**_
**All runs with 3 nests and 200 saves = **_**2.34 TeraWords**_
**Metadata entries = 64 x 3 x 200 x 100 = **_**3.8 M**_

## Output From a Hurricane Ensemble

**Data Volume**
- 600 gigabytes per storm (with a grid spacing of 20 km)
- In 3-5 years, most hurricane ensemble predictions will use an inner-grid resolution of 1-2 km, resulting in several tens of terabytes of data!

## Output from a Single Large Simulation

**Billion Zone Simulation**
- 109 x 12 variables x 1000 times x 4 bytes is
**48 Terabytes**
**plus analysis, visualization, and scientific notebook**

## M&DM – Issues & Organization

**Issues**
- How to store and access (including finding relevant info) the large data volumes (e.g. use DODS,.....)
- Interactive distributed (?) parallel metadata searches through and across hugh metadata databases
- What databases to use?
- Organization of runs, projects, groups, ...
- Secure user _publishing_ and access (more than a pipeline) including “user notebook”
- Replica management
- Movement of data chunks between sites for post pipeline services (analysis, data mining, and vis)
- Stable, portable middleware and M&DM related software on platforms starting with the TeraGrid

## Some Details: Data  Structure 

**Only need logical name**
**Application reads, writes to logical name**
**URIs for each individual file**
**5D data: (field, time, data(3d))**** **
**Would specify 2 of these dimensions when accessing**
**Optimize for sequential access**
**Could ask for data subset**
**Other dimensions**
**Run number**
**Tile number**
**Nest number**

_**Initial Suite Output**_

## Some Details – Who?

**Repository - metadata web services**
**Existing; Shawn Hampton (NCSA)**
**Replica catalog - fast access to desired data**
**Stable GT2; C & Java API; LDAP**
**RLS: ******** : RDBMS;**
**(Nobody)**
**Virtual data catalog**
**1.0**** release - *****www.gryphn.org/chimera***
**(Nobody)**
**GRID ftp (assumed to be available)**

## M&DM - Project

**A Project is a container to hold all of the information pertaining to a series of Runs either by a single person or by many.**
**Metadata**
- Name
- ID
- <other specific metadata>
- Name/Value pairs
**Associated runs**
- Links to Run objects
**Associated documents**
- Links to Document objects
- Useful for registering an executable
- Papers
- Reports
- Etc.

## M&DM - Run

**A Run object is a single experiment.**
**A Run can be associated with many Projects or with none.**
**Metadata**
- Name
- ID
- Name/Value pairs
**Associated Documents**
- Input files / data
- Output files / data

## M&DM - Document

**Represents a single file or data set.**
**Can be annotated with metadata pertaining to the run, user, etc.**
**Can contain either the data itself, a URI to a file store, or both.**
**Can be associated with many Projects, many Runs, both, or neither.**