B. Unless a specific arrangement has been otherwise negotiated, each institution will be responsible for maintaining the code and computing infrastructure supplied by them. Each institution will further insure that a manageable fallback position exists so that data-taking, data production, and analysis can continue in the event of component failure.
1. Reconstruction and simulation algorithms for the silicon vertex detector.
2. Fast, efficient Level 3 trigger algorithms, based on the standard offline code, but modified as necessary to optimize performance at L3.
3. Studies and validation of the performance of the L3 algorithms, and development of online monitors and other software required for efficient oversight of the code performance throughout the data taking period.
4. Evolution of the L3 trigger for maximum physics performance over the period of Run II.
The Run II Offline, Online, L3, and TDSWG groups meet weekly at Fermilab, and the Oxford will be periodically requested to report on progress and status of this project at these meetings.
This document describes the responsibilities of Oxford University. The Oxford contact persons are Todd Huffman and Armin Reichold.
The Run II Offline Manager is Marjorie Shapiro. The Run II Online Project Leader is Jim Patrick, and the L3 leaders are Kevin McFarland and Gerry Bauer. These managers have authority over the work outlined below, and make the final sign-off that responsibilities have been faithfully discharged.
* Benchmark and improve speed performance of the silicon tracking.
* Implement and manage regional reconstruction in the silicon tracking.
* Implement and manage programs to verify track quality for i.p. based triggers
* Incorporate into the L3 silicon reconstruction other specialized concepts related to the use and needs of the SVT trigger
* Implement and manage programs to verify in a global way other triggers based on silicon tracks at L3.
* Develop monitors and other software required for efficient oversight of the code performance throughout the data taking period.
* Interface to the Physics Groups as required by the above.
* Make apropriate modifications to the CDF simulation to support the above tasks.
* Supply a computer for L3 code validation and L3 code distribution.
12/98 -- Implementation of Profiling Tools in the standard Si code,
\& and distribution & maintenance of tools through Run II
-- Implementation
of wedge/layer/barrel based regional clustering
1/99 -- Implementation of framework in the Run II Silicon Simulation
for
-- Track/Min Bias embedding
-- Noise simulation with
adjustable parameters
This work is the design of an open platform or framework which will allow users to design and include min bias and noise models as desired.3/99 -- Implementation of wedge/layer/barrel-based regional reconstruction Si code
6/99 -- Implementation of code to manage regional reconstruction, including SVT interface and multi-pass regional reconstruction
12/99 -- Delivery of programs which will run online to verify efficiency of Si reconstruction/cuts in Level-3. These programs will be designed to "plug-in" to the generic online consumer framework to be delivered by the MIT, Rochester, and Online groups.
4/00 -- Full responsibility for the continued development of the L3 silicon reconstruction as the CDF trigger evolves over the course of Run II, to incorporate new triggers, to improve sensitivity and purity, and to accomodate increases in Tevatron luminosity.
4/00 -- Delivery of manpower during the data taking to monitor L3 silicon performance, address problems arising, and contribute to daily operations as appropriate.
All parties agree that the operation and maintenance of this code is an institutional responsibility of Oxford University as long as it is a member of the CDF Collaboration, independent of personnel changes at Oxford.
n.b. At time of this signing, we understand this agreement is contingent
on Oxford's receipt of support from UK funding sources
___________________________________
_____________________
Group Leader from University of Oxford
date
___________________________________
_____________________
Offline Project Leader
date
___________________________________
_____________________
L3 Project Leader(s)
date
__________________________________
______________________
CDF Spokesman
date
__________________________________
______________________
CDF Spokesman
date