1 / 23

Summary of WP2

Summary of WP2. Plenary meeting at Kick-off AIDA meeting P. Mato/ CERN, F. Gaede /DESY. Agenda WP2 Session. Goals – ‘Common Software”.

ilori
Download Presentation

Summary of WP2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Summary of WP2 Plenary meeting at Kick-off AIDA meeting P. Mato/CERN, F. Gaede/DESY

  2. Agenda WP2 Session AIDA WP2

  3. Goals – ‘Common Software” • Develop core software tools that are useful for the HEP community at large and in particular for the next big planned projects: sLHC and Linear Collider (ILC/CLIC) AIDA WP2

  4. Partners (lead beneficiary) CERN DESY CERN, DESY, LLR, UniGla, STFC DESY, CERN, OeAW, KFKI Ucam, LLR, CERN, INFN, NTU, KFKI CERN, DESY, LLR, UniGla, STFC DESY, CERN, OeAW, KFKI Ucam, LLR, CERN, UniGla STFC Deliverables for WP2 AIDA WP2

  5. Overall Strategy • We committed ourselves to write re-usable and generic code that can be used later by the HEP community • All partner are involved in ongoing projects and develop their code in the corresponding context (ILC, sLHC) • We need to make sure that the developments are designed such that we address the current needs in these activities, while at the same time we pay attention to provide the toolkits in a standalone and well documented way • Often the developments will be done to address an immediate need for a given experiment/project but the intention is to deliver later a ‘standalone’ packaging of it fully reusable AIDA WP2

  6. Organizational Matters • Work package coordinators: Pere Mato (CERN), Frank Gaede(DESY) • Sub-tasks: • (1) Geometry, (2) Tracking, (3) Particle Flow, (4) Alignment, (5) Pile-up, PID and PR Algorithms • Coordinators will be identified • Meetings: • Face-to-Face meetings every 6 months (one coinciding with annual AIDA meeting) • At the beginning every 2 months phone/video meetings • Web site and mailing lists: • Web is already available • Collecting data to build initial mailing lists AIDA WP2

  7. AIDA WP2 PARTICIPANTS PLANS

  8. Geometry Primitives Library AIDA WP2

  9. Requirements New Toolkit AIDA WP2

  10. Geometry Toolkit • Needs to be completed with a number of tools for • Persistency • Exchange format • Visualization • Transformation from high-level to detailed geometry • Transformation to adequate format to be used by reconstruction algorithms • Alignment support • Avoiding overlaps • Etc. AIDA WP2

  11. Alignment Tools • Development of common alignment methods • Repository of algorithms AIDA WP2

  12. Tracking Tools • Development of a ‘palette’ of tracking tools covering most of the tracking detectors (TPC, pixels, DT, ...) • Targeting detector design and optimization studies AIDA WP2

  13. Tracking Tools Strategy • From now – early 2012, to be used for the ILD DBD • Experience gained will be used for the AIDA deliverable AIDA WP2

  14. RAL Contribution • RAL will make contributions to both work packages Geometry and Reconstruction AIDA WP2

  15. INFN Contribution AIDA WP2

  16. Particle Flow AIDA WP2

  17. PFA Software AIDA WP2

  18. PFA Plans AIDA WP2

  19. LLR Contribution AIDA WP2

  20. MTA-KFKI Contribution • Vertexing and PID Algorithm development AIDA WP2

  21. NTUA Contribution • Development pattern recognition algorithms AIDA WP2

  22. AIDA WP2 Conclusions

  23. Main Challenges Ahead • Make a coherent program of work out of these apparently disconnected plans • The accepted strategy • Develop with ‘generality’ in mind while designing concrete solutions to particular needs from ILC/CLIC and sLHC • Repackage/document it as a generic solution • Ensure the adequate connections between WP2/WP9/WPx • Coding standards & conventions that we wish to enforce across the collaboration • Many technical details still to be defined • Standalone tools without large duplications • Dependency of a framework? • Languages supported • … AIDA WP2

More Related