1 / 8

Status of Brunel team and next steps

This update discusses the current status of the Brunel team and outlines the proposed next steps. It includes the introduction of C++ functionality, tracking digitization and reconstruction, improved tracking simulation, essential tool for optimization, and output formats. The update also highlights the original proposal, frequent team meetings, and feedback from sub-detectors. Additionally, it suggests a modified proposal with monthly topical workshops and regular project meetings.

virgiep
Télécharger la présentation

Status of Brunel team and next steps

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. Status of Brunel team and next steps Brunel v2 Brunel team Topical workshops Project meetings

  2. Brunel v2 • First version with added C++ functionality w.r.t. SICBDST • Likely candidate: tracking digitisation and reconstruction • Improved tracking simulation incompatible with SICBDST • Essential tool for tracking optimisation • Backward compatible if AXTK created from Brunel • Output formats: • Existing SICB ZEBRA file? • Full ROOT based DST? • Requires completion of data-model • ROOT based MINI-DST?

  3. Brunel team • Original proposal: • OO reconstruction representatives from each sub-detector • Frequent (~weekly) team meetings to make progress on: • Project plan (milestones and deliverables) • Program structure • Common issues • Event data model, Geometry, Common language, Common Tools etc. • Feedback from sub-detectors: • Decisions on common issues are urgent • Weekly meetings unacceptable (too CERN-centric)

  4. Brunel team: modified proposal • Sub-detector OO contacts remain mandatory • Primary contact with team leader • Has responsibility to attend meetings, respond to E-mail etc. • Should delegate whenever appropriate • Monthly “topical” workshops • One or two days • not necessarily at CERN, with telephone conferencing? • Decision making forum for common issues • One common issue per workshop • Alternative proposals, toy studies prepared in advance • All interested parties must be represented • Goal is to reach agreement • Documented, binding (at least until next iteration...) • Project meetings every 3-4 months

  5. Topical workshop IProposal • End July - Event data model • Reach agreement on event structure • e.g. Is MonteCarlo, FrontEnd, Raw, Reconstructed, Analysis OK? • First definition of common classes • e.g. Tracking hits, Tracks • Updating strategies • Reach agreement on naming conventions • e.g. Consistent naming of classes and methods, functionality • L0Calo2x2Sum, MCCaloSummedDeposit • VeloCluster->width(), CaloCluster->size() • Reach agreement on common approach to navigation from raw+reconstructed data to MC truth • e.g. Digitisings to MC hits, Clusters to MC Hits, Tracks to MC particles • Inheritance, reference table, association etc.

  6. Technical workshop IIProposal • End August - Alignment and Calibration strategies • Required infrastructure • Geometry and conditions database design • Ideal detector? Survey measurements? Alignment results? • Impact on event and detector data models • Strategy for online calibration / alignment • Impact on Brunel structure • Strategy for MonteCarlo • Perfect Montecarlo? Misaligned? Smeared? • Impact on Brunel • Initiate an alignment working group?

  7. Project meetingsProposal • Review progress in collaboration weeks • Milano: • Retirement of SICBDST • Status of Brunel v2 • Feedback from topical workshops • Organisation of October workshop • Project meetings in software weeks • To review progress and define milestones • To identify “topical” issues • 1-3 November: • Release of Brunel v2 • Planning for Brunel v3 • Planning for next topical workshops • What about project tracking? • Status reports at weekly software meeting? • Can be sent by E-mail

  8. Discussion • SICBDST retirement • C++ migration priorities • Brunel team and topical workshops

More Related