Subject:summary on muon alignment DAQ issues (from 17-18 May muon alignment mtg.)
Date: Thu, 31 May 2001 16:01:23 -0500
From: kaori maeshima <maeshima@fnal.gov>

To: Gyorgy Bencze <gyorgy.bencze@cern.ch>, 
    Teresa Rodrigo <Teresa.Rodrigo@cern.ch>,
    David_Eartly <deartly@fnal.gov>, vila@fnal.gov, Jmolnor@atomki.hu
CC: Guenakh Mitselmakher <mitselmakher@phys.ufl.edu>, 
    Dick Loveless <loveless@hep.physics.wisc.edu>,
    Fabrizio GASPARINI <Fabrizio.Gasparini@cern.ch>, 
    Dan Green <dgreen@fnal.gov>,
    Alain Herve <Alain.Herve@cern.ch>, 
    maeshima@fnal.gov, Frank.Glege@cern.ch, wolfgang.funk@cern.ch


Dear all,

I summarize here the outcome of the last muon alignment meeting at
CERN (May 17-18th) from the discussion on CMS muon alignment DAQ.
At the end of this note, I express my concern about barrel system DAQ.

The basic concept we all agree on is that DAQ for each of three subsystems
must be modular and that each subsystem  is responsible for developing the 
modular DAQ to read out their own devices.  This allows us to develop and test
each subsystem efficiently and independently.

The second point is: though we plan to develop 3 modular DAQ programs,
it is extremely important to keep "integration" in mind from the design
stage in order to operate the alignment system reliably and efficiently
in the CMS experiment environment. 

Here a list of some common integration issues to keep in mind:
   1) synchronization of alignment data taking 
   2) data exchange method and interface with the alignment 
      reconstruction (COCOA)
   3) method on how the alignment data be used for the muon trigger
   4) method on how the alignment data be used for the muon reconstruction
   5) monitoring the DAQ and alignment data quality
   6) DCS interface.  (use of DCS may make doing (some or all of) above 
      actions easier)

In order to achieve this in timely manner (we must test design by the
end of 2001, EDR), it is essential to have 3 representatives, one from each 
subsystem who are responsible for designing/developing such DAQ systems
and start to coordinate as soon as possible.

Here is the current situation of each DAQ system:

Barrel: no one assigned yet for the CMS DAQ.
        (current contact is: J.Molnor, but as I was told he is assigned for
         low level electronics and read-out, not for barrel cms daq program)

Link:   Ivan Vila (starting this summer, 2001)

EMU:    Kaori Maeshima (basic 0th order design is done and presented at
        this alignment workshop.  This, of course, still need to be tested
        and developed.  If this scheme works, then the link system may be
        able to use the similar scheme).

In order to have barrel DAQ development, it is crucial to have 
someone identified from the barrel muon alignment group as soon as possible.

Here is a tentative near future plan I propose for each group (barrel, 
link, & emu) alignment DAQ development:

current - end of Sept. (by the next alignment meeting): 
                        *  finish design includng the 1st order testing 
                           and report at the meeting.
                        *  start developing cms DAQ 

Oct. 2001 - Dec. 2001.: *  continue to develop the real DAQ programs.
                        *  start implementing DCS interface.
                        *  document design for EDR.

Ivan and I are already started talking about some essential common issues.
Again, in order to have barrel DAQ development, it is crucial to have 
someone who is appropriate for this task to be identified from the barrel 
muon alignment group and start to communicate with us.

all the best,
                    Kaori