1. Trigger and online software Simon George & Reiner Hauser T/DAQ Phase 1 IDR

2. Scope – Trigger software: runs in HLT farm, selects events – Online software: DAQ and HLT infrastructure – Upgrade only; M&O excluded Plans: – Main work during 2015-2018 – Based on experience of original software, data taking, and planning LS1 S.George & R. Hauser2

3. Time line TDR (end 2013) – Will describe baseline assumptions and plan, with some potential options to consider – Some technology evaluations (e.g. GPGPU, Xeon Phi) already starting Advantage to delay technology decisions to 2016/17 – Most software upgrades will benefit from experience of development during LS1 and operational experience in 2015 – Hardware decisions best taken as late as practical - avoid being caught out by change in technology trends after decision – Lead time on software changes varies: plans will reflect this – Evaluate emerging hardware and software technologies until decision is needed Final software testing and iteration through 2018 S.George & R. Hauser3 201320142015201620172018201920202021 LS1 LS2 TDR Phase 1 Phase 1 software upgrade

4. Drivers for changes to Trigger/DAQ/HLT software (1) LHC upgrade – higher energy, luminosity, pileup Detector and T/DAQ upgrades – L1Calo, L1Muon, L1Topo – FTK – Dataflow software, network and ROS upgrades The next rolling network upgrade will be in 2018. Performance requirements – Higher rates and bandwidth throughout the system – More complex algorithms and trigger strategies to achieve necessary rejection/efficiency – More precise/frequent online conditions updates S.George & R. Hauser4

5. Drivers for changes to Trigger/DAQ/HLT software (2) External computing trends – CPU evolution, co-processors, PC architecture (memory, cores, i/o) – Networking technology and prices – Developments and possible paradigm shifts in software languages, libraries, technologies – Rise and fall of numerous free & commercial products we use Offline computing – Offline software: framework, detector, data and reconstruction code – Common infrastructure: o/s, build, compilers, libraries Turnover of people and significant evolution of requirements – Some of the TDAQ core services and HLT core software will be over 10 years old, during which time they have been extended to do things that were never imagined when first designed – Plan refactoring and replacement where needed for future maintenance and to rebuild a pool of expertise Need for increased automation – Operations procedures, scaling of expert systems S.George & R. Hauser5

6. Summary of main trigger work Trigger core software – Includes steering, data access, configuration, monitoring, analysis – Need sub-event parallel code to exploit many-core and co-processor architectures – Work closely with offline to introduce new framework before phase 1 – Expect significant effort to contribute and adapt – New challenges for monitoring algorithm performance and code analysis/debugging tools – Also expect possible changes to i/o framework and data model – Interfaces with DAQ/HLT, steering, algorithms affected Menus & algorithms – A lot of work on studies, strategy development, code development and offline code adaption. – Includes use of IBL, FTK Trigger simulation – New L1 hardware – Implications of using specialist processors online such as GPGPUs and FTK – Fast trigger simulation S.George & R. Hauser6

7. Common Trigger and DAQ/HLT work Evaluate emerging software and hardware technologies – GPGPU, other co-processors, better CPU vector engines, performance vs. cost of many-core vs multi-core – Example: GPGPU evaluation Data preparation, tracking in HLT algorithms. Gatherer in DAQ? – Redesign of software to take advantage of chosen technologies S.George & R. Hauser7

8. Trigger work packages and effort Work package2015201620172018Total Core software3.75.55.32.717.2 Evaluate and exploit new technologies3.0 2.01.59.5 Menus & algorithms10.5 8.010.039.0 Simulation1.3 5.2 Total 18.520.316.615.570.9 S.George & R. Hauser8

9. Summary of DAQ/HLT work Changes are required to HLTPU for new offline framework interface to data flow. DAQ/HLT core software, control and monitoring changes will depend on outcome of evaluation in 2015 – Some changes likely but not yet known which – Might also require many changes in detector sw that are not costed in this plan. Data flow changes will be driven by the availability/cost/capabilities of networking technology. S.George & R. Hauser9

10. DAQ/HLT work packages and effort Work package2015201620172018Total HLT Processing Unit1.00.50.4 2.3 DAQ/HLT Core Software, Infrastructure0.73.54.03.011.2 Configuration, Control & Monitoring, Web Services2.43.7 2.011.8 Data Flow, Event Format0.23.2 3.09.6 Detector and Control Room Software and Tools-0.32.52.35.1 Evaluate and exploit new technologies0.5 0.4-1.4 Total4.811.714.210.741.4 S.George & R. Hauser10

11. Developer profile Due to extensive use of new software and hardware technologies and highly technical nature of work Most work requires people with software engineering background or significant experience. Estimate about 25% of trigger work could be done by motivated physicists, mainly in menus and algorithms. S.George & R. Hauser11

12. Major Milestones End 2013: TDR End 2015: Decisions on need to renew major software components and software technology choices Early 2017: Decision on PC architecture for new HLT farm nodes End 2017: Final software release ready for testing End 2018: Ready for data taking S.George & R. Hauser12

13. Summary S.George & R. Hauser13 Total effort over 4 years (FTE): 70.9 (Trigger) + 41.4 (DAQ/HLT) See document for more details 201320142015201620172018201920202021 LS1 LS2 TDR Phase 1 Phase 1 software upgrade 4-year software plan for Phase 1