BES III core/reconstruction BES III core/reconstruction software planning for Release software planning for Release

3.03.0

Li Weidong

2003.12.3

3 December 2003 BES III Software Meeting 2

Release 3.0 PlanRelease 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 December 2003 BES III Software Meeting 3

Raw Event FormatRaw 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

3 December 2003 BES III Software Meeting 4

IdentifierIdentifier

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

3 December 2003 BES III Software Meeting 5

Geometry ServiceGeometry 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)

3 December 2003 BES III Software Meeting 6

DC reconstructionDC 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

3 December 2003 BES III Software Meeting 7

dE/dx ReconstructiondE/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

3 December 2003 BES III Software Meeting 8

EMC reconstructionEMC 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

3 December 2003 BES III Software Meeting 9

Database AccessDatabase 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

3 December 2003 BES III Software Meeting 10

CMTCMT

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