MUON TRIGGER DCS introduction & tutorial - ALICE Muon Trigger ...

MUON TRIGGER 

DCS introduction & tutorial 

F. Jouve – LPC Clermont-Ferrand 

M. Gagliardi – Università & INFN Torino - CERN 

Frédéric Jouve & Martino Gagliardi Dimuon Meeting, Aussois – 09/06/2009 slide 1

Outline 

Concepts 

• A few words about PVSS 

• FSM: what is it and what do we use it for? 

Tutorial 

• How to get started 

• The MTR User Interface 

• Using the FSM 

• Emergency button and Alarm screen 

• CContacts 


Concepts 


A few words about PVSS 

• The PVSS software provides remote control of all hardware devices in the 

system 

• CControl t l i is conveniently i tl split lit over more tterminals. i l MTR MTR: two t worker k nodes d 

(for DCS experts) + one operator node (alidcscom056, for shifters) 

• Devices are modeled with datapoints. Their parameters are stored in 

datapoint elements elements, eg e.g. 

Datapoint (HV channel) Datapoint elements 

alimtrcae001.board00.channel005.vMon 

alimtrcae001.board00.channel005.iMon 

• Datapoints are displayed via dedicated panels. When applicable, panels 

also allow datapoint configuration (e.g. HV settings, thresholds..) 

• PVSS provides alarms whenever parameters are out of pre-defined ranges. 

• Connection with other systems (LHC, gas, environment) 

• Finite State Machine (more details in next slides) 


Fsm: what it is and what we use it for 

• FSM = Finite State Machine 

•A software tool which links all different parts p of 

the system together. Used to evaluate the state of the 

system and to control it in a standardised way. 

• DDevices i are given i llogical i l names 

(alimtrcae001.board02.channel005 -> MTR_INSIDE_MT11RPC6_HV ) 

• Devices are grouped into logical objects (e (e.g. g MtrHalPlane) 

• Both devices and objects can take a finite number of 

states. 

• States of objects are logical functions of the 

states of the devices in the object. 

• Actions send a device or object from one state to 

another. 

• During data-taking, detector fully controlled by FSM! 


Fsm states and actions 

Colo Colour code: ode ready ead fo for physics, ph si s not ready ead fo for ph physics si s (but (b t no eerrors), o s) 

warning or error, mixed or moving. 

A few typical yp object j states: 

A few typical yp device states: 

READY (LV ON, HV nominal) 

ON 

STBY_CONFIGURED (LV OFF, HV OFF) OK 

BEAM TUNING U G (LV ( O ON, , HV = 6000 V) ) OFF O 

ERROR 

TRIPPED 

MIXED 

NO_CONTROL 

MOVING_READY 

ERROR 

MOVING MOVING_STBY_CONF 

STBY CONF RAMP RAMP_UP_READY 

UP READY 

MOVING_BEAM_TUNING 

RAMP_DOWN_OFF 

DEAD (FSM not running) DEAD 

A few typical actions: 

GO_READY 

CONFIGURE (l (load d settings tti f from PVSS t to hardware) 

h d ) 

RELOAD 

GO_STBY_CONF 

GO_BEAM TUNING 

RESET (error recovery) 


MTR FSM logical structure 

MTR_DCS Top node 

Side 

Half plane 

RPC 

RPC HV ch. 

MP RPC temperature probe 

RPC ext. threshold 

Threshold values 

In progress, see 

F. Jouve’s presentation 

LV channels 

LV for FEE 

LV for ext. thresholds 

Infrastructures 

G Gas system t 

LV modules for ext. thr. 

HV PS 

Run unit 

LV PS 

Frédéric Jouve & Martino Gagliardi Dimuon Meeting, Aussois – 09/06/2009 slide 7 

VME crates

Use of majority 

Con Concept: ept we e do not want ant the top node to take an error e o state if only onl a 

few elements are in error, since a top node state change will stop the 

whole ALICE run. We will only stop the run when physics is no longer 

possible. 

To this purpose, errors are only propagated to the parent element if a 

majority of children is in error 

E E.g.: 

- we assume we can still do physics with 6 RPCs 

in a half-plane, error is not propagated if 

3 RPCs are in error 

- we can not do physics with less than 6 RPCs 

in an half plane, if 4 RPCs are in error the half 

plane takes an error state 

CCurrent t majority j it conditions diti 

Error is not propagated to the parent if: 

- Top node: at least one side available 

- Side: at least 3 half planes available 

-Half plane: p at least 6 RPCs available 

Warning: majority is only active for error states!! 


Tutorial 

Please note that what follows are just the main guidelines to the use 

of MTR DCS. 

Please make sure you read the Shifter’s guide, where you can find: 

- a more detailed explanation of all panels 

-a set of Howto’s 

- updates p whenever the system y is modified 

http://prosnet.web.cern.ch/prosnet/running/DCS_Shifter_Guide.pdf 


Getting started 

• Log onto the operator node. From a linux terminal in the ACR: 

rdesktop –g1280x1000 –a16 alidcscom056 

• L Log in i with ith your NICE username and d password. d If it does d not t work, k 

contact us 

• Start -> mtrUserInterface. Log in. Temporary account mtrExpert is 

available il bl ( (ask k f for the h password!!) d!!) 


The MTR User Interface 

FSM Tree 

Auxiliary monitoring zone: a 

quick overview of the status 

of main FSM elements. All 

boxes should be green during 

data-taking! 

Start alarm screen 

Open FSM control 

Frédéric Jouve & Martino Gagliardi Dimuon Meeting, Aussois – 09/06/2009 slide 11 

MMain i 

panel

The MTR main panel 

Di Displays l FSM status t t of f the th system t in i 

details, using colour code. 

Status of RPC 

HV, 

TTemperature, t 

Thresholds 

Status of half-plane 

majority 

(Orange = 1 to 3 

RPCs out of order) 

(Red = 4 or more 

Safety for 

injection and 

emergency 

button 

Gas flow 

and 

humidity 

(colour 

code!!) 

RPCs out of order) Push buttons open panels with more detailed detailed, non-FSM non FSM 

info about LV, HV, VME, thresholds, ventilation… 


Start/Restart/Stop FSM 

•Click on the FSM box at the bottom of the User Interface 

• Push the Start/Restart or Stop button 

• You may be asked to kill some SMI processes: you can skip it! 

• When FSM elements are no longer DEAD, close window 


Take control of the FSM 

•Click on the FSM button in the FSM Tree 

• If the lock is grey and open, click on the lock; then click on “Take”. If 

the lock is red and closed, , someone else has the control, ,y you can’t take 

it. If the lock is green and closed, you have the control. 


Display device and object panels 

• Click right on an FSM element in the FSM Tree and 

select “VIEW VIEW PANEL” PANEL to display the panel of that 

element (if available) 


Control devices and objects via FSM 

• After displaying the panel of a device or object object, click on ”FSM” FSM in the FSM Tree 

to open its FSM control panel 

• The panel displays the state of the element and of its children. 

• Double click on a child’s name to view and control its own children 

•The h available il bl actions i ffor one element l are shown h in a menu which h h can be b 

displayed by clicking on the status box of that element 


Disable a device or object 

• To exclude a device 

or object from the 

FSM, , click on the 

small square right of 

the status box, then 

click on Disable (for 

devices) or Exclude 

(for objects) 

• Wh When an element l t is i 

disabled: 

-it is not taken into 

account in the h 

evaluation of its 

parent’s p state. 

- it will not respond 

to FSM commands 


Non-FSM tools: Emergency button 

Several PVSS buttons and panels can be used to monitor and control 

the system when the FSM is not running. Please read the Shifter’s guide 

for their description. Here, we will focus on the Emergency button and 

Alarm screen 

The emergency button: 

• Tells the shifter whether the system is safe for 

injection or not not. The safe condition is: all HVs < 6100 V 

• Allows the shifter (or even the central DCS operator) to 

force the system to a safe state when, for any reason, the 

GO_BEAM_TUNING FSM command does not work: 

- Right-click on the HVoff button 

to unlock it 

- Left-click on the HVoff button to 

ramp down all HV channels 

- Make sure the box turns “SAFE” 

after a while 


Non-FSM tools: Alarm screen 

•Gathers all alerts of MTR and connected systems 

• Three degrees of alarm: warning, error, fatal 

• Right click on the error line, then “Alarm Help” to display instructions 


The end - Contacts 

Hope things are a little clearer now. now For any issues: 

- Read the shifter’s guide! 

- Contact us: 

Frédéric Jouve 

frederic.jouve@clermont.in2p3.fr 

+33 473 40 73 12 (Clermont-Ferrand) 

Martino Gagliardi 

gagliard@to.infn.it 

16 37 63 (CERN) 

+39 39 011 670 73 77 (T (Torino) 

i )

MUON TRIGGER DCS introduction & tutorial - ALICE Muon Trigger ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?