1 / 8

Current Status and Future Directions of the BESF Framework Development

This document outlines the current status of the BESF framework, focusing on various components like BesKernel for data processing, UserInterface for command history, and BesMessageSvc for logging information. It discusses EventIO compatibility with different data formats and highlights tools such as Histogram service, BesDatabaseSvc, and ProxyDict for data management. Future work areas include improving geometry access, event data models, and performance measurements. Emphasis is also placed on design, documentation, and effective team collaboration in large-scale software development.

alec
Télécharger la présentation

Current Status and Future Directions of the BESF Framework Development

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. BESF Framework Development Weidong Li 2003.11.19

  2. Current status • BesKernel that controls data processing application • UserInterface copes with user’s interactive command history • BesMessageSvc provides facilities for the logging of information, warnings, errors etc. • EventIO which supports panther, “raw data” and BES II NDST formats • Histogram service histogram and N-tuple facilities • BesDatabaseSvcfor accessing geometry information stored in database • ProxyDictnew data management system • Parallel processing was removed

  3. Raw Data Flow in BES III

  4. Code reuse in Offline and EF

  5. Future working areas (1) • Accessing BES III geometry information • see previous talk • Event Format package • cope with byte stream data from network and data files • reusable in event filter, offline reconstruction and MC simulation domains • Byte Stream Conversion Service which provides friendly interface for • raw data unpacking • raw data serialization

  6. Future working areas (2) • Event Data Model • Raw Data (Digits, TDC …) • Prepared Data (EMC clusters …) • Reconstructed Data (Tracks, Showers … ) • Accessing simulated MC Truth information • needed for checking the pattern recognitionquality in DC and EMC etc

  7. Future working areas (3) • Performance measurements utilities • benchmarking • profiling • Accessing “alignment data” for algorithm robustness study • Assess if panther meets the requirements of EF

  8. Other issues • Lack of manpower • Design and documentation are important for a large-scale software development. • Recommended UML toolkits: Microsoft Visio and IBM Rational Rose 2003 • Design walk-through is also important • How to organize software development • more sophisticated release administration tool (like CMT used in Gaudi/Athena) • teamwork • “open” management environment

More Related