This page gives information about the editorial team responsable for bringing the TDR to completion as far as editing and content consistency is concerned.

The first task has been to assign one or more people to be responsible for each of the chapters so that they can coordinate the contributions for their chapter. These are called chapter editors or chapter responsibles.

However it is my feeling (Marc Dobson) and I believe quite clear that if the editorial board is made up of all the chapter responsables then it becomes very big and cumbersome. The following text was the original intention but has not heppened. I reproduce it below for history peurposes. "I therefore propose that only a representative subset of the chapter responsables (a core) be on the editorial board and that other chapter responsables are invited on issues which are global. Furthermore most if not all issues will be discussed previously by all editors through the editors mailling list referenced below." The last sentence is however still valid.

The chapter responsible(s) should be responsible for the timely delivery of the chapter content and the internal consistency of the chapter, which will then be handed to the editorial board. The editorial board will be responsible for the overall integration of the chapter in the document and for the technical consistency of the content. I believe the latter job is more time consuming and demanding. This seperation does not exclude anyone from looking at the overall document consistency and giving their comments to the editorial board, all the editors, or Marc Dobson.

It is suggested that any comments about individual chapters should be sent to the person(s) responsible for that chapter. More general comments on the TDR as a whole should be addressed either to Marc Dobson or preferably to all the editors using the mail address atlas-project-hltdaqdcs-tdr-editors@cern.ch.
 

This section gives information about the people responsible for the various chapters of the TDR.

Part 1: Global View
      Chapter 1: Overview ...................................... M.Dobson / TDMT
      Chapter 2: Parameters .................................... B.Di Girolamo/J.Vermeulen
      Chapter 3: Operational requirements for the TDAQ system .. G.Mornacchi
      Chapter 4: Event selection strategy ...................... S. Tapprogge
      Chapter 5: Architecture .................................. R.Hauser/G.Mornacchi
      Chapter 6: Fault tolerance and error handling ............ D.Burckhart
      Chapter 7: Monitoring .................................... F.Touchard

Part 2: System components
      Chapter 8: Data-Flow ..................................... D.Francis (ad interim)
      Chapter 9: High level trigger ............................ F.Wickens
      Chapter 10: Online software .............................. D.Burckhart
      Chapter 11: DCS .......................................... F.Varela
      Chapter 12: Experiment control ........................... F.Varela/D.Burckhart

Part 3: System Performance
      Chapter 13: Physiscs selection and HLT performance ....... V.Vercesi
      Chapter 14: Overall system performance and validation .... R.Dobinson/S.Gonzalez/G.Lehmann/J.Vermeulen

Part 4: Organisation and Plan
      Chapter 15: Quality assurance and software dev. proc. .... D.Burckhart
      Chapter 16: Costing ...................................... TDMT
      Chapter 17: Organization and resources ................... TDMT
      Chapter 18: Work-plan .................................... TDMT
      

TDMT stands for Trigger DAQ Managment Team, and is composed of C.Bee, N.Ellis and L.Mapelli.