1 / 9

Muon Tracker

Muon Tracker. DCS Status on behalf of Ronald Kunne. Status, overview. HV: a prototype of the system exists, including PVSS LV: some experience with the PVSS, but no prototype.

winter
Download Presentation

Muon Tracker

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Muon Tracker DCS Statuson behalf of Ronald Kunne

  2. Status, overview • HV: a prototype of the system exists, including PVSS • LV: some experience with the PVSS, but no prototype. • FEE: nothing exists. Planned is only a small DIM server that transmits the status of the FEE (on, off, calibration,….) • GMS (Geometry monitor): exists partially • Environnement: agreement reached on number of sensors necessary, nothing else. Will use ELMB • MU-TRK control unit (FSM): a first version exist, able to communicate with the HV, and some preliminary coding for the other sub-systems ALICE DCS Workshop

  3. 2 (was 4) 20 (was 40) updated ALICE DCS Workshop

  4. Equipment inventory ALICE DCS Workshop

  5. Use of ELMBs • Used for environment monitoring on and around the detector • For each of the 5 stations are foreseen: • 10 temperature sensors to monitor on-detector electronics • 4 temperature sensors to monitor CROCUS • 1 hygrometer • 1 overpressure on chamber gas outlet • 1 ELMB needed for prototyping • Total of ~4 needed at installation time ALICE DCS Workshop

  6. Databases (FEE) • Need to read/write from the configuration databases: • the acquisition programs (which might change over time) • the configuration data. Comprised of a few words per read-out channel: (address, status, current pedestal, small number of calibration constants) • These data will be hierarchised according to the detector structure, as follows:Subdetector -> Chamber (10) -> Quadrant or halfchamber (2 or 4) -> Read-out bus (up to 12) -> MARC (up to 26) -> channel (64). • In total there are 1.1 million channels and 22MB of data per configuration. • We would appreciate help with the design of the databases. • The contact person for the DAQ is Sylvain Rousseau (rousseau@ipno.in2p3.fr). ALICE DCS Workshop

  7. Databases (FEE) • The read-out will not be directly monitored via the DCS, but checked by sampling via the DAQ. • A DIM server might be developed to broadcast the general status of the FEE to the DCS. ALICE DCS Workshop

  8. Computer needs • Agree with the table as proposed, but would like to have GSM on separate (additional) machine: ALICE DCS Workshop

  9. Questions from MTRK • Is there a standard sensor for temperature/ hygrometry? • No • What is the minimum information that the DCS expects from the FEE? No real monitoring of the FEE by the DCS is foreseen in our case: is that acceptable? • If there is also no action expected, I guess it’s OK… • We have no expertise in database construction and requirements. Help is appreciated (starting from the most basic….) • But that will be on the DAQ side then… ALICE DCS Workshop

More Related