Projects, Tools and Engineering Patricia McBride Computing Division Fermilab March 17, 2004

P L McBride Operations Review2 Projects, Tools and Engineering There are a number of division activities that are either common to several experiments or require developments that take advantage of specific software or engineering expertise. Stakeholders: Experiments, Accelerator Division, Computing Division Objectives: –Encourage the use of common tools by several experiments – sometimes this is not possible –Development of new techniques Activities: –Development, consulting, support, and distribution of software components –Design, production, and support of electronic components or systems

March 17, 2004P L McBride Operations Review3 CD Project Areas Some examples areas of work: –Core software for experiments: ~ 8 FTEs + exp. departments Framework, Databases, Compilers –Physics Analysis Software ~4 FTEs C++ class libraries, ROOT, Visualization –Online software, Trigger&DAQ ~4 FTEs –Collaboration Tools ~ 1.5 FTEs Electronic logbook –GRID Applications ~3 FTEs (mainly externally funded) –Data Management ~8 FTEs + the FTEs for SAM –Electronics for experiments ~1 FTE Run II and run II upgrades –Accelerator support ~15 FTEs –CD infrastructure ~8 FTEs Effort reporting, equipment support

March 17, 2004P L McBride Operations Review4 Projects on the web

March 17, 2004P L McBride Operations Review5 CD Project monitoring We attempt to capture the development and support activities in the division through project monitoring. Through this process we –define project goals and status, –define beginning and end(!) of projects Status reports –Written by project leaders, posted on web –Meetings to review the status are held periodically Briefings –Meetings to discuss new projects or major changes to projects Project Web pages –available to all –Record of the status and accomplishments for each project

March 17, 2004P L McBride Operations Review6 Support and maintenance We try to concentrate our support efforts on tools and components needed by the ongoing experimental program. –Support for ROOT is one example. Used by almost Run II, Minos, Miniboone, etc. –A core component in many cases FTE for critical ROOT development, user support and distribution –Highly successful effort Support will be required over an extended time. –Active mailing list for questions, issues (3/day on –Meet every 3 months with experiments to set priorities –Also meet annually with the full ROOT team and other users at the annual ROOT workshops Many important products are HEP specific –Share support with other labs and institutes CLHEP, GEANT, GRID –Share the support with the experiments C++ Working Group works this way (KAI to GCC migration) Often this support is done through mailing lists

March 17, 2004P L McBride Operations Review7 Simulation and Modeling Generator support (pythia and others) –Provide support for CDF and D0 (and CMS) –The patriot project provides physics MC data sets that have been “approved” by the experts. This project will use central facilities to produce and store data files. Detector Simulation –GEANT3 – minimal support (0.1 FTE) Used by most experiments at Fermilab Distribute the product through UPS/UPD Provide support through mailing lists –GEANT4 – minimal support (0.3 FTE) Used by CMS (maybe BTeV) Distribute though UPS/UPD upon request Validation studies for CMS using test beam data has been done here. Could do more if more manpower was available and the experiments demanded new features. –Important for LHC and other future experiments. Accelerator Simulations

March 17, 2004P L McBride Operations Review8 Accelerator Support Projects Many small projects in FY03 (3-6 months) –Recycler BPMs, Booster Monitoring, Document Database,… Current involvement FY04 (15 FTEs): –Simulations: Modeling of Space Charge in Booster(SCIDAC) –Shot Data Analysis: Tools and Analysis –Tevatron BPMs –Ionization Profile Monitors –Orbit Smoothing –Magnet Database (BLASTdb) –Support for Labview, VXworks Possible Future projects (under discussion) –Controls system migration to unix (waiting for technical review) –Main Injector and other BPMs –Beam Beam simulations for Tevatron –Infrastructure to make lattice calculations in the control room

March 17, 2004P L McBride Operations Review9 Accelerator Support since July ‘03

March 17, 2004P L McBride Operations Review10 TeV BPM Project Hardware: We are replacing the readout electronics. Echotek boards similar to the boards used for the recycler BPMs will be installed in Tevatron support buildings. Software: front-end, control room applications, “offline” Challenge: to measure antiproton positions in the presence of a large proton signal CD scientist R. Kutschke (assigned to BTeV software) stepped in to solve this critical problem. He should be able to return to BTeV in the summer S. Wolbers – Project Manager B. Webber – Deputy Project Manager J. Steimel – Technical Coordinator B. Banerjee – Project Assistant J. Nicholls – Project Assistant Electronics Vince Pavlicek Front-End/ DAQ Software Margaret Votava Online Software Brain Hendricks Offline Software Rob Kutschke Requirements Mike Martens From AD 3-5 FTE From CD 4-8 FTE Sept 03-Dec 04

March 17, 2004P L McBride Operations Review11 TeV BPM Project Tracking

March 17, 2004P L McBride Operations Review12 Conclusions Large number of active projects in the Computing Division There is always a list of potential projects – important to set priorities. Projects are started/ended after consultation with the experiments or the accelerator division Projects are monitored by division management and reports are available to all.

March 17, 2004P L McBride Operations Review13 Additional Slides

March 17, 2004P L McBride Operations Review14 Status Reports CRL Projects page:

March 17, 2004P L McBride Operations Review15 TeV BPM project Effort Reports:

March 17, 2004P L McBride Operations Review16 TEV BPM status

March 17, 2004P L McBride Operations Review17 BLASTdb project reporting BLASTdb Accelerator Magnet Database Short Description of Project: Create and do early populating and critical applications for a modern and maintainable unifying several sources of magnet and alignment data "owned" by Accelerator and Technical divisions. Milestones agreed on are: 0. Agreement on what we are doing. 1. Creation of good database, meeting agreed key purposes a) Repository for the data previously in N. Gelfand's database b) Adequate scheme for accepting new survey data c) Repository for some part of the "other" data that AD has currently in pseudo- and real databases. Use case applications for populating and simple access. 2. Refinement of that database, for decent performance, completion of schema to include all the critical data categories, and incorporation of all formulas needed for users to convenientlyaccess data in their prefered forms. 3. Incorporation of other data sets for maximal usefulness to AD and TD. Project Status: Ongoing

March 17, 2004P L McBride Operations Review18 Current engineering support projects