# Presentation: 329882

## MUON Alignment DAQ (overview)

- Often a question is asked: Do we have a single DAQ program or 3 separate DAQ programs for each subsystem?
- Our approach to answer above question is:
- Keep the DAQ modular for maximum efficiency (Hardware and FE of each subsystems are different.  Avoid unnecessarily  large overhead.).
- Be sure the common issues are addressed and coordinated in order to achieve coherent operation in the CMS experiment.

## Outline

- Contact people for DAQ in each subsystem
-  Brief review of each subsystem readout scheme
- Common Issues
- Schedule and plan

## Contact people and brief review of each subsystem readout plan

- Barrel: J.Molnar, D.Novak                          (see G.Bencze’s talk in the barrel session for more details).
- Link: I.Vila                                                  (See A.L.Virto’s talk in the link session for more details)
- EMU: K. Maeshima                                    (see K.Maeshima’s talk in the EMU session for more details)

## Barrel Readout Scheme

- _Barrel Readout Scheme_

- HUB (MAB) #1

- BC #6

- BC #1

- SCADA
- MAB Workstation

- ...

- Cam #1

- Cam #24

- Video

- HUB (MAB) #6

- HUB (Wheel)

- 10/100 Ethernet (Optic
- al)

- 10/100 Ethernet (Optical)

- 10/100 Ethernet
- (Twisted pair)

- BC #36

- BC #31

- ...

- Control room

- Exp. Hall

- BC = Board computer

- Wheel -2

- Wheel +2

- LED-s

- Tilt

- sensor

- Flat

- Cam #1

- Cam #24

- Video

- LED-s

- Tilt

- Flat

- sensor

- Tw.

- pair

- Tw.

- pair

## Link Readout Scheme 

**Hardware components location**

**Link Readout Scheme **

## Link Readout Scheme (cont.) 

**Canbus lines and daq architecture**

**Link Readout Scheme (cont.) **

- L: LEB
- E: ELMB

## EMU Readout Scheme 

## Common Issues

- Synchronization of the data taking
- Data exchange among the 3 alignment subsystems.
- Common framework for an alignment reconstruction program (COCOA) and Interface - how the muon chamber alignment results being used (data storage, data accessing, issues):
- CMS muon chamber geometry and offline muon track reconstruction. (see P.Arce’s talk for more details)
- Operation and Monitoring
- Comment: Use of the CMS DCS system solves much of above issues.

## DATA Flow  (Conceptual)

- Readout for the
- Barrel Alignment
- devices with
- DCS interface

- COCOA for the
- Barrel chambers

- Barrel chambers
- positions

- Geometry of
- ORCA for the
- muon reconstruction

- Readout for the
- Link Alignment
- devices with
- DCS interface

- Readout for the
- EMU Alignment
- devices with
- DCS interface

- COCOA for the
- Link information

- COCOA for the
- EMU chambers

- EMU chambers
- positions

## DAQ Plan for the Magnet Test 2004 

- Should be able to read out the full Link and EMU alignment subsystems and  the barrel magnet test setup.
- The software must be developed enough that during the magnet test we can have fast feed-back from the data taken.  This means:
- Interface must be ready such that raw data from DAQ and other necessary data (calibration, etc.) can be readily converted into input format of COCOA.
-  COCOA should run in a timely manner to give us the fast feed-back on the position/movement of chambers.

## Barrel Setup for the Magnet Test 2004

- 10 MAB Board Computers to control the MAB-s
-   1 MAB workstation
-  to communicate with the MAB board computers
-  to communicate with the chamber part (DCS function)
-   5  Board computer hardware configurations with special software
-  to control the LED-s on the muon chambers (minicrate function)

## Summary and Plan

- Design of each subsystem DAQ has been worked on and being tested, keeping in mind that there are some common issues (DCS interface, etc.) must be addressed.
- Implementation should follow.
- milestone: Magnet test 2004 – deliver the operational system in the 1st order.
- Continue to implement and deliver the final muon alignment DAQ system for the installation/commissioning of the alignment system and the CMS experiment with good monitoring system and documentation for the long term operation to follow.
- (see each subsystem report for more detailed schedule)