CMS software organisation

Date:       Tue, 26 Apr 94 17:27:58 SET
From:       MARICA@cernvm.cern.ch
Subject:    CMS software organisation

Dear Colleagues,

The following message is sent to the full CMS LIST. As you know the LHCC is asking us to report on our Software organisation for the next LHCC of June 7. This is a good occasion to redefine our software priorities. Many of our young talented software physicists are doing physics simulations on Higgs, CP violations, SUSY etc... The time has come where the main effort should now go to the "technical software" i.e. full simulation of the raw data and realistic reconstruction algorithms. After discussions with M. Pimia, D. Denegri and F. Pauss the following four different types of software have been defined:

Global service software: Coordinator To Be Defined (TBD)
Detector specific software: Coordinator, M. Pimia
Physics tool software: Coordinator, F. Pauss
Physics performance and analysis: Coordinator D. Denegri

Each type of software is divided into different tasks. These tasks will be allocated to software teams consisting of physicists, engineers and software specialists from several laboratories lead by a convener. The conveners and the above coordinators form the Software Management Group (SMG) chaired by the overall CMS software coordinator (M. Pimia). The following tasks have been defined for the moment:

Global service software (15 tasks)
- Information system
- User interface
- Software methodologies
- Data modelling
- Data management
- Code management
- Geant
- CADD
- Visualisation
- Simulation system
- Reconstruction system
- Analysis system
- Magnetic field
- Alignment
- Machine and neutron background
Detector specific software (5 tasks)
- Tracker
- Calorimetry
- Muons
- first level trigger
- high level filter
Physis tool software (4 tasks)
- electron/photon
- muon
- Missing transverse energy, jets, tau
- bottom/charm
Physics performance and analysis software ( > 4 tasks)
- Higgs
- Susy
- Top
- Bottom
- etc...

We have identified some 28 tasks for which it is of prime importance to find a convener within the collaboration. I therefore urge all the group leaders to help in identifying the 28 conveners! I expect some feedback for the next CMS week of May 16. Thanks for your help.

Michel Della Negra