# Presentation: 905485

## Report from HENP Networking Meeting

- Rob Gardner
- Distributed IT Project Manager  /  U.S. ATLAS Collaboration
- Indiana University
- ESNet Coordination Committee Meeting
- Brookhaven National Laboratory
- June 26-28, 2001

## Background

- U.S. LHC Common Software and Computing Projects (January 2001)
- Collaboration between U.S. LHC Software and Computing Projects
- Identify common computing projects, eg.
**Computing Facilities (Regional Centers)**
**Networking**
**Database Technologies**
**Grid Software Projects**
- Strongly endorsed by U.S. LHC Joint Operations Group
- Networking Working Group Formed
- H.Newman, R. Gardner co-Chair
- Initial charter developed;  encouraged to broaden scope to include other HEP experiments as well as NP

## Networking Group

- Mission:
-     Help ensure that the required national and international network infrastructures, monitoring tools and facilities, and collaborative systems, are developed and deployed in time to meet the needs of the US LHC Program, as well as the HEP ( HENP) community.

## Goals and Technical Activities

- Programmatic Requirements
- Use Cases, Analysis models
- Uniform Requirements Definition
- Cost Models
- Toolkits and Documentation
- Make available toolkits and documentation so that existing expert knowledge and tools for high throughput data transfers, packet loss and throughput-limit monitoring, and collaborative systems are widely known.
- Develop new tools in some cases; support FAQ pages; best practices guides
-   Liaison
- Work with network Engineering Staffs of ESNet, Internet2, STARTAP, the US-CERN link, and other expert groups, to ensure that the existing major network links relevant to ATLAS, CMS and other HEP major programs may be used to their full capability.
- Local Site Administrators
- LHC Program Officers, Institutional CIOs
- HENP Software and Computing Projects

## Programmatic Requirements

- Trans Atlantic Network Committee
- Formed by LHC Joint Oversight Group
- Charge
- Estimate the bandwidth needed for the network connection to CERN to meet the needs of the U.S. HEP community over the next 5 years (2001-2005)
- Estimate the cost of providing this bandwidth
- Several meetings held since February 01
- Current HEP experimental requirements collected
- Report  nearing completion
- LHC Project Planning Documents
- We anticipate additional committees and charges from LHC JoG
- Focusing on domestic networks, local site infrastructure development, etc.

## Large Hadron Collider at CERN

**Large Hadron Collider at CERN**

## Example Application: ATLAS

**Example Application: ATLAS**

- A Torroidal LHC Apparatus
- Collaboration
- 150 institutes
- 1850 physicists
- Detector
- Inner tracker
**Calorimeter**
- Magnet
- Muon
- United States ATLAS
- 29 universities, 3 national labs
- 20% of ATLAS
- Start operations in 2006,7

## Raw data

- Reconstruction

- Data Acquisition

- Level 3 trigger

- Trigger Tags

- Event Summary Data
- ESD

-  Event Tags

- Calibration Data

- Run Conditions

- Trigger System

## Tier 0,1

-  Event Tags

- Event Selection

**Analysis**
** ****Processing**

- Collaboration /
- National Level

- Tier 2
- Analysis
- Groups

- Tier 3, 4
- Physicists

- Physics Analysis

- PhysicsObjects
- StatObjects

- Analysis
- Objects

- PhysicsObjects
- StatObjects

- PhysicsObjects
- StatObjects

-  ...continued

- Event Summary Data
- ESD

## LHC Computing Model (U.S. Implementation)

- Tier-2

**Tier-1**

**Tier-0**** **

**Tier-2**

**(2) Tier 1 Centers**
**CMS: FNAL**
**ATLAS: BNL**

**CERN**

**Universities (~60)**

**Lab or University-based**
**Regional Computing Centers (10)**

## Tier 2 Requirements

## GriPhyN

- Four Frontier Physics Experiments
- LIGO
- Sloan Digital Sky Survey
- CMS
- ATLAS
- Collaborating with Leading Computer Scientists
- Fundamental CS Research in Grids
- Virtual Data Models
- Virtual Data Grid Toolkit Development

## US ATLAS Data Grid Testbed

**UC Berkeley**
**LBNL-NERSC**

**Brookhaven**
**National**
**Laboratory**

**Indiana **
**University**

**Boston **
**University**

**Argonne**
**National**
**Laboratory**

**US ATLAS Data Grid Testbed**

- HPSS sites

**U Michigan**

**University of**
**Texas at**
**Arlington**

**University of**
**  ****Oklahoma**

** ****GriPhyN (NSF ITR)**
** ****Particle Physics Data Grid   (SciDAC)**

##     International Virtual Data Grid Laboratory (proposed)

**    ****International Virtual Data Grid Laboratory (proposed)**

## HENP Networking Meeting

- June 1-2, 2001  Indianapolis (Indiana University)
-  Purpose:
- Bring together leading user-groups (present and future), and experts representing the key networks and transoceanic links vital to HENP’s and other major scientific programs
- Review the status and plans for next generation networks and network technology status and trends
- Review the issues limiting high throughput and/or responsiveness, as seen by networked applications and approaches to remove the limits and scale up general Gbps networking
- To begin to understanding the potential impacts of the coming “self-aware” Data Grid systems on regional, national and international scales
- Form relationships between end-users and network experts

## Meeting Outcomes

- Two Ad-hoc Workgroups formed:
- Requirements (L.Price/ANL, S.Wallace/Indiana)
- Technical “Roadblocks” (H.Newman/Caltech, T.Hacker/Michigan)
- Executive Summary (being written); mail list, website
- Discussion about forming an umbrella group or “Forum”
- What is the appropriate framework and/or “Forum”?
- Internet2 Application Working Group
**Develop charter (H. Newman, R. Gardner meeting with Ted Hanss)**
**October (Austin) I2 Meeting**
- Best way to Interact with ESNet?
**Advised to attend ESCC Meetings**
**Future E2E Performance Working Group**
- Grid Forum Networking BOF?

## Feedback from You

- Two main reasons for such a group
- Expressing Programmatic Requirements to Steering Groups, Program Officers, Lab and University CIOs
- Developing working relationships between users & networking experts
- Encourage participation from local site infrastructure engineers, managers
- Choose meeting places with high overlap of people
- Internet2 Meetings
- Grid Forum BOF for Networking
- Joint Techs Meetings
- ESCC Meetings like this one
- Joint I2, ESNet E2E Meetings
- Need to get the word out to Universities

## More Information

- _http://www.transpac.org/meeting.html_
- _http://lexus.physics.indiana.edu/griphyn/henpnet.html_