1. Reporting of the Experiments Follow procedures set up for technical WP of EDG Spreadsheet report man month effort Pro-forma reply sheet Pro-forma sheet slight change in emphasis from EDG Pete to approach expt & re-assess deliverable & dependencies Dry run with LHCb Introduce report back procedure about behaviour & experiences of: Middleware Tier centres Introduce reqts on expt in the next 3 months of the: Middleware Tier centres

2. Man effort useful to keep track of contribution to project outside of GridPP funding regime

3. Pro-forma reporting For Section 1: “Technical achievement ” Please summarise below all work done by “GridPP” staff during this quarter. Also describe any “ issues” which have arisen. C Cioffi: Attended GAUDI course. Installed and familiarised himself with the GAUDI s/w framework. Attended LHCb s/w week. Discussion on design /use requirements for addressing physical/logical filename services with N Brook(Bristol) & M Frank(CERN) A Soroko: Attended GAUDI course. Familiarised himself with Gaudi framework. Attended LHCb s/w week. Started work on requirements for GANGA and review of existing technologies. K Harrison: Started work on requirements for GANGA and review of existing technologies.

4. Pro-forma reporting For Section 2: “Status of deliverables and milestones” Describe the status of the deliverable for which GridPP post(s) is responsible, at a level of detail appropriate to closeness of delivery date. Also provide the schedule information in the table Deliverable name Actual deliver- able PlanTargetActual Persistency servicesReqt docsEnd of May GANGAReqt docsEnd of March End of June The delivery of requirements document on persistency services is on schedule. The GANGA requirements documents have slipped due to the fact that A Soroko began March 1 st and K Harrison began March 10 th.

5. Pro-forma reporting For Section 2: “Status of deliverables and milestones” Describe any changes in the deliverables In addition to the production of requirements document, after a joint meeting between ATLAS & LHCb (CERN – March 7 th 2002) it was felt necessary to also perform a technology review (i.e. existing tools being used by ATLAS & LHCb in distributed computing)

6. Pro-forma reporting For Section 3: “Achievements” Describe any tangible which falls under the following headings: Conference/workshop organised Conference talks Submission of papers Release of Software Package/Tools

7. Inter-Dependencies LHCb/ATLAS GANGA/Gaudi Project The following milestones are scheduled for this project for the 1 st 12 months. Listed in italic in brackets are the dependencies on EDG software/work packages. 3 months, March 2002: Study and determine the analysis environment Study the procedures for MC production Write detailed requirements, architecture and design Technology review 6 months, June 2002: First prototype modelled on current Atlas and LHCb production tools, using DataGrid job submission (WP1 tools - already exist) data move (replica) and (WP2 tools due end March’02 + TestBed2 release) catalogue services. (WP2 tools due end March’02 + TestBed2 release) Design Ganga GUI (Html page). Remote mass storage write capability (Dependent on remote RFIO from WP5)

8. Inter-Dependencies LHCb/ATLAS GANGA/Gaudi Project The following milestones are scheduled for this project for the 1 st 12 months. Listed in italic in brackets are the dependencies on EDG software/work packages. 3 months, March 2002: Study and determine the analysis environment Study the procedures for MC production Write detailed requirements, architecture and design Technology review 6 months, June 2002: First prototype modelled on current Atlas and LHCb production tools, using DataGrid job submission (WP1 tools - already exist) data move (replica) and (WP2 tools due end March’02 + TestBed2 release) catalogue services. (WP2 tools due end March’02 + TestBed2 release) Invent syntax of generic script, and write a program that creates scripts from it. Make scripts crash proof. Design Ganga GUI (Html page). Remote mass storage write capability (Dependent on remote RFIO from WP5)

9. Expt Feedback Mechanism Computing Element Performance: Tier1/A Tier2 Storage Element Performance: Disk Mass storage Network Response: Reliability Bandwidth Functionality of middleware: Scheduling Data Management Monitoring Services Mass storage Network & services Applications s/w: S/w framework (eg GAUDI, SAM,…) Expt specific tools Report back on experiences and planning for next 3 months

10. Procedures 1.Data collation (and chasing) - Nick 2.Data interpretation – Nick & Roger [~2 weeks before EB meeting] 3.Data processing  EB report. EB & TB will meet on same day. (Parallel meetings in morning joint session in afternoon) - Nick & Roger & others 4.Feedback [long-term & annual] Nick & Roger & Pete &Tony