![](media/image1.wmf){width="3.3895833333333334in" height="4.0in"}

**Computing and Physics PROJECT STATUS REPORT**

**REPORTING PERIOD**

##### Q2 2003 {#q2-2003 .unnumbered}

January-March, 2003

#   {#section .unnumbered}

[1. Project Manager's Summary. J. Shank (BU)
4](#project-managers-summary.-j.-shank-bu)

[2. WBS 2.1 Physics Manager's Report (Ian Hinchliffe, LBNL)
6](#wbs-2.1-physics-managers-report-ian-hinchliffe-lbnl)

[3. WBS 2.2 Software Manager's Report (Srini Rajagopalan, BNL)
8](#wbs-2.2-software-managers-report-srini-rajagopalan-bnl)

[WBS 2.2.1: Core Services (D. Quarrie)
8](#wbs-2.2.1-core-services-d.-quarrie)

[WBS 2.2.1.1: Framework 8](#wbs-2.2.1.1-framework)

[WBS 2.2.1.2: EDM Infrastructure 9](#wbs-2.2.1.2-edm-infrastructure)

[WBS 2.2.1.3: Detector Description Infrastructure
9](#wbs-2.2.1.3-detector-description-infrastructure)

[WBS 2.2.1.4: Graphics 10](#wbs-2.2.1.4-graphics)

[WBS 2.2.1.5: Analysis Tools 10](#wbs-2.2.1.5-analysis-tools)

[WBS 2.2.1.6: Grid Integration 10](#wbs-2.2.1.6-grid-integration)

[WBS 2.2.2, Databases and Data Management (D. Malon)
10](#wbs-2.2.2-databases-and-data-management-d.-malon)

[WBS 2.2.2.1 Database services and servers
10](#wbs-2.2.2.1-database-services-and-servers)

[WBS 2.2.2.2 Common data management software
10](#wbs-2.2.2.2-common-data-management-software)

[WBS 2.2.2.3 Event store 10](#wbs-2.2.2.3-event-store)

[WBS 2.2.2.4 Detector data management
11](#wbs-2.2.2.4-detector-data-management)

[WBS 2.2.2.5 Collections, catalogs, and metadata
11](#wbs-2.2.2.5-collections-catalogs-and-metadata)

[WBS 2.2.3 Application Software (F. Luehring)
12](#wbs-2.2.3-application-software-f.-luehring)

[WBS 2.2.4 US ATLAS Software Support (A. Undrus)
12](#wbs-2.2.4-us-atlas-software-support-a.-undrus)

[WBS 2.2.4.2 Quality Assurance: (P. Nevski)
13](#wbs-2.2.4.2-quality-assurance-p.-nevski)

[4. WBS 2.3 US ATLAS Facility Manager's Report (B. Gibbard, R. Baker,
BNL)
14](#wbs-2.3-us-atlas-facility-managers-report-b.-gibbard-r.-baker-bnl)

[WBS 2.3.1 Tier 1 Computing Facility at Brookhaven National Laboratory
14](#wbs-2.3.1-tier-1-computing-facility-at-brookhaven-national-laboratory)

[WBS 2.3.1.1 Management and Administration
14](#wbs-2.3.1.1-management-and-administration)

[WBS 2.3.1.2 Tier 1 Fabric Infrastructure
14](#wbs-2.3.1.2-tier-1-fabric-infrastructure)

[WBS 2.3.1.3 Tier 1 Linux Systems 14](#wbs-2.3.1.3-tier-1-linux-systems)

[WBS 2.3.1.4 Tier 1 Storage Systems
15](#wbs-2.3.1.4-tier-1-storage-systems)

[WBS 2.3.1.5 Tier 1 Wide Area Services
15](#wbs-2.3.1.5-tier-1-wide-area-services)

[WBS 2.3.1.6 Tier 1 Operations 15](#wbs-2.3.1.6-tier-1-operations)

[Summary of Major Milestones and Deliverables
15](#summary-of-major-milestones-and-deliverables)

[Forthcoming Milestones and Deliverables
16](#forthcoming-milestones-and-deliverables)

[WBS 2.3.2 Tier 2 Computing Facilities
16](#wbs-2.3.2-tier-2-computing-facilities)

[WBS 2.3.3 Wide Area Network 16](#wbs-2.3.3-wide-area-network)

[WBS 2.3.4 Grid Tools and Services
16](#wbs-2.3.4-grid-tools-and-services)

[Overview 16](#overview)

[Infrastructure 17](#infrastructure)

[Packaging and Configuration 17](#packaging-and-configuration)

[VO Management 18](#vo-management)

[Grid User Management System 18](#grid-user-management-system)

[VO Project with USCMS and iVDGL 18](#vo-project-with-uscms-and-ivdgl)

[WorldGrid Infrastructure 18](#worldgrid-infrastructure)

[Distributed Developers Environment
19](#distributed-developers-environment)

[Workflow Services 19](#workflow-services)

[Chimera based workflow systems 19](#chimera-based-workflow-systems)

[Data Services 19](#data-services)

[ATLAS Distributed Data Management -- MAGDA
19](#atlas-distributed-data-management-magda)

[RLS Service 20](#rls-service)

[Monitoring 20](#monitoring)

[PPDG Monitoring Effort 20](#ppdg-monitoring-effort)

[iVDGL Monitoring Effort 21](#ivdgl-monitoring-effort)

[Production Frameworks 21](#production-frameworks)

[ATLAS Simulation, Reconstruction Software and Run Scripts for
Production
21](#atlas-simulation-reconstruction-software-and-run-scripts-for-production)

[Production RLS 22](#production-rls)

[Chimera Simulation and Reconstruction Bundles
22](#chimera-simulation-and-reconstruction-bundles)

[GRAT Integration 22](#grat-integration)

[Analysis Applications, Interactive Grid Analysis, Portals
22](#analysis-applications-interactive-grid-analysis-portals)

[Grappa (Web Portal) 22](#grappa-web-portal)

[Ganga (Athena Grid Integration) 23](#ganga-athena-grid-integration)

[DIAL (Interactive Analysis Framework)
23](#dial-interactive-analysis-framework)

[WBS 2.3.5 Grid Production 24](#wbs-2.3.5-grid-production)

[5. Financial Report (Chuck Butehorn, BNL)
25](#financial-report-chuck-butehorn-bnl)

#   {#section-1 .unnumbered}

# Project Manager's Summary. J. Shank (BU)

A major reorganization of the US ATLAS Computing and Physics project
took place during this quarter. This started after the Jan., 2003
DOE/NSF LHC Computing review at LBNL. A new organization structure was
formed as shown in figure 1.

![](media/image2.png){width="6.759722222222222in"
height="4.727777777777778in"}

Figure 1. The new US ATLAS Computing and Physics Organization Chart.

Major changes include: new roles for Shank/Huth. Shank is now the
Executive Project Manager for Computing and Physics with responsibility
for the day-to-day operations of the project. This includes allocation
of project funds and planning for the project effort.

Huth retains his title of Associate Project Manager for Physics and
Computing. His new role deals with organization and issues which are
larger than US ATLAS, such as the new ITR proposal DAWN, for which he is
the PI.

S. Rajagopalan takes over as Software Manager from Torre Wenaus.

Under Facilities, we now include level 3 managers for Production (in
charge of Data Challenge production) and Grid Tools and Services (GTS)
for all grid related effort.

Though this new organizational structure has been in place for only a
short time, we believe it is working well.

During this quarter, the new level 2 and 3 managers undertook a complete
rewrite and scrubbing of the project WBS. The new WBS is reflected in
this report. The scrubbing process allowed us to precisely define the
project tasks, assign resources to carry out these tasks and o set
priorities in case of funding shortfalls. We also took the opportunity
to align the new WBS with the emerging new computing structure at CERN
where Dario Barberis and David Quarrie took over from Norman McCubbin. A
completely new ATLAS organization chart also went into effect during
this quarter. This is shown in figure 2.

![](media/image3.jpeg){width="7.1402777777777775in"
height="5.143055555555556in"}

Figure 2. The new ATLAS Computing Organization Chart.

During this quarter the reconstruction jobs for Data Challenge 1 were
started. This is being done on most of the facilities of the US testbed
and will be completed in approximately 2 weeks, once the final version
of the software is released (scheduled for May, 2003). The data from
this will be used for the soon to be completed High Level Trigger
Technical Design Report (HLT TDR, June, 2003).

Most of the software effort in this period went to adding features
needed for the HLT TDR. This included Athena and Gaudi, the Event Data
Model and Data Mangement software. We also made major contributions to
the LCG projects POOL and SEAL, which are crucial to our longer term
ATLAS goal for Data Challenge 2 in 2004.

Under facilities, the new organization with Production and GTS was
developed and plans for using existing grid tools for the next phase of
production (the reconstruction for the HLT TDR) were deployed.

# WBS 2.1 Physics Manager's Report (Ian Hinchliffe, LBNL)

Most of the work in this quarter focused on ensuring that the

generator tools needed for the Atlas physics meeting in Athens in

May 2003 and the High Level Trigger TDR are in place. Effort was

focused on the integration of Tauola and Photos as manpower finally

became available from the physics groups to validate the code that has

been available for some time. (WBS 2.1.1.10 and 2.1.1.11). This code

is expected to be fully validated for use with Pythia and Herwig for

release 6.0.3. Users have begun to exploit the ability to run external

specialized event generators such as Comphep (WBS 2.1.1.13).

Additional changes were made to GenzModule (WBS 2.1.1.18) to provide

improved access to the truth information for the Geant-3 simulation

(atlsim) needed for the reconstruction phase of DC1. A new package,

GenAnalysisTools (WBS 2.1.1.19), was implemented using code originally
part of

Reconstruction. This package provides Ntuples containing Monte Carlo

Truth information and helper packages to handle the truth in a form

that shields the users from the different conventions of the

individual physics generators.

Documentation for all the packages was brought up to date for release

6.0.0 on the web (www-theory.lbl.gov/\~ianh/monte/Generators).

The new Athena random number service (WBS 2.1.1.17) was fully deployed

in release 6.0.0. The specific state of any event generator can be

dumped and is done so automatically should a job crash. This service

should ultimately be used by all athena algorithms so that specific

events can be debugged on demand.

Work also began on porting the code to gcc3.2 and redhat 7.3

which will be used for

atlas release 7.0.0. This has necessitated many technical changes to

overcome the more strict standards that are enforced by this compiler

and the loader distributed with red hat 7.x. Work also started in

preparation for the replacement of the package Simulation/HepMC in the

atlas releases with the CLHEP version of this code. This is expected

to be completed as soon as the next version of CLHEP is made

available in atlas.

# WBS 2.2 Software Manager's Report (Srini Rajagopalan, BNL) 

The ATLAS Computing was reorganized during this quarter, with a new
Computing Coordinator (Dario Barberis), and Software Project Leader

(David Quarrie, LBNL). This reorganization has resulted in a new
management structure, with the software being structured into the
following groups:

o Core Services

o Infrastructure Support

o Simulation

o Event Selection, Reconstruction and Analysis Tools

o Detector Subsystems

This restructuring has been reflected in a new organization structure
for US-ATLAS software development.

The activity during the first quarter was geared toward providing the
necessary support for the reconstruction phase of Data Challenge 1 and
the studies in support of the High Level Trigger (HLT) Technical Design
Report (TDR). The reconstruction of the Data Challenge 1 is scheduled to
begin in May 2003 using Release 6.0.x. The HLT TDR is due in July 2003.

## WBS 2.2.1: Core Services (D. Quarrie) {#wbs-2.2.1-core-services-d.-quarrie .unnumbered}

The breakdown under Core Services was reorganized as well and is
consistent between ATLAS and US ATLAS structure. The primary focus of
the US ATLAS effort remain in the Framework and Event Data Model.

### WBS 2.2.1.1: Framework {#wbs-2.2.1.1-framework .unnumbered}

The main activities in this area were:

-   A CLIDSvc service is available that provides centralized management
    of class-ids (the mechanism by which persistent objects are coupled
    with their transient representation). Currently this is operating in
    \"spy\" mode to detect conflicts, and will transition into full
    operation during the next reporting period (C. Tull).

-   Development of the core component infrastructure for the SEAL LCG
    project. This includes plug-in management supporting dynamic loading
    and unloading of components (M. Marino).

-   W. Widenmann (Wisconsin, ATLAS) provided a prototype of event level
    multi-threading for Athena/Gaudi. This has been productized and
    integrated into the code repository (P. Calafiura).

-   Major re-write of GaudiPython. Changes introduced to convert the
    package to new version of Boost.Python 2.0. Added the capability of
    setting and getting properties of Algorithms and Services before
    they are created by the Application Manager. (W. Lavrijsen)

-   New version of the Athena Reconstruction tutorial. Changes to the
    material to reflect the evolution of StoreGate API. New enhanced
    version of ASK, the Athena Software Kit (P. Calafiura, W.
    Lavrijsen, M. Marino)

-   The Interval of Validity service (IOVSvc) has been integrated with
    the detector description of the Pixels inner detector and a testbed
    ASCII conversion service to demonstrate support for time-varying
    mis-alignments. (C. Leggett)

-   An enhanced Message service (MessageSvc) has been provided that
    supports the use of color to highlight messages of different
    severity levels (debug, informational, warning, etc.) (C. Leggett)

-   Preparation for porting of the ATLAS software to gcc 3.2 was begun.
    The focus for this will be release 6.1.0, scheduled for the
    beginning of May, but essentially groundwork has been put in place
    in order to accelerate the porting of higher level software such as
    reconstruction. This has involved changes to several of the core
    Gaudi/Athena packages (P. Calafiura, W. Lavrijsen, C. Leggett)

### WBS 2.2.1.2: EDM Infrastructure {#wbs-2.2.1.2-edm-infrastructure .unnumbered}

-   The StoreGate package has been reorganized into three collaborating
    packages in order to reduce couplings and dependencies and to
    improve the modularity. (P. Calafiura, S. Rajagopalan)

```{=html}
<!-- -->
```
-   The Proxy Provider Service has been deployed that handles the
    loading of data object addresses from persistency. The loading of
    addresses can be done at the beginning of the job, beginning of the
    event or on-demand. Note that the data object is itself loaded only
    on-demand from persistency using these addresses. This establishes a
    communication channel between client requests for data objects in
    transient memory and the persistency services. (P. Calafiura, S.
    Rajagopalan)

```{=html}
<!-- -->
```
-   A prototype pile-up framework has been developed based on the Liquid
    Argon detector. This supports optimized pile-up based on the
    detector characteristics, and can be used as the basis for the
    development of support for the other detector subsystems (P.
    Calafiura).

### WBS 2.2.1.3: Detector Description Infrastructure {#wbs-2.2.1.3-detector-description-infrastructure .unnumbered}

-   A major emphasis has been to establish a common materials definition
    that can be used by all detector subsystems. This is now in place,
    although a few additional material definitions are required. The
    ability to generate a Geant4 geometry from a GeoModel geometry has
    been demonstrated, although there are some optimization issues that
    need to be resolved. Integration with the NOVA service for primary
    numbers has begun. (J. Boudreau, D. Costanzo).

### WBS 2.2.1.4: Graphics {#wbs-2.2.1.4-graphics .unnumbered}

There was no development in this area from US-ATLAS in this quarter.

### WBS 2.2.1.5: Analysis Tools {#wbs-2.2.1.5-analysis-tools .unnumbered}

There was no development in this area from US-ATLAS in this quarter.

### WBS 2.2.1.6: Grid Integration {#wbs-2.2.1.6-grid-integration .unnumbered}

## WBS 2.2.2, Databases and Data Management (D. Malon) {#wbs-2.2.2-databases-and-data-management-d.-malon .unnumbered}

### WBS 2.2.2.1 Database services and servers  {#wbs-2.2.2.1-database-services-and-servers .unnumbered}

(Vaniachine)

MySQL server support, cleanup and archiving of data in legacy
Objectivity/DB databases, external package support for both ATLAS and
LCG, and updating of server-side software were all part of U.S. database
service/server support in this reporting quarter.

New developments included a web interface for access to conditions data,
and database replication infrastructure for the tag database (the latter
jointly with Grenoble).

### WBS 2.2.2.2 Common data management software  {#wbs-2.2.2.2-common-data-management-software .unnumbered}

(Fine, Adams, Perevoztchikov)

While continued support of the AthenaRoot conversion service required
some effort in this reporting quarter, U.S. development efforts in this
WBS area have been aimed primarily at delivery of a prototype conversion
service based upon the LHC-wide LCG POOL persistence software currently
under development. Design has been completed, and a limited
implementation was delivered to specialists. A prototype will not be
delivered for general use by software developers until the coming
quarter (ATLAS Release 6.3.0), when insufficiencies in the underlying
software upon which this work depends (particularly the dictionary
coming from the LCG SEAL project) and non-database LCG/Athena (and
cmt/scram) integration issues have been resolved.

### WBS 2.2.2.3 Event store  {#wbs-2.2.2.3-event-store .unnumbered}

(Adams)

A plan for integration of dataset and POOL event collections was
developed. Work in this area is targeted primarily for the second half
of this year in preparation for Data Challenge 2, after POOL-based
common data management software (WBS 2.2.2.2) becomes available, and the
underlying components (POOL and SEAL in particular) are more functional
and more stable.

### WBS 2.2.2.4 Detector data management  {#wbs-2.2.2.4-detector-data-management .unnumbered}

(Vaniachine, Eckmann)

The Nova database was extended to support several additional kinds of
data, including liquid argonne calorimeter sagging parameters, new tile
calorimeter primary numbers, and test beam simulations. The database was
reorganized to support hierarchical organization of digitization
parameters for the muon system.

Several enhancements were made to support access to data in Nova
mediated by an interval-of-validity database service under development
at Orsay.

At the request of the detector description group, work was begun on
support for a materials service.

An automatic converter generation mechanism was delivered; it will be
integrated into nightly builds in the coming quarter.

### WBS 2.2.2.5 Collections, catalogs, and metadata  {#wbs-2.2.2.5-collections-catalogs-and-metadata .unnumbered}

(Eckmann)

A prototype relational database implementation of explicit collections

(roughly, event lists with associated \"tag\" data) was delivered as a
U.S. ATLAS contribution to the LCG POOL project. Interfaces and
infrastructure in support of typesafe collections was also delivered;
implementation will be handled by CERN-based POOL project members.

Kristo Karr will replace Steve Eckmann in the coming reporting quarter
in this WBS reporting area.

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

Status of database milestones mentioned in the previous quarterly

report:

-   Athena conversion service prototype based upon POOL Release 0.3.0
    (February 2003);

    -   **Status:** limited prototype, late along with all of ATLAS
        release 6.1.0 (mitigating factors: introduction of new compiler
        (gcc3.2), problems in AtlasSEAL integration package on which
        this milestone depends)

    -   New milestone: prototype based upon POOL Release 1.0.0 in ATLAS
        Release 6.3.0 (June 2003);

-   Extensions to NOVA to support interval-of-validity services
    (February 2003);

    -   **Status: DONE**

-   Explicit collections instantiated in ROOT, and higher-level
    collection services (March 2003);

    -   **Status:** CERN-based effort has been identified to offload the
        ROOT implementations\--no longer a U.S. responsibility (though
        overall coordination remains a U.S. job)

-   ATLAS workshop on conditions and other time-varying data (February
    2003)

    -   **Status: DONE**

## WBS 2.2.3 Application Software (F. Luehring) {#wbs-2.2.3-application-software-f.-luehring .unnumbered}

**Geant3 Simulation Support: (P. Nevski)**

The schema to simulate the complete pile-up in the ATLAS detector
(including the cavern neutron background componen and minimum bias
collisions in ± 750 ns gates) have been optimised. This allowed
production to run on standard machines in a dual processor production
mode.

The calorimeter pile-up code was instrumented to control the quality of
event mixing and the calorimeter digitization on demand.

Two new event generators have been interfaced to ATLSIM and the relevant
geometry elements added to DICE. The cosmic muons generators integrated
in the ATLAS environment will provide muon fluxes in the experimental
cavern. The interface to the machine background calculations using MARS
codes will alow to estimate the rates of halo particles and beam-gas
collision in the ATLAS cavern.

## WBS 2.2.4 US ATLAS Software Support (A. Undrus) {#wbs-2.2.4-us-atlas-software-support-a.-undrus .unnumbered}

-   Maintenance of the ATLAS nightly build system:

The ATLAS nightly build facilities at CERN and BNL were monitored and
improved. The special branch of nightly builds with new compiler gcc-3.2
was started at CERN. As a result ATLAS software developers got immediate
feedback on compliance of their new submissions with new compiler
standards.

-   Participation in the ATLAS Software Infrastructure Team:

U.S. Atlas Software Librarian (A. Undrus, BNL) actively worked in ATLAS
software infrastructure and testing (SIT) team on software release
management, quality assurance and testing. He proposed to create a
document on ATLAS software testing standards and methods and will
provide a prototype for the SIT testing meeting scheduled in April 2003.

-   Deployment of the nightly control system tools used by LCG:

The nightly control system tool, NICOS, was developed based on the
experience and software created for ATLAS nightly builds. This flexible
tool for coordination of software development manages the multi-platform
nightly builds based on the recent versions of software packages, tests
newly built software, identifies possible problems and make results
immediately available to developers spread over different institutions
and countries. The NICOS tool was accepted for use by SPI group of LHC
Computing Grid (LCG) Project at CERN. The experimental NICOS builds of
LCG software are started. The talk about NICOS was presented at CHEP
2003, San Diego, CA.

-   Deployment of LCG related software at the Tier 1 facility:

The work on integrating POOL (the persistency framework being developed
by the LCG) into Athena (the ATLAS offline software framework) has
started. In the first quarter POOL was installed at BNL and the bridge
package, AtlasPOOL, that provides the access to POOL in the ATLAS
software release was developed.

-   Tests of ATLAS software using Redhat 7.3 in preparation for upgrade:

In cooperation with ACF staff, the upgrade of operating system to Red
Hat 7.3 in the Tier I Linux Farm nodes has been scheduled for April,
2003. In preparation, a single node on the farm was upgraded to the new
OS where the ATLAS software was successfully built and tested. This
upgrade is performed in synchronization with the analogous upgrade at
CERN with the purpose of creating identical working environment on Atlas
computer farms.

-   Deployment of new ATLAS software at BNL:

New ATLAS software continues to be promptly installed at the BNL Tier I
Center, usually in one to three days after the corresponding CERN
installation (typically once every three weeks). The BNL software
support page is updated in a timely way.

-   Maintenance of the US ATLAS MySQL web server:

The U.S. Atlas MySQL database, web server, and cvs pserver were
maintained and administered. The U.S. Atlas community actively used
these services.

### WBS 2.2.4.2 Quality Assurance: (P. Nevski) {#wbs-2.2.4.2-quality-assurance-p.-nevski .unnumbered}

A procedure for verification of the reconstruction results used for the
ATRECON has been modified for the reconstruction running in ATHENA. A
number of limitations implied by the ouput event size have been removed.
This procedure will be later used for the DC1 reconstruction validation.

# WBS 2.3 US ATLAS Facility Manager's Report (B. Gibbard, R. Baker, BNL)

During the second quarter of FY '03, the Facility project under WBS 2.3
was reorganized to reflect the increasing importance of both Grid
projects and Production activities. Most of the work that was previously
included under the "Distributed IT Infrastructure" WBS item 2.3.2 has
been moved into the new level 3 area 2.3.4, Grid Tools and Services. An
entirely new level 3 WBS item, 2.3.5, US ATLAS Production, has been
created to focus on the very significant effort required to prepare and
execute ATLAS Data Challenges in addition to configuring and running the
production Grid infrastructure for US ATLAS.

## WBS 2.3.1 Tier 1 Computing Facility at Brookhaven National Laboratory {#wbs-2.3.1-tier-1-computing-facility-at-brookhaven-national-laboratory .unnumbered}

###  {#section-2 .unnumbered}

This report reflects a modified WBS breakdown for the Tier 1 facility
based on functional areas (CPU, Storage, etc.) which more clearly
reflect the way work is organized and managed. During the first quarter
of FY '03, Tier 1 facility staffing was maintained at the level of 4.5
FTE on project. An additional 0.5 FTE for ATLAS Grid support funded via
PPDG which was previously accounted for under the Tier 1 WBS item has
been shifted to WBS 2.3.4.

The focus of Tier 1 activity during the second quarter was the
successful execution of Data Challenge 1 Phase 2 and preparation for the
subsequent reconstruction and analysis phase scheduled for the third
quarter.

### WBS 2.3.1.1 Management and Administration {#wbs-2.3.1.1-management-and-administration .unnumbered}

This new level 4 WBS item includes management and support of the
facility staff, Global planning and reporting and liaison between the
Tier 1 facility and external groups. In previous reports, most of this
effort was reported under WBS item 2.3.1.3, Facility Administration and
Support.

In addition to the day-to-day oversight of the Tier 1 facility, the
reorganization of WBS area 2.3 was a significant task during the second
quarter.

The level of effort directed to WBS 2.3.1.1 during this quarter was
constant at 1.4 FTE.

### WBS 2.3.1.2 Tier 1 Fabric Infrastructure {#wbs-2.3.1.2-tier-1-fabric-infrastructure .unnumbered}

This new level 4 WBS item includes both physical infrastructure (power,
A/C) and the basic elements of the local computing infrastructure
including security, local area network components and backup systems.

The level of effort for WBS 2.3.1.2 continued at a constant 0.7 FTE
during the quarter.

### WBS 2.3.1.3 Tier 1 Linux Systems {#wbs-2.3.1.3-tier-1-linux-systems .unnumbered}

This new level 4 WBS item consolidates all of the items related to Linux
Systems that were previously split between separate level 4 entries for
hardware and software.

The Tier 1 Linux Farm was used heavily during the quarter for ATLAS Data
Challenge activities, and most of the effort in this WBS area was
dedicated to maintaining and optimizing the environment (particularly
batch queues) needed to support this effort. A significant upgrade of
the operating system and compiler was also completed during the quarter.

.

The level of effort for WBS 2.3.1.3 was at the planned 0.3 FTE during
the quarter.

### WBS 2.3.1.4 Tier 1 Storage Systems {#wbs-2.3.1.4-tier-1-storage-systems .unnumbered}

###  {#section-3 .unnumbered}

This new level 4 WBS item consolidates all of the items related to disk
and tape storage that were previously split between separate level 4
entries for hardware and software.

During the quarter, both the disk and tape storage systems were heavily
used to handle the large volume of data produced by ATLAS Data Challenge
1, Phase 2. The storage systems performed extremely well and were a key
factor in the success of the Data Challenge.

The level of effort for WBS 2.3.1.3 was 0.5 FTE

### WBS 2.3.1.5 Tier 1 Wide Area Services {#wbs-2.3.1.5-tier-1-wide-area-services .unnumbered}

###  {#section-4 .unnumbered}

This new level 4 WBS item includes Wide Area Network support and Grid
Middleware deployment and support.

The major effort in this area during the quarter was to support Phase 1
of the Data Challenge, which relied heavily on Grid protocols and
services.

The level of effort for WBS 2.3.1.5 was 1.0 FTE

### WBS 2.3.1.6 Tier 1 Operations {#wbs-2.3.1.6-tier-1-operations .unnumbered}

###  {#section-5 .unnumbered}

This new level 4 WBS item focuses primarily on Facility support and
monitoring.

The level of effort for WBS 2.3.1.6 was 0.6 FTE

## Summary of Major Milestones and Deliverables {#summary-of-major-milestones-and-deliverables .unnumbered}

During the quarter, the Tier 1 facility contributed significantly to the
execution of ATLAS Data Challenge 1 which is an important project
milestone.

There were no significant facility-specific milestones scheduled or
completed during the quarter.

## Forthcoming Milestones and Deliverables {#forthcoming-milestones-and-deliverables .unnumbered}

During the quarter, work was started on deployment of the LCG pilot
release in preparation for full LCG pilot operation in the third and
fourth quarters.

The next major facility hardware upgrade is planned for FY '04 in
preparation for ATLAS DC 2. Pre-production for DC 2 is expected to begin
in the second quarter of FY'04.

### WBS 2.3.2 Tier 2 Computing Facilities {#wbs-2.3.2-tier-2-computing-facilities .unnumbered}

### WBS 2.3.3 Wide Area Network {#wbs-2.3.3-wide-area-network .unnumbered}

### WBS 2.3.4 Grid Tools and Services {#wbs-2.3.4-grid-tools-and-services .unnumbered}

# Overview {#overview .unnumbered}

This quarterly report covers the period January 1-March 31, 2003. During
this time the US ATLAS Software and Computing project was reorganized,
with Grid Tools and Services (WBS 2.3.4) becoming a new area in the
Facilities subproject. GTS is responsible for development, evaluation,
and creation of integrated grid-based systems for distributed production
processing and user analysis within the US ATLAS software and computing
project. The initial organization of the project is given in the table
below. Work has begun to develop a WBS dictionary, schedule, milestones,
and resource assignments.

+---------+-----------+------------------------------------------------+
| WBS     | Name      | Technology Areas                               |
| Number  |           |                                                |
| 2.3.4.x |           |                                                |
|         |           |                                                |
| (level  |           |                                                |
| 4)      |           |                                                |
+=========+===========+================================================+
| 1       | Infra     | Packaging, configuration, testing and          |
|         | structure | certification harnesses, security, VO          |
|         |           | management, distributed systems developer      |
|         |           | environment (grid component libraries, hosting |
|         |           | environment, R&D testbed).                     |
+---------+-----------+------------------------------------------------+
| 2       | Workflow  | Execution and data placement; planners,        |
|         | Services  | resource brokers, scheduling systems, resource |
|         |           | prediction; computing model and architecture.  |
+---------+-----------+------------------------------------------------+
| 3       | Data      | Replica location services, virtual data and    |
|         | Services  | provenance, metadata management services,      |
|         |           | knowledge management frameworks.               |
+---------+-----------+------------------------------------------------+
| 4       | M         | Directories for resource discovery (MDS, grid  |
|         | onitoring | service registries), resource monitoring       |
|         | Services  | (status level, historical), performance,       |
|         |           | accounting, and archival systems.              |
+---------+-----------+------------------------------------------------+
| 5       | P         | Production frameworks for data challenges;     |
|         | roduction | ATLAS software packaging and run time          |
|         | F         | environments.                                  |
|         | rameworks |                                                |
+---------+-----------+------------------------------------------------+
| 6       | Analysis  | Distributed interactive analysis, grid user    |
|         | App       | interfaces and portals, advanced workspace     |
|         | lications | environments and venues.                       |
+---------+-----------+------------------------------------------------+

#  {#section-6 .unnumbered}

# Infrastructure {#infrastructure .unnumbered}

Development of the necessary infrastructure for middleware services, as
related to US ATLAS, is covered in this work area. Below we describe
activities and progress during the work period.

## Packaging and Configuration {#packaging-and-configuration .unnumbered}

Work continued on development of the Pacman packaging and configuration
tool developed by US ATLAS. This work is being performed by Saul Youssef
of Boston University, as part of the iVDGL project. The project homepage
is at <http://physics.bu.edu/~youssef/pacman>. Development included:

-   Improved support for Pacman software updates

-   New caches: University of Chicago (UCHEP) for ATLAS software
    releases and the University of Southern California Information
    Sciences Institute (ISI) to support RLS (Replica Location Service).

-   Participation in metapackaging discussion forums.

Under the auspices of the HIJTB, which is the intergrid joint technical
board co-chaired by Ruth Pordes (Fermilab, PPDG Coordinator) and Ian
Bird (LCG Grid Deployment Manager) a group was formed to address
packaging, installation, and configuration of grid middleware. A
document was produced which was addressed to grid middleware developers
and distributors such as the NSF Middleware Initiative (NMI), the
Virtual Data Toolkit group of GriPhyN and iVDGL (VDT), the European
DataGrid project (EDG), the LCG certification group, and to
organizational entities HICB (HENP Intergrid Collaboration Board) and
the LCG Grid Deployment Board (GDB). A collaborative effort between LCG,
EDG, and iVDGL has been organized (GLUE Metapackaging Group) to address
development and future directions.

A number of recommendations have been made for software developers,
metapacking developers, and site administrators. Consideration has been
given to supporting LCG installations for various types of sites: large
farms, medium-sized clusters, and desktops or mini-clusters, and for
manual and automatic installations. Keeping in mind that to establish a
uniform service, the functionality of the resulting setup must be the
same regardless of the site.

The group is collaborating closely with the core technology groups
(Globus, Condor) and the NSF NMI project[^1] which provides
distributions in RPM format, ideal for LCG installations, or EDG
installations which use LCFG[^2].

## VO Management {#vo-management .unnumbered}

### Grid User Management System {#grid-user-management-system .unnumbered}

This effort is led by Dantong Yu of Brookhaven National Laboratory.

We developed the Grid User Management System (GUMS). The particular
problem that we intend to address is the need for strong
pre-registration of users, and we believe that this builds nicely on the
existing grid VO management software. Our focus has been on developing a
user account management system and tools to allow sites to keep track of
users. We intend all of these developments to be compatible with
whatever VO management tools are adopted for LCG. GUMS downloads
certificates from VO server, then stores the certificates in the local
MYSQL database. The local account manager maps the newly discovered
Distinguish Name to a grid account and groups based on local policy. The
mapping information will be stored in MYSQL database also. A simple
Python script scans the MYSQL database and creates the gridmap file. The
software package can be obtained from Web site:
http://www.atlasgrid.bnl.gov/testbed/gums. The presentation is available
at http://chep03.ucsd.edu/files/363.ppt. The paper is in the writing
processing. It will be published in CHEP03.

### VO Project with USCMS and iVDGL {#vo-project-with-uscms-and-ivdgl .unnumbered}

During this period US ATLAS has joined a new project with iVDGL and
USCMS to develop VO management solutions appropriate to large sites such
as Brookhaven National Laboratory and university Tier 2 and Tier 3
centers.

## WorldGrid Infrastructure {#worldgrid-infrastructure .unnumbered}

This effort is being led by Professor Saul Youssef of Boston University.

WorldGrid is an iVDGL project and includes participation from US ATLAS,
US CMS, LIGO, and the Sloan Digital Sky Survey project. The WorldGrid
project is aimed to develop software to provide simple, complete grid
solution for sites wishing to participate in various grid computing
projects. The focus for SC2002 was ease of installation,
interoperability with EDG software, and controlled use of shared
resources.

During this work period the WorldGrid team redesigned the Pacman cache
structure, removing EDG components and ScienceGrid applications. Designs
for a new WorldGrid application which facilitates site management and
the packaging and distribution of applications into "projects" were
started. A joint iVDGL and DataTAG talk on WorldGrid was given at CHEP:

<http://chep03.ucsd.edu/files/199.ppt>.

The WorldGrid package has been installed and is being used on the Tier 1
facility at Brookhaven, and at both US ATLAS prototype Tier 2 centers at
Indiana University and Boston University, and a number of other US ATLAS
Testbed sites.

## Distributed Developers Environment {#distributed-developers-environment .unnumbered}

In order to facilitate integration of components from many different
software packages, a new Pacman cache containing "templates" required
for interfaces and adapters was created. This library is called "Grid
Component Library", or GCL, and adapters to components are being placed
there for Chimera development. Available packages and documentation for
the library is available at: <http://grid.uchicago.edu/gcl>.

# Workflow Services {#workflow-services .unnumbered}

## Chimera based workflow systems {#chimera-based-workflow-systems .unnumbered}

As a part of US ATLAS collaboration with the GriPhyN project, we have
been developing workflow systems based on the Chimera/Pegasus virtual
data system. The effort comes from Dan Engh and Yuri Smirnov of the
University of Chicago, and Edward May and Jerry Gieraltowski of Argonne
National Laboratory. During the work period, the following were
accomplished:

-   ATLSIM scripts reconfigured into suitable format for grid-based
    execution

-   ATLSIM transformations defined in VDL (Virtual Data Language)

-   An RLS service provided by Argonne was evaluated

-   Script to generate "abstract" DAG (directed acyclic graph) for
    Condor execution written

-   Script to create and update a virtual data catalog written and
    tested

-   Script to create "concrete" DAG corresponding to DC1 partition
    (file) creation

-   Script to execute dataset creation on a number of US ATLAS testbed
    sites

-   Configuration software written to allow use of opportunistic use of
    shared resources -- the case tested was the new Jazz cluster at
    Argonne National Laboratory

-   Utility scripts to list, cleanup, monitor the RLS service

Results from the development effort were presented at the March ATLAS
software workshop. The ATLAS Chimera project homepage provides more
detailed information: <http://grid.uchicago.edu/atlaschimera>.

# Data Services {#data-services .unnumbered}

This work are contains development efforts for replicas, distributed
replica environments, metadata and advanced metadata management systems
and interfaces.

## ATLAS Distributed Data Management -- MAGDA  {#atlas-distributed-data-management-magda .unnumbered}

The MAGDA effort is led by Wensheng Deng of Brookhaven National
Laboratory.

MAGDA has been adopted by the International ATLAS Collaboration as the
primary metadata and replication service for ATLAS (data challenges and
user interface). The system is based on an SQL (MySQL) database at the
core of the system. DB interactions occur via perl, C++, java and cgi
(perl) scripts. A web interface for browsing files resulting from the
current data challenge for the high level trigger has been implemented,
along with command line tools (magda_findfile, magda_getfile,
magda_putfile, and magda_validate).

For the current high level trigger data challenge for international
ATLAS, data are cataloged from the entire US ATLAS Grid Testbed,
Alberta, CERN, Lyon, INFN (CNAF, Milan), FZK, IFIC, NorduGrid, and RAL,
and made available to the Collaboration. So far, 264k files have been
cataloged, representing 65.5 TB of data. The system has now been tested
for scalability up to 1.5M files.

MAGDA has now been in stable operation since May 2001. It is now being
employed by the Phoenix experiment at RHIC and is being evaluated by
other collaborations.

Current and near term work includes an implementation of Magda as an
option for a catalog back-end to the LCG POOL persistency framework. It
is being tested by the EDG testbed. Further details can be found in a
talk presented by Dr. Deng at the CHEP2003 conference:

<http://www.atlasgrid.bnl.gov/magdadoc/magda_chep2003.ppt>.

## RLS Service {#rls-service .unnumbered}

In support of Chimera development, and for evaluation of EDG and LCG
software environments, two new RLS instances were created -- one at
Chicago by Ed May, the other at BNL by Jason Smith. They are currently
under evaluation and being used in support of production framework
development for Chimera, which at the moment requires it.

# Monitoring {#monitoring .unnumbered}

Two major monitoring development efforts are underway in US ATLAS. Both
use the popular Ganglia monitoring package developed at UC Berkeley to
provide the basic resource monitoring infrastructure for cluster
resources. The first effort, working under the auspices of PPDG, focuses
on publication of resource availability and load using MDS (the Globus
Metacomputing Directory Service) and the GLUE Schema. The second,
working in collaboration with GriPhyN and iVDGL, focuses on "Grid Level"
monitoring for research into policy-driven scheduling and usage.

## PPDG Monitoring Effort {#ppdg-monitoring-effort .unnumbered}

This PPDG related effort is being led by Dantong Yu of Brookhaven
National Laboratory. In the last quarter, there was work to integrate
Ganglia with the Globus Monitoring and Discovery Service. Here, we
implemented the Ganglia information provider which publishes the data
from the collector daemon of Ganglia (gmetad) into MDS. The existing
Ganglia information provider only works with individual daemons and it
does not support hierarchical monitoring while ours does. The front-end
of our information provider uses GLUE schema
(http://www.cnaf.Infn.It/\~sergio/datatag/glue/), and its back-end uses
XML.

The work will be published by CHEP03: "GridMonitoring: Integration of
Large Scale Facility Monitoring with Meta Data Service in Grid
Environment". This abstract and full version of paper describe a Grid
Monitoring Architecture that captures and makes available the most
important information from a large computing facility. The presentation
can be downloaded at: <http://chep03.ucsd.edu/files/321.ppt>.

## iVDGL Monitoring Effort {#ivdgl-monitoring-effort .unnumbered}

In addition to the above work, development continued on the VO-Ganglia
software demonstrated at Super Computing 2002 in Baltimore. This work
complements the PPDG monitoring work by focusing on collecting
information required for policy-driven scheduling. The project is being
developed by Catalin Dumatrescu (University of Chicago, GriPhyN) with
supervision from Rob Gardner (University of Chicago) and Mike Wilde
(Argonne). The goals of the project are to develop systems to monitor
grid-level resource activity, utilization, and performance; to provide
VO-level resource activity and resource utilization monitoring; to
create customized views of monitoring data include those target for
hardware resources (clusters, sites, grids) and VO usage: jobs and
workflow types. Extended requirements and goals of the project are to
provide a policy-driven steering mechanism for grid-resource scheduling.
The design goals are to provide for scalability over large number of
resources and networks, and to be fault-tolerant.

# Production Frameworks {#production-frameworks .unnumbered}

Production frameworks are required to support ATLAS data challenges.
During the work period development for DC1 pileup simulation was pursued
with the GRAT toolkit. In parallel, development began using the Chimera
(GriPhyN) libraries.

A simple production framework based on the Chimera workflow system was
developed. The framework is useful for small scale datasets (requiring
submissions for input ranges of partitions which can be done by hand
with limited user intervention and monitoring. The system was used by
Dan Engh and Ed May to produce a 10,000 event data sample for the SUSY
group. The work was done in close collaboration with ATLAS physicists at
Chicago (Ambreesh Gupta and Jim Pilcher) and with Ian Hinchliffe of
LBNL.

## ATLAS Simulation, Reconstruction Software and Run Scripts for Production {#atlas-simulation-reconstruction-software-and-run-scripts-for-production .unnumbered}

During the work period we began a new approach to Pacmanizing and
distributing ATLAS releases for grid-based production, taking advantage
of release preparation by our ATLAS colleagues working on the Nordugrid
project.

Yuri Smirnov of the University of Chicago has sucessfully Pacmanized and
tested several ATLAS releases based on Nordugrid rpms starting with
release 5.3.0. He recently completed 6.0.2, which has been tested by
Yuri Fisyak at Brookhaven and by Ed May, as well as by Yuri himself at
LBL. The package consists of the release itself, plus a test package
which comes with a sample input Zebra data file consisting of 5 events
to be reconstucted for testing. These are available in the UCHEP Pacman
cache, with instructions given at:
[[http://grid.uchicago.edu/Atlas-nordugrid/]{.underline}](http://grid.uchicago.edu/Atlas-nordugrid/).

It its currently being installed into official US ATLAS testbed
installation areas. Fred Luehring at IU has installed and tested this at
the IU Tier 2 center.

Future US ATLAS software packaging activities will use common packaging,
installation, and configuration adopted by international ATLAS. At
present, no single, official solution exists. A new working group is
being formed to address a CMT to Pacman packaging solution.

## Production RLS {#production-rls .unnumbered}

As discussed earlier, an RLS (a local replica catalog and replica
location index server) is required by the curent release of Chimera. Ed
May has installed, configured, and tested an RLS instance on
grid02.uchicago.edu which uses a MySQL database as a backend. The RLS is
being used in an auxillary fashion: LFNs (logical file names) in the
abstract DAGs are mapped to PFNs (physical file names). The RLS
installation method has been Pacmanized by iVDGL, and the BNL team of
Jason Smith and Dantong Yu installed a second RLS service there.

## Chimera Simulation and Reconstruction Bundles {#chimera-simulation-and-reconstruction-bundles .unnumbered}

Based on early work of Dan Engh, Jerry Gieraltowski of Argonne has
created a set of Pacman packages which create the appropriate submission
environment for Chimera for simulation and reconstruction production.
These packages are being deposited for general use ATLAS users with
complete instructions in the Grid Component Library cache (GCL):
[[http://grid.uchicago.edu/gcl/]{.underline}](http://grid.uchicago.edu/gcl/).

## GRAT Integration  {#grat-integration .unnumbered}

Future work on production frameworks will integrate with components from
the GRAT toolkit which have been developed for DC1 production. The
initial plan is to:

1.  Create an input staging system which reserves LFNs from available
    DC1 partitions to be reconstructed; this will use the production
    database, MAGDA, GRAT modules, and RLS.

2.  A system to direct Chimera and Pegasus workflow, which automates
    preparation of the Condor DAGs.

3.  A submission layer to US ATLAS grid resources

4.  A validation and monitoring system

# Analysis Applications, Interactive Grid Analysis, Portals {#analysis-applications-interactive-grid-analysis-portals .unnumbered}

In parallel with the production framework development, a number of grid
user interface, interactive analysis, and grid portal frameworks are
under development in US ATLAS. To track developments in this field, US
ATLAS continues to participate and lead development forums such as the
PPDG CS-11 working group, <http://www.ppdg.net/pa/ppdg-pa/idat/>. The
goal of this group is "interfacing and integrating interactive data
analysis tools with the Grid and identifying common components and
services".

Three ATLAS projects have been under development, each working on
different aspects of the grid/user/application interface problem.

## Grappa (Web Portal) {#grappa-web-portal .unnumbered}

The Grappa project is being developed by Dan Engh of the University of
Chicago. Two weeks of development time was given to the project during
the work period.

Grappa was an early (web-based) grid portal designed to provide a simple
point of grid access for Athena applications running on the grid. The
project originally was developed at Indiana University under the
auspices of the GriPhyN project, and used significant leveraged
resources in the form of a full-time CS developer (Shava Smallen) for
one year, with extended support through SC2002. The project utilized the
Common Component Architecture notebook software developed by the
computer science department at Indiana University.

Work during FY03 Q2 focused on a feasibility study to evaluate Grappa
using the Jetspeed portal framework. A new grid portal was built,
providing basic job submission functionality for Athena ATLFAST
simulations on the US ATLAS testbed, including:

a)  support for distributed grid proxies

b)  specification of input and output locations for grid-resident data

c)  input of Pythia and/or Isajet physics generation parameters

d)  selection of grid computational resources

e)  job execution monitoring using Globus protocols

f)  invocation and display of pre-sampled PAW histograms produced by
    Athena jobs executing on the grid

g)  recording of job "sessions" allowing archival of grid interactive
    sessions

The feasibility study using Jetspeed was performed for two reasons:
before leaving IU, Smallen had completed a port of the underlying Grappa
notebook component technology, and so many of the previous problems and
shortcomings had been fixed; second, Jetspeed, a web-based portal
framework, has been receiving increasing attention in the grid user
environment community and was selected as the base technology by the HEP
collaborative tools ITR "GECR". A presentation describing the Grappa
Jetspeed development was given at CHEP:

<http://hep.uchicago.edu/chanl/grappa/grappa_chep03.html>

## Ganga (Athena Grid Integration) {#ganga-athena-grid-integration .unnumbered}

Ganga is a user interface for configuring applications that use the
Gaudi/Athena software framework of ATLAS and LHCb, and for performing
the tasks necessary to run jobs either locally or on the Grid. It is
being funded by the GridPP project in the UK. In US ATLAS, Craig Tull of
LBNL coordinates design and architecture, and specific Python interfaces
to Athena. The interface work is fully described in the Software WBS.
Future grid integration work and testing within US ATLAS grid
development environments will be described in this WBS. The details of
the Ganga design and implementation, and report on the first use of
Ganga to run ATLAS applications were given at a CHEP presentation:
<http://chep03.ucsd.edu/files/175.ppt>

In contrast to Grappa, Ganga provides a rich, native interface to be
integrated with the users desktop.

## DIAL (Interactive Analysis Framework) {#dial-interactive-analysis-framework .unnumbered}

DIAL (Distributed Interactive Analysis of Large datasets) is a project
to investigate HEP distributed interactive analysis. It has three
primary goals:

a)  Demonstrate the feasibility of distributed analysis of large
    datasets

b)  Set corresponding requirements for grid components and services

c)  Provide the ATLAS experiment with a useful distributed analysis
    environment

DIAL is being developed by David Adams of Brookhaven National Laboratory
as a part of PPDG, to understand the requirements that interactive
analysis places on the grid. Within ATLAS the goal is to enable
distributed interactive analysis of event data. DIAL will enable users
to analyze very large, event-based datasets using an application that is
natural to the data format. Both the dataset and the processing may be
distributed over a farm, a site (collection of farms) or a grid
(collection of sites). The system has been described in a CHEP paper:

[[http://www.usatlas.bnl.gov/\~dladams/dial/talks/dial_chep2003.doc]{.underline}](http://www.usatlas.bnl.gov/~dladams/dial/talks/dial_chep2003.doc)

### WBS 2.3.5 Grid Production {#wbs-2.3.5-grid-production .unnumbered}

During Q2 of FY03, the U.S. ATLAS facilities played a major role in
ATLAS Data Challenge (DC) production. Large samples of events were
processed through the entire event generation and pile-up chains using
ATLSIM. We also started testing ATHENA reconstruction production on
small test samples. During this reporting period, the U.S. continued to
provide the largest grid-based production system in all of ATLAS,
through participation in the U.S. ATLAS Grid Testbed.

The U.S. Testbed supports a diverse range of activities. Many of the
grid applications and tools developed in the U.S. (reported in W.B.S.
2.3.4) were tested and validated using the testbed. The production team
also wrote scripts to integrate and adapt some of these tools for large
scale production.

Our first production target this quarter was to finish up generation of
the 2500 minimum bias files using the LSF batch system at BNL. Over
600GB of these files were produced.

Our second production target in Q2 was to re-generate 50k supersymmetry
events using the grid testbed. The sample consisted of 500 output zebra
files and occupied \~200GB disk space. 400 files were done using the
GRAT framework based on Globus middleware, and 100 files were generated
using the Chimera framework.

A major task this quarter was to set up pile-up production. During this
process, the 2500 minimum bias files were mixed in randomly with all the
GEANT simulation files generated in DC1 Phase 1. We wrote a set of
scripts, using the GRAT framework, to start this complex process on the
grid. All file transfers, including software, were done using grid based
tools.

MAGDA was used to move and catalogue every file instance on the grid,
including all input files. Many new features were added to MAGDA as
needed for our grid based production system. A MySQL production database
was developed to manage the production. Automated scripts were developed
for validation of the generated data.

First, low luminosity pile-up was done for \~500 input files. Each grid
site was pre-staged with 40 minimum bias files (\~10GB), which were
mixed in with up to 100 input files. A new minimum bias set was
pre-staged when necessary. The system worked well.

Second, we started high luminosity pile-up, where 100 minimum bias files
were mixed in with each input file. Our primary target was to process
the 2000 di-jet events for trigger studies. This sample contained one
million events with pT greater than 25 GeV. Because of maximum file size
limitations, each input file was split into 3 output files.

The high luminosity pile-up became a major 6 week long exercise on the
grid. We used five sites including BNL, LBNL, Boston U., Indiana U., and
U.T. Arlington, each with large amounts of scratch disk space. 10TB disk
was available at the BNL Tier 1 center for final file staging. Over 5000
CPU days was used to produce this \~10TB sample, fully using Globus and
MAGDA.

We learned about various bottle-necks and failure modes on the Grid.
Better data management tools are necessary to do future production at
this or larger scale. More automation of production is also needed. The
middleware needs to be more fault tolerant and fault resistant.

Simultaneously with pile-up production, the smaller sites like Oklahoma
and SMU continued to produce simulation files. Overall, this quarter was
a great success in demonstrating the use of the grid for data
production.

# Financial Report (Chuck Butehorn, BNL)

The total of funding for the U.S. ATLAS Computing Project is expected to
reach \$11,009,000 dollars during Fiscal Year 2003. The Project is
supported by DOE and NSF.

DOE program funding includes allocations from Fiscal Year 2000 through
2003, in the amount of \$8,357,000. The remaining Undistributed Budget
of \$1,422,000 will be allocated soon.

-   The NSF total funding will reach 2,652,000. As of the end of this
    quarter, \$575,000 was pending allocation.

Appendix Table 1: The details of the reported costs and reported
obligations.

Appendix Table 2: Summary of Agency funding Profile

Appendix Table 3: Summary of Allocation of Funding to Institutions

  -------------- --------------------- ------------ --------------- -------- ------- ------------
                                                                                      

  **U.S. ATLAS                                                                       
  Computing                                                                          
  Program**                                                                          

  **Summary of                                                                       
  Funds                                                                              
  Authorized**                                                                       

  **and**                                                                            

  **Total Costs                                                                      
  and                                                                                
  Commitments to                                                                     
  Date**                                                                             

  **March 31,                                                                        
  2003**                                                                             

  **(AY\$ x                                                                          
  1,000)**                                                                           

                                                                                      

                                       Funds        Expenses +                       Balance of
                                                    Commitments                      

  WBS No.        Description           Authorized   Expenses to     Open     Total   Authorized
                                       Thru FY03    Date            Commit   to Date Funds

                                                                                      

  2.1            Physics               175          103             \-       103     72

  2.2            Software Projects     6,474        6,432           168      6,600   \(126\)

  2.3            Computing Facilities  2,244        2,116           \-       2,116   128

  2.9            Project Support \*    119          102             \-       102     17

                 Subtotal              9,012        8,753           168      8,921   91

                 Anticipated NSF       575          \-              \-       \-      575
                 Additional Funds                                                    

                 Anticipated DOE       1,422        \-              \-       \-      1,422
                 Additional Funds                                                    

  2              U.S. ATLAS Computing  11,009       8,753           168      8,921   2,088
                 Total AY\$                                                          

                                                                                      
  -------------- --------------------- ------------ --------------- -------- ------- ------------

Table 1: Reported costs and commitments

  --- ---------- ---------- ---------- ---------- ---------- ----------- ----
                 Planned                                                  
                 Funding                                                 
                 (k\$)                                                   

      Agency     FY 00      FY 01      FY02       FY03       Total        

      DOE        1,266      1,785      2,441      2,865      8,357       

      NSF        655        434        988        575        2,652       

      Total      1,921      2,219      3,429      3,440      11,009       

                                                                          
  --- ---------- ---------- ---------- ---------- ---------- ----------- ----

Table 2: Summary Agency Funding Profile

![](media/image4.png){width="7.001388888888889in"
height="3.285416666666667in"}

Table 3 Summary of Allocation to Institutions.

[^1]: http://www.nsf-middleware.org/

[^2]: http://www.lcfg.org/