Difference between revisions of "Steps for Offline Activities, 12 Gev Project"
From GlueXWiki
(add header fonts) |
(intermediate) |
||
| Line 1: | Line 1: | ||
| + | These are a subset of the activities in the Offline Computing section of the 12 GeV Project plan. The same activities also appear in the BIA plan. | ||
| + | |||
==Integration of Slow Controls (5533020)== | ==Integration of Slow Controls (5533020)== | ||
| − | * Design API for accessing items from | + | * 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 | * Implement API | ||
* Integrate use of API into offline reconstruction code | * Integrate use of API into offline reconstruction code | ||
| + | ** There will be place-holder access routines that must be replaced by API calls. | ||
* Testing | * Testing | ||
* Documentation | * Documentation | ||
| Line 10: | Line 14: | ||
* prototype algorithm development | * prototype algorithm development | ||
| + | ** something that works, but not suitable for production data reconstruction | ||
* integration into analysis framework | * integration into analysis framework | ||
* design of final algorithm | * design of final algorithm | ||
| Line 19: | Line 24: | ||
* prototype algorithm development | * prototype algorithm development | ||
| + | ** something that works, but not suitable for production data reconstruction | ||
* integration into analysis framework | * integration into analysis framework | ||
* design of final algorithm | * design of final algorithm | ||
| Line 27: | Line 33: | ||
==Integration/QC (5533100)== | ==Integration/QC (5533100)== | ||
| − | * design system for version management | + | * design system for source code version management |
* design integration testing system | * design integration testing system | ||
| + | ** system for doing a combined test of various software components, e. g., reconstruction involving several detector components | ||
* implement integration testing | * implement integration testing | ||
| − | * design/implement component 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 | * documentation | ||
| Line 36: | Line 44: | ||
* choose software environment/utilities | * choose software environment/utilities | ||
| + | ** Things like database engine choice and server hardware choices | ||
* design database structure | * design database structure | ||
| + | ** pure relational database design, deciding on tables and their contents | ||
* design API | * design API | ||
* design user interface | * 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 | * implement API/user interface | ||
* testing | * testing | ||
Revision as of 14:10, 16 September 2009
These are a subset of the activities in the Offline Computing section of the 12 GeV Project plan. The same activities also appear in the BIA plan.
Contents
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
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
- something that works, but not suitable for production data reconstruction
- integration into analysis framework
- design of final algorithm
- implementation
- testing
- documentation
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 (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
PWA Development (5533160)
- Install PWA system components locally
- Test installation
PWA Challenge (5533165)
- develop scope
- choose appropriate platform
- collect and assemble components
- develop metrics and tools for evaluation
- production
Documentation (5533180)
- no step for this activity have been identified at this time
