1. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter1 Status Report APD Meeting July 26, 2007 Jean Slaughter

2. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter2 Basic Question How can Fermilab people effectively participate in the LHC? Three distinct but related activities LARP LHC@FNAL McGinnis Proposal (new coherent and forceful formulation of “old” ideas)

3. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter3 LARPLARP Collection of activities Magnets Accelerator Systems ( V. Shiltsev) Instrumentation (A. Ratti) Commissioning (M. Syphers) Collimation (T. Markiewicz Accelerator Physics (W. Fischer) U.S. Effort – BNL, FNAL, LBNL, SLAC

4. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter4 Commissioning Activities Trips to CERN Build connections Investigate projects Research practical aspects Several documents in LARP DocDb larp, sevenon7 Participate in LHC@FNAL Instigated by Alvin Tollstrup E. Harms, E. McCrory, J. Slaughter from AD Other advisors (V. Shiltsev, J. Patrick,….

5. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter5 Four types of collaboration 1.Deliverables - person builds something, visits to install, debug, etc., then leaves; may need remote access 2.On-site Commissioning - person has moved to CERN (for ~1 year, say) and works daily with LHC group 3.1-on-1 Contacts - person works with a particular person or group located at CERN, with occasional trips to CERN to participate in a study, etc. 4.Remote Participation - person is part of a group at Remote Site, participating daily for shorter time periods "Training” can be performed at the Remote Site; periodic, shorter trips to CERN working with the "On-site" commissioners; people can continue to work remotely upon return

6. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter6 Model Four Commissioning Team at CERN LARP Team Member Remote Site Critical Mass: people, consoles, video/audio, eLogs, meeting space, coffee, etc. collaborative beam studies “real time” off-line analyses periodic shifts special responsibility for communication with Remote Site Issue – how to make it happen?

7. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter7 LHC@FNAL Status Remote Access Center for both CMS and LHC Design approved by Director and money found Construction starts ~Aug 19, 2006 E. Harms is project manager Erik Gottschalk is in charge of consoles, computers, projectors, etc. Console furniture arrives Nov 1, 2006 Ready for (limited) use Jan 1, 2006 http://cd-amr.fnal.gov/remop/remop.html

8. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter8 LHC@FNAL – LARP/LHC needs CCC Model the CCC at CERN speed assimilation prior to stays at CERN ease in remote participation in studies ‘service after the sale’

9. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter9 LHC@FNAL – Floor plan

10. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter10 LHC@FNAL – renderings

11. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter11 LHC@FNAL – Floor plan

12. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter12 LHC@FNAL – Isometric view

13. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter13 LHC@FNAL – Consoles

14. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter14 LHC@FNAL – view from Atrium

15. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter15 LHC@FNAL – Wall display

16. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter16 LHC@FNAL – Window display

17. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter17 LHC@FNAL Integration Task Force Replaces LHC@FNAL Task Force Draft charge and membership sent to Pier Oddone for final approval Subgroups Engineering LHC CMS Outreach

18. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter18 Integration Task Force Jobs coordinate ongoing activities to complete construction of Phase 1; develop a plan for hardware and software tool development; develop requirements and cost estimates for Phase 2; develop requirements for outreach; develop a plan to support CMS and LHC/LARP commissioning activities; produce a list of capabilities that LHC@FNAL will provide for CMS and LHC/LARP, and an explanation of how these capabilities have been, or will be, achieved; develop an operations model for CMS and LHC/LARP that integrates the three functions of LHC@FNAL; develop a support model for LHC@FNAL infrastructure; and develop an organizational structure that identifies roles and responsibilities.

19. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter19 Outreach Working Group Charge from Director Identify the scope of LHC@Fnal outreach Identify the audience Decelop requiremnts to be incorporated in Phase II Working group members Fred Ullrich, Kurt R. Marge Bardeen, Liz Quigg, Sue Sheehan Erik gottschalk, Alvin toollstrup Jean Slaughter(chair)

20. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter20 Current OWG Activities Developing scenarios Tour related Conference related Middle School and High school tours VIP tours (President \Bush, etc.) Senior citizens Technical groups Non-tour related Accidental tourist – biker, birder, walker… Intentional tourist – science junkie Fermilab staff, technical, non-technical

21. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter21 Will LHC@FNAL be Useful? Obvious “yes” for CMS. ROC is a prototype. Obvious remote monitoring activities “Maybe” for LHC Solve security issues Run applications in “read-only” mode Access to data Critical mass of involved people McGinnis proposal practical approach

22. Accelerator Physics Department Meeting July 26, 2006 Jean slaughter22 Dave McGinnis Initiative Fortuitous meeting at CERN of Dave and Suzanne Gysin Addresses many of the concerns I’ve had over the past year regarding LARP commissioning activities and the use of LHC@FNAL for LHC. Recognizes two important facts Software is vitally important to commissioning a machine We have to contribute useful stuff to CERN to be engaged.

23. f LHC Software at Fermilab Goal  Fermilab wants to be involved in the commissioning and operations of the LHC.  For example, we are making a substantial investment in remote operations  It is difficult for outside visitors from other labs to make important contributions once beam commissioning has started. Unfamiliarity with the control system Critical problems are assigned to in-house staff.  Fermilab will be much more welcomed at CERN if it:  Can bring real resources to the table  Has the ability to solve operational problems

24. f LHC Software at Fermilab Accelerator Software  One possibility is to develop a suite of software products to enable Fermilab accelerator physicists to make key contributions to the beam commissioning of the LHC.  Fermilab has a wealth of experience in the software issues of running a collider complex  Comparable to the LHC, a significant portion of the Fermilab control system is based on Java  Fermilab has a large pool of software expertise to draw on.  A number of LARP hardware deliverables will require substantial software investment to make them useable. It might be unlikely that the software effort needed for these projects will receive a high priority from CERN

25. f LHC Software at Fermilab Lessons Learned from Run II  The importance of flexible “control room” software during Run 2 cannot be overstated.  It is impossible to foresee all the software applications necessary for commissioning before commissioning begins.  A framework is required that permits quick and flexible application development by machine physicists.  A mature shot data analysis framework must be available on Day 1 of LHC beam commissioning.  There is little need to diagnose the accelerator when things are working well.  It is difficult for outside visitors from other labs to make important contributions once beam commissioning has started.  Unfamiliarity with the control system  Critical problems are assigned to in-house staff.

26. f LHC Software at Fermilab Software Product Types  Specific programs needed by CERN  Developed in cooperation with CERN and under the leadership of CERN  Gives Fermilab access to the LHC control system  Programming environments and operational tools  Developed for the CERN control system  Aimed for use by Fermilab accelerator physicists initially CERN will initially be reluctant to use software developed from the outside  Designed for the eventual use by CERN staff once CERN realizes the benefit of the software  Accelerator Physics Modeling Code

27. f LHC Software at Fermilab Possible Software Products  Specific programs needed by CERN  SDA and OSDA  Role Based Access  Sequencers  Programming environments and operational tools  Synoptic Displays  GUI Application Builder  Accelerator Physics Code  CHEF, OPTIM

28. f LHC Software at Fermilab Software Products  SDA and OSDA  The most important products.  CERN has already expressed a strong interest in collaborating with Fermilab on SDA  Fermilab’s SDA and OSDA are written Java and might be straightforward to adapt to the CERN control system  Will have to develop the concept of “states” or “cases” at CERN  Role Based Access  This software is crucial for any outside collaboration to work on the LHC  As CERN begins to realize how vulnerable the LHC is to external settings, this software will become critical to maintain central control of LHC while still preserving the flexibility of remote monitoring and diagnostics.

29. f LHC Software at Fermilab Software Products  Synoptic Displays  Replace the Fermilab practice of “personalized” parameter pages with easily personalized synoptic displays Easy to use and personalize for both operators and engineers Takes advantage of high level data pool management. Avoid the pitfalls of using “LABVIEW”-like front ends  GUI Application Builder  Provides a graphical and menu based development environment for rapid application development by machine physicists  Similar to Visual Basic or Visual C++  Has access to a library comparable to CLIB for gathering accelerator data (BPMs, magnet settings, etc..)

30. f LHC Software at Fermilab Software Products  Accelerator Physics Code  CHEF, OPTIM, etc.. Graphical user interfaces to lattice calculations Advance calculation tools Interface to control system

31. f LHC Software at Fermilab LHC Software Team Composition  Computer Professionals  1.5 FTE’s from AD  1.0 FTE’s from CD  Operational Experts  Can write code  1.0 FTE’s from AD  Accelerator Physicists  Can write code  1.0-1.5 FTE’s  With 0.5 FTE as the team leader  This project would last 2-3 years  At least until the LHC is commissioned  The workload will change as LHC commissioning progresses  Demand for computer professional effort will be high at the beginning of the project.  Demand for operational specialist and accelerator physicist effort will increase as the LHC commissioning matures

32. f LHC Software at Fermilab Initial Team Tasks  Develop expertise on the CERN control system  CERN is pleading for experienced Java programmers to assist them with their current programming loads see last LHC-Mac presentation by P. Charrue  We should assign at least 1.5 FTE’s to help CERN Spend 35% of their time at CERN  These FTE’s in return become the liaisons with CERN Knowledgeable on the CERN control system Knowledgeable on CERN needs Builds good will with CERN  Further define:  software products  scope of work  resources required