Download presentation
Presentation is loading. Please wait.
Published bySilas Garrett Modified over 9 years ago
1
BES III core/reconstruction software planning for Release 3.0 BES III core/reconstruction software planning for Release 3.0 Li Weidong 2003.12.3
2
3 December 2003BES III Software Meeting2 Release 3.0 Plan Release contents Raw Event Format Identifier Geometry Information Service Geometry information database access Raw Event Data Model (MDC, EC, dE/dx and MC) Part of reconstruction code (MDC, EC, dE/dx and MC) Time schedule beginning of December 2003 to mid of January 2004
3
3 December 2003BES III Software Meeting3 Raw Event Format who: Zhang Xiaomei dependences: a key and fundamental package risks: lots of validation and test work will be involved. backup plan: Previous Event I/O service status: A few Discussions with Zhu Kejun Work out a proposed event format Implementation design is in progress
4
3 December 2003BES III Software Meeting4 Identifier who: Li Weidong how: Identifier value is a simple 32 bit unsigned integer. Identifier helper class provides methods to generate or decode an identifier for the different levels of the detector element hierarchy. status: basic idea was presented in the software meeting 19/11/03 further discussed with Shilei, Wangzhe and Xiaomei first implementation is ready waiting for integration into Geometry Service
5
3 December 2003BES III Software Meeting5 Geometry Service who: Zhang Xiaomei and Li Weidong how: Define common interfaces for different sub-detectors Data caching ability One service per sub-detector system dependencies: Qiumei’s Database access code MDC, EMC and MC geometry data class risks: may not provide a unified interface for both Rec and M.C. applications, but Rec algorithm developers can use those services. status: Initial discussions started (Shilei, Dayong, Wangzhe, YuanYe and Chengdong)
6
3 December 2003BES III Software Meeting6 DC reconstruction who: Zang Shilei how: Retrieve Geom information and store them in the Rec module Write partially-functioned or dummy modules to form the skeleton of track reconstruction. dependencies: Geometry Service, Database Access, Raw Event Format packages risks: Time is tight and the dependencies. backup plan: Generate single track event; write some basic classes for track finding module. status: Geometry data classes have been designed. ref: Belle CDC Rec modules and panther tables
7
3 December 2003BES III Software Meeting7 dE/dx Reconstruction who: Wang Dayong how: Refine the main packages of the dE/dx Module to the level of public members and methods Implement and test database I/O interface of dE/dx Data Co-design and share Geo and Rec data format with Zang- Shilei and YuanYe; databse I/O test with Ma Qiumei risks: Foundation of the correction models not so sure. backup plan: Try best to raise the refinement; Otherwise limited and branch methods at the time also fulfill the requirements of system test. status: The first version with only skeleton of branch methods finished and is being test
8
3 December 2003BES III Software Meeting8 EMC reconstruction who: Wang Zhe how: Event Model; Environment Model; MakeShower dependencies: Identifier, MC EMC hit, Database risks: Geometry, MC EMC hit backup plan: fake Geometry, fake hit status: Event Model finished ref: Belle ECL reconstruction software
9
3 December 2003BES III Software Meeting9 Database Access who: Ma Qiumei how: Following the successful implementation for MC, build the geometry database of DC and EMC and provide interface programs. dependencies: Geometry data files from DC and EMC software developers status: The geometry database for MC has been setup and the corresponding geometry service available to MC Rec module. Design and preparation are in progress
10
3 December 2003BES III Software Meeting10 CMT who: Teng Tao how: Start some experiment and initial work in consultation with Xingtao and Xiaomei. Write requirement files package by package. The current directory structure may need small modification. risks: lack of technical expertise and may not work for the whole system. backup plan: automake compile system status: CMT tool has been installed and works well Study on CMT is in progress ref: CMT manual and Gaudi and Athena examples
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.