University Computing for BaBar: Funding

6
1 University Computing for BaBar: Funding Frank Porter Caltech US University PI Meeting June 22, 1999

description

University Computing for BaBar: Funding. Frank Porter Caltech US University PI Meeting June 22, 1999. Introduction. US Universities need to participate in BaBar analysis, simulation, software development Different models for doing this Needs to be funded DOE apprised of need - PowerPoint PPT Presentation

Transcript of University Computing for BaBar: Funding

Page 1: University Computing for BaBar: Funding

1

University Computing for BaBar: Funding

Frank Porter

Caltech

US University PI Meeting

June 22, 1999

Page 2: University Computing for BaBar: Funding

Frank Porter 990622 2

Introduction

US Universities need to participate in BaBar analysis, simulation, software development

Different models for doing this Needs to be funded DOE apprised of need Actual experience so far not terrific

Page 3: University Computing for BaBar: Funding

Frank Porter 990622 3

What has been done?

Spring 1998 - US PIs asked L.Gladney, B.Meadows, F.Porter to draft report on university computing for BaBar.

Summer 1998 - Report completed:

~frankp/tex/babar/collab/univcomp.ps

~frankp/univcomp.xls

December 11 1998 - D.Hitlin, F.Porter, T.Schalk visit DOE to discuss university computing for BaBar.

doe9812.ps, doe9812GAF.ps on frankp web page at SLAC

PK supportive, but suggests time-stretch, importance of university matching funds.

Page 4: University Computing for BaBar: Funding

Frank Porter 990622 4

Title:doe9812GAF.figCreator:fig2dev Version 3.1 Patchlevel 2Preview:This EPS picture was not savedwith a preview included in it.Comment:This EPS picture will print to aPostScript printer, but not toother types of printers.

Page 5: University Computing for BaBar: Funding

Frank Porter 990622 5

Experience Summary

Page 6: University Computing for BaBar: Funding

Frank Porter 990622 6

Conclusions

DOE has BaBar university computing document, proposal may refer to it

DOE response is generally supportive of need, but Time lags, stretchout Matching (1:1) typically expected