Muon Tracking : Tutorial

[email protected] 1

Muon Tracking : Tutorial

• Introduction

• Log on the muon_trk machine

1) Data Acquisition

2) Detector Control System

3) Mood

4) logbook

• Expert Tools (lc2gui, ltu)

• FAQ and frequent problems

Updated : September 12th 2008

[email protected] 2

Introduction (i)

A preliminary remarks; during december 2007 cosmic the number of people in the ACR was very high. Please do not consider the ACR as a working room. Seats are reserved for shifters (and experts when specific software developments are required).

This (basic) tutorial is divided in 3 main sections :– Take control of the DAQ

– Configure the chambers included in the readout (DCS)

– Check data quality with mood

[email protected] 3

Introduction (ii)

First you will have to log onto our dedicated machine in the ACR (Alice Control Room) :

aldaqacr25 : username is muon_trk (you will get the password during your training)

On this machine, one task = a desktop (please keep this organized this way):

1- DCA (Detector Control Agent) and DAQ

2- DCS (Detector Control System)

3- Monitoring and MOOD

4- Alice Web : logbook, alicesms, etc..

We’ll start with DAQ and DCA…

[email protected] 4

1) Data Acquisition

To start the DAQ interfaces the MTRK machine in ACR (aldaqacr25), go to desktop 1. If nothing is present on the screen , you can start the interfaces by clicking on

this icon

Then 3 windows will pop up…

[email protected] 5

1) Data Acquisition

The infoBrowser display all the info and error messages. Make sure it is online and the Stream selected is MUON_TRK.

You can also add some information like the run number

[email protected] 6

1) Data Acquisition

The Detector Control Agent from which you will issue the command for data taking :

Take control of the DCA with a click on the icon (if the lock is red, another DCA is open or central DAQ has control)

If DAQ_RC status is not ready (most probably it would be disconnected), see next slide

Take control of the DAQ_RC (Run Control ) with a click on the icon. If the lock is red, a RC window is open and own the interface… slide14

[email protected] 7

1) Data Acquisition

The Detector Control Agent from which you will issue the command for data taking :

If DAQ_RC status is disconnected, you can connect by requesting the DAQ resources.Click on GET_DAQ_RESOURCES

[email protected] 8

1) Data Acquisition

The Detector Control Agent should now look like this :

[email protected] 9

1) Data Acquisition

The run sequence need the execution of several commands; here a few explanations about the commands. The sequence is given in the next slide (assuming the detector configuration via DCS has been properly done )

• STANDALONE_RUN : start a run. Make sure LDC local recording is off (unless you really need it). GDC : No recording (recording in root format require mStream Recording).

• PEDESTAL_RUN : start a pedestal run (detector should be in BEAM_TUNING)

• ELECTRONICS_CALIBRATION_RUN : start a 10 calibration runs (detector should be in BEAM_TUNING). About 20 minutes.

• RESET_FERO• COMPUTE_THRESHOLDS• LOAD_CROCUS_SW : this command can not be

executed twice in a row without power cycling the readout (crocus)

• RELEASE_RESSOURCES

[email protected] 10

1) Data Acquisition

From the STANDY_CONFIGURED state (the detector is completely off).

Commands to be sent are : • GO_BEAM_TUNING • LOAD_CROCUS_SW (this command should be executed only if the detector was

previously in STANBY_CONFIGURED)• PEDESTAL_RUN • CHECK_FERO (if necessary, normally executed a the end of the pedestal run) • GO_READY

If the detector is in BEAM_TUNING state. The only necessary

operation to be done is • GO_READY

• During runs the detector will remain in the READY state. From time to time it is necessary to start a pedestal run; the shifter should go to the ECS operator and request a pedestal run. Commands are :

• GO_BEAM_TUNING • PEDESTAL_RUN • CHECK_FERO (if necessary, normally executed a the end of the pedestal run) • GO_READY


1) Data Acquisition

The third window is a “control panel”. The infoBrowser and the ECS button will start the infoBrowser window and the DCA window ; both are already open.

The runControl button will start the DAQ interface.

The select equipment button will allow you to select the part of the detector that are included into the readout.

CLICK on it


1) Data Acquisition

This is the list of the equipment id or DDL for the muon tracker. Here the DDL 2560, 2561 and 2563. Each time you change the selected DDL you must commit and then quit.

With the DAQ interface (after clicking on the runControl button), you will need to select the ldc corresponding to the equipId you’ve selected.This will be explained in a few slides…


1) Data Acquisition

A few words about the numbering scheme of the readout :

1 LDC receive the data corresponding to 1 full station :– id: 53 ldc-MTRK-S1-0 hostname:aldaqpc088 station1

– id: 54 ldc-MTRK-S2-0 hostname:aldaqpc089 station2




1 full station has 4 DDL (or CROCUS) : 1 LDC read 4 CROCUS – ldc-MTRK-S1-0 read DDL or equipment 2560,2561,2562,2563

– ldc-MTRK-S2-0 read DDL or equipment 2564,2565,2566,2567





1) Data Acquisition

Up to date values are now located here : https://twiki.cern.ch/twiki/bin/view/ALICE/CablingAndNumberingScheme

2560 (EquipId): Chamber 1 Right (DCS) [rorc minor = 3; rorc channel = 0]2561 : Chamber 1 Left [rorc minor = 0; rorc channel = 0]2562 : Chamber 2 Right [rorc minor = 1; rorc channel = 0]2563 : Chamber 2 Left [rorc minor = 2; rorc channel = 0]2564 : Chamber 3 Right [rorc minor = 3; rorc channel = 0]2565 : Chamber 3 Left [rorc minor = 0; rorc channel = 0]2566 : Chamber 4 Right [rorc minor = 1; rorc channel = 0]2567 : Chamber 4 Left [rorc minor = 2; rorc channel = 0]2568 : Chamber 5 & Chamber 6 Top Left [rorc minor = 3; rorc channel = 0]2569 : Chamber 5 & Chamber 6 Top Right [rorc minor = 0; rorc channel = 0]2570 : Chamber 5 & Chamber 6 Bottom Left [rorc minor = 1; rorc channel = 0]2571 : Chamber 5 & Chamber 6 Bottom Right [rorc minor = 2; rorc channel = 0]2572 : Chamber 7 Right [rorc minor = ; rorc channel = 0]2573 : Chamber 7 Left [rorc minor = ; rorc channel = 0]2574 : Chamber 8 Right [rorc minor = ; rorc channel = 0]2575 : Chamber 8 Left [rorc minor = ; rorc channel = 0]2576 : Chamber 9 Right [rorc minor = ; rorc channel = 0]2577 : Chamber 9 Left [rorc minor = ; rorc channel = 0]2578 : Chamber 10 Right [rorc minor = ; rorc channel = 0]2579 : Chamber 10 Left [rorc minor = ; rorc channel = 0]


1) Data Acquisition

The third window is a “control panel”. The infoBrowser and the ECS button will start the infoBrowser window and the DCA window ; both are already open.

The runControl button will start the DAQ interface.

CLICK on it


1) Data Acquisition

The lock is red because the control of the DAQ interface is taken by the DCA interface. To control this panel, release the control from the DCA window.


1) Data Acquisition

Since Friday 15th (Feb. 2008), the bridge between the ECS and DCS has been successfully tested. It simply means that the DCS (HV,LV) is controlled by ECS.

This box represents the real detector state. The lock allows to release/take the control. From the pull down menu, it is possible to change the state of the detector FSM.

More on the FSM next slide…


FSM : Final State Machine

Our detector has 3 main states :– STANDY_CONFIGURED (off)– BEAM_TUNING (LV on, HV @intermediate value == no gain)

• used for pedestal and electronic calibration runs

– READY (HV@ at full value and LV on)• get ready for physic

+ 1 additional state which doesn’t change the HV or LV configuration :– READY_LOCKED

• state is lock ; data taking can start (the state ready may not be sufficient).

Rising the low and high voltages (like going from standby to ready) can be harmful to the detector and need to be careful prepared and checked :– select the active parts of the detector corresponding to ones included

in the data taking– check the high voltages values

This is done via the DCS interface…



First go on desktop #2 and start the DCS. Most probably the DCS UI interface will be already open, then go directly to slide 22.

If not :

Start a xterm and launch tsclient (connection to windows machines to start the DCS interface)

>tsclient

Open

Choose dcs and ok

Connect

Use your personal NICE “username” and “password” to log in on the DCS application gateway



Open the Remote Desktop Connection from here and connect to “Operator Node” (computer ALIDCSCOM048).

Type “alidcscom048” and press Connect

Use your NICE “username” and “password” to log in on the DCS “Operator Node” server.

Once on the machine start the programmchdcsui



DETECTOR LOGO

USER LOGIN

FSM NODE STATE

FSM HIERARCHY TREE BROWSER

DETECTOR GRAPHIC LOCATOR

TITLE BAR

USER TOOL BAR

DATE-TIME

ENVIRONMENT PARAMETERS

USER PANEL FOR MONITORING

MESSANGER READER

CLOSE WINDOWS

AUXILIARY MONITORING ZONE OF THE FSM MAJOR NODES HOSTS STATE & FSM MAIN

CONTROL

LHC STATUS

FSM NODE CONTROL

The Standard DCS UI provided by the ACC



After several seconds, when finished to download the FSM Tree, you must type your user name and password to log in to the DCS system. This user name and password are only for DCS and are different from the NICE ones. You must click on the “Enter” after user name and password.

If you are member of some group (Operators, Experts ..) will be opened the “User Panel” for Muon DCS. More information about every part of User Panel one can found in: http://alicedcs.web.cern.ch/AliceDCS/Software/Downloads/AliceDcsUi_v3.0.doc



FSM

TemperatureGas

Low VoltagesRight side

Low VoltagesLeft side HV

See chambers LV and HV : right click and [view panel]

Do notTouch



The top panel (previous slide) of the DCS interface gives a summary of most of the variables that we can control and/or monitor :– FSM

– gas flow

– temperature monitoring

– low voltages (Left and right side)

– high voltages view

– half chamber view (left side) to access the a particular part of the detector (from which low and high voltages values can be set)



FSM :

1. which parts of the detector will be included in the run ? It is required to power up on only the DDL that participate in the DATA taking (this has been defined previously with the select of the equipment Id). If not done properly, done the detector will appear in BUSY state to the DAQ.

2. the mechanism to include/exclude chambers of the muon spectrometer uses the lock icons associated to each ½ chambers.

3. the hierarchy of the FSM is the following :MCH_DCS

MCH_DCS_RUN

MchHvLvLeft MchHvLvRigth

• mchChamber01Left• mchChamber02Left• mchChamber03Left• …..

• mchChamber01Rigth• mchChamber02Rigth• mchChamber03Rigth• ….



The correspondence between the naming scheme of the DCS and the

naming scheme of the DAQ is listed on slides 13 and 14 ( e.g. Chamber 4 Right = 2566, etc…).

So how to include/exclude in the DCS the part of the detector declared in the equipment ID list of the DAQ (slide 12)?

First, you need to pop up the FSM window corresponding to the Top Node MCH_DCS of the Dimuon Spectrometer :

Click precisely on the border line surrounding the element(the pointer of the mouse will change from an arrow to a hand).



Click on the lock to see the menu of the possible actions

A pop-up window appears : you can take the control of the detector ( then the lock close and become green, as displayed on the left).

If you click again on the lock, another window appears : you can release the control of the detector (to release the ownership prefer ReleaseAll to Release.)

Now you can close the Top Node (MCH_DCS) FSM window ; the main panel should now look like this…



All the chambers are now selected, which certainly doesn’t correspond to reality : only parts of the detector (specific DDL or EquipId) are readout. Thus the others have to be excluded, according to the selection done in the DCA (slides 12,13 and 14). This will done from the level below the Top Node (see slide 26), MchHvLvLeft and MchHvLvRigth



All the left side of the spectrometer is selected. Let’s remove Chamber03 for an example ; simply click on the lock…

In the pop-up window, click on Exclude to remove this chamber from the DCS control.


Chamber03 is deselected; one more click on the lock will allow to lock it out.

In the pop-up window, click on LockOut to lock out this chamber when DCS control will be given to the DCA. This operation is crucial to have the correct part of the detector powered up.You exclude and lock out the other chambers on the left side. Then you will go to the rigth side.


This was the default configuration during the February/March cosmic run. Full station 1, full station 2 but 1 DDL (2565). Nothing from Station 3, 4 or 5.



FSM

TemperatureGas

Low VoltagesRight side

Low VoltagesLeft side HV

See chambers LV and HV : right click and [view panel]

Do notTouch


2) Detector Control System : High voltages settings

It is crucial to check the high voltage setting of the chamber. A right click on a the chamber name (on the left side of the DCS panel) will allow to view its “voltage panel”.

Click on the “Channel Set” button to pop up the HV settings panel.


2) Detector Control System : High voltages settings

This is the table describing the high voltages settings.

Click here to set the all values of a column at once

Do not modify these values !! Ask an expert if something doesn’t looks

normal to you.

Up to date guide/values is now located here : https://twiki.cern.ch/twiki/bin/view/ALICE/HighVoltages


2) Detector Control System : temperatures probes

Click here to seethe list of sensors and the temperature measured.

Shifter should check : 1. temperatures values2. in a normal operating

mode Tmax ~ 30


2) Detector Control System : temp. probes

Up to date information is available at :

https://twiki.cern.ch/twiki/bin/view/ALICE/TemperatureSensors


2) Detector Control System : GAS system

Rack 61 provide gas to station 1 and 2.

Rack 62 provide gas to station 3, 4 and 5.

Shifter should check : 1. Status of the rack2. flow in and out3. pressure

If the gas flow (mix of Ar + C02) stops, a hardwired interlock (not wired yet) will shutdown the HV after a short delay (~10 minutes).Without the proper gas , the gain of the chamber is not adapted to particle detection.


3) Monitoring and MOOD

Data monitoring is done with MOOD. The machine to muon tracking is aldaqdqm07 (accessible from acr machines, user muon_trk same password).

Once logged on, simply type > mood&

(a development version can be selected with :

> source ~/Guillaume/mood_env.sh )

On the mood window, “Detector” “MCH (MUON Tracker)” “Cosmic Test 2007” ( this name may change, in any case do not use “Test Beam” )

After a few seconds….



Configuration is accessible from the tabs : “Setup Monitor” and “MUON Tracker Configuration”.

Do not change this configuration unless you know what you are doing ! (for non-gdc monitoring, you need to have the correspondance between the monitoring source and the LDC.)



Monitoring histograms are grouped in the display tabSummary histos have give occupancy and errors distributionManu Dump will allow you to see the raw data at the MANU level



Look at pedestal/noise and gains files

Pedestal subtraction can then easily be applied to the data

Pedestals and calibration runs are local to a LDC, i.e.to a station. After a pedestal or a calibration run, resuls files will be located in the /tmp of the ldc: pedestal file = /tmp/MUONTRKda_ped_ {rn}.pedcalib file = /tmp/MUONTRKda_gain_ {rn}.ped(where {rn} stands for the appropriate run number).NB : all files from different LDC have the same name. So these files need to be transferred from the LDCs aldaqpc088,089,090,091,092 to the mood machine with a different name, to do so :

On the monitoring machine (aldaqdqm07), > cd ~/CurrentRun/> rm *.ped On the aldaqacr machine : > cd ~/> source copyPedRun 12345 (where 12345 is the proper ped. run number )



Look at pedestal/noise and gains files

It is not yet possible to reset the pedestal/noise and gain files from mood “memory”. Thus before visualizing a new run, one should clean the directory CurrentRun and restart mood.

Pedestals and calibration runs are local to a LDC, i.e.to a station. After a pedestal or a calibration run, resuls files will be located in the /tmp of the ldc: pedestal file = /tmp/MUONTRKda_ped_ {rn}.pedcalib file = /tmp/MUONTRKda_gain_ {rn}.ped(where {rn} stands for the appropriate run number).NB : all files from different LDC have the same name. So these files need to be transferred from the LDCs aldaqpc088,089,090,091,092 to the mood machine with a different name, like :


4) Expert tool : [LC]2

This is the tool that will allow you to modify the configuration files (init{DDL.number}.dat) of the detector sent to each crocus.

1- go to the working directory (> cd ~/LC2work)

2- start [LC]2 with the command lc2gui

You want to use the “Edit” mode.



Modify and save a configuration file : Edit mode

The default configuration of the CROCUS, generated from the AliRoot mapping is in ~/LC2ConfigFromAliRoot (numbered from 0 to 19, you need to add 2560 to get the real crocus id) :

1. Copy the original crocus in the working directory 2. open it with LC2, modify it to reflect the real state of the corresponding part of the detector

A very good idea is to check FIRST with adiff command the configuration stored inthe ~/LC2work/init{CrocusId}.dat with the one use by the ECS :> diff ~/LC2work/init{CrocusId}.dat

$LC2_CONFIG/init{CrocusId}.dat

X X



Modify and save a configuration file : Edit mode

The default configuration of the CROCUS, generated from the AliRoot mapping is in LC2ConfigFromAliRoot (numbered from 0 to 19, you need to add 2560 to get the real crocus id) :

1. Copy the original crocus in the working directory

2. open it with LC2, modify it to reflect the real state of the corresponding part of the detector

3. save it with the appropriate name init{CrocusId}_modified.dat

4. move it to the directory from which crocus configuration files are loaded by the ECS scripts

> mv ~/LC2work/init{CrocusId}_modified.dat $LC2_CONFIG/init{CrocusId}.dat

5. After any operation with LC2, it is safer to do > rm /tmp/*.scr



Creation of the original configuration file :

The original configuration file is first taken from aliroot and modified to reflect the active patch buses of the detecteur :

1. Set the proper rorc minor id

2. rorc channel number id is always 0

3. Set the proper equipment id

4. Set the last bullet (CRT1 resets FRT board at init). This is NEW and has to be done for every file !


5) Expert tool : Trigger Emulator

Trigger emulator window is accessible from the DCA window ;

View

Show trigger Control Configuration


5) Expert tool : Trigger Emulator

Default configuration of the MCH Local Trigger Unit

Do not modify anything in the trigger setup for the muon tracking… This can take days to be fixed ! If you “think” you have modified something, please

contact me asap !!

You may need to change

the trigger rate :

1. This is the “bcrate”

2. put a new value in hertz

3. Save

4. Quit the interface


6) Expert tool : Crocus Control via trigger dispatching.

From an xterm, ssh to alidcsvme009 and connect as muon_trk (usual password) :

> ./dispatching

This is the interface to the trigger dispatching crate that received trigger signals from CTP/LTU, dispatch them to the CROCUS and collect the busy signals from the CROCUS before sending it back to the Alice trigger. This allows you to monitor the busy of the CROCUSClick on CMD tab..



If a crocus has raised its busy, it will appear in red. Theoretically crocus should become busy but it happens from time to time at the beginning of the run (this is still an open issue). During the data taking, it’s perfectly normal to see different crocus going from busy to not busy; this is just reflecting the data taking.

In case of busy problems, can not start standalone run after SEVERAL TRIES !You may click : Select AllReset Crocus Then go back to the DCA window where you’ll

have to execute LOAD_CROCUS_SW, PEDESTAL or STANDALONE_RUN, etc….



# board addr (4bits hexa).FFT 6

# FTD boards# No space beetween its name and its number, board addr (4bits hexa).FTD1 1# Number of CROCUS in decimal (not in hexa).

crocus0 2560crocus1 2565crocus2 2570

# crocus3 2575

FTD2 2crocus0 2561crocus1 2566crocus2 2571crocus3 2576

FTD3 3crocus0 2562crocus1 2567crocus2 2572crocus3 2577

FTD4 4crocus0 2563 crocus1 2568

# crocus2 2573# crocus3 2578

FTD5 5crocus0 2564crocus1 2569

# crocus2 2574# crocus3 2579

Once logged on the machine alidcsvme009, you can edit the configuration (dispatchingConfig.txt) that describes where trigger cable are connected in the FTD of the Trigger dispatching crate.

What you see on the left is the current configuration. The trigger cables must be connected according to this file do not modify this file !

The only change you’re suppose to make are removing the # sign (comment out the line) at the beginning of the line when a new crocus is put in the global mode and its associated trigger cable is connected.


FAQ and frequent problems

• when sending directly boot command via LC2 one should not forgot to clean up the /tmp : rm /tmp/bootFrtCrtDSP.scr (this is still necessary for the moment)

• pedestals and calibrations are automatically written on disk (as it supposed to) but users should always keep an eye on the disk occupancy of their LDC– df –h

– and remove old files in /local/data/

Muon Tracking : Tutorial

Documents

Transcript of Muon Tracking : Tutorial