Difference between revisions of "Steps for Offline Activities, 12 Gev Project"

Revision as of 16:25, 29 October 2009

These are the activities in the Offline Computing section of the BIA Project plan. The same activities also appear in the 12 GeV plan.

MC Studies for Detector Optimization (5533010)

• Software optimization tools development
• CDC Optimization
• FDC Optimization
• Global tracking Optimization
• Start Time reconstruction sequencing
• Field Map Parameterization
• XML geometry access

Reconstruction Framework (5533015)

• Stream Logging
• Exception Handling
• Build System Configuration
• Memory Footprint diagnostics
• Calibration parameter storage optimization
• Documentation
• SIMD implementation

Integration of Slow Controls (5533020)

• Design application programmer's interface (API) for accessing items from experimental online database
  • The online database will be built outside the scope of this activity (an online computing activity). Here we need only access the data
• Implement API
• Integrate use of API into offline reconstruction code
  • There will be place-holder access routines that must be replaced by API calls.
• Testing
• Documentation

DAQ to Detector Transition Table (5533025)

Micro DST Writer (5533030)

Track Finding (5533045)

• prototype algorithm development
  • something that works, but not suitable for production data reconstruction
• integration into analysis framework
• design of final algorithm
• implementation
• testing
• documentation

Track Fitting (5533050)

• prototype algorithm development
• integration into analysis framework
• design of final algorithm
• implementation
• testing
• documentation

BCal Reconstruction (5533055)

• prototype algorithm development
• integration into analysis framework
• design of final algorithm
• implementation
• testing
• documentation

FCal Reconstruction (5533060)

• prototype algorithm development
• integration into analysis framework
• design of final algorithm
• implementation
• testing
• documentation

TOF Reconstruction (5533070)

• prototype algorithm development
• integration into analysis framework
• design of final algorithm
• implementation
• testing
• documentation

Tagger Reconstruction (5533080)

• prototype algorithm development
• integration into analysis framework
• design of final algorithm
• implementation
• testing
• documentation

Start Counter Reconstruction (5533085)

• prototype algorithm development
• integration into analysis framework
• design of final algorithm
• implementation
• testing
• documentation

Particle ID (5533090)

Kinematic Fitter (5533095)

Integration/QC (5533100)

• design system for source code version management
• design integration testing system
  • system for doing a combined test of various software components, e. g., reconstruction involving several detector components
• implement integration testing
• design/implement component testing system
  • The component testing system would run test on individual components of the software. Each component developer must provide a test suite that is compatible with this system
• documentation

Calibration Database(5533105)

• choose software environment/utilities
  • Things like database engine choice and server hardware choices
• design database structure
  • pure relational database design, deciding on tables and their contents
• design API
• design user interface
  • User interfaces include not only access by reconstruction routines, but also things like database editors and browswers. All should use the same API.
• implement API/user interface
• testing
• documentation

CDC Calibration (5533110)

• design procedure for measuring calibration constants
• implement design
• design and implement interface to calibration database

FDC Calibration (5533115)

BCal Calibration (5533120)

FCal Calibration (5533125)

Tagger Calibration (5533140)

Starter Counter Calibration (5533145)

Job Control Reconstruction (5533150)

Job Control/Database for Simulation (5533155)

Event Viewer (adapted from online) (5533175)

Documentation (5533180)

• no step for this activity have been identified at this time
  • Documentation steps have been included in each of the other activities