1. Muon Shifter Start Manual – July 08 1 The (im)Perfect Muon Shifter

2. Muon Shifter Start Manual – July 08 2 Forewords This pages are meant to initiate people who are not familiar with ECS, and Muon ECS in particular, to perform shifts in global data taking run. In this sense, information given here are very basic and in general refer to a non- expert use of the system: setting-up of the system for DAQ runs, first check of proper running conditions, first simple interventions in case of simple frequently encountered problems. This basic manual can also be a starting point for a richer documentation while the operator skill increases and the control system becomes more stable and complete. Please note also that the ECS system is still under development. Changes on the panels and even on the structure is still possible. This pages should not be meant as a user manual of a delivered project/system, but just to gain a first idea on system operation. Muon ECS (basics of the) basics The LHCb Experiment Control System (ECS) is based on the PVSS framework. You can find some documentation on PVSS and LHCb ECS at page http://lhcb-online.web.cern.ch/lhcb-online/ecs/default.htm, and in particular the tutorial http://lhcb-online.web.cern.ch/lhcb-online/ecs/powerpoint/LHCb_ECS_Tutorial.ppt, which we warmly suggest you to read.http://lhcb-online.web.cern.ch/lhcb-online/ecs/default.htmhttp://lhcb-online.web.cern.ch/lhcb-online/ecs/powerpoint/LHCb_ECS_Tutorial.ppt The ECS is based on so-called PVSS projects, running on dedicated online PCs. You can find the list of the Muon online PCs on page 6. Each project runs on independent partitions and must be started on its specific machine. No ECS is active if the related project is not up and running. The MUON ECS has several project types, controlling: FEB (front end boards, i. e. CARDIAC via the Service Boards); ODE (Off Detector Electronics); LV and HV; Tell1; FSM (Finite State Machine & Hierarchy) projects. The last projects do not directly control any hardware but the hierarchical structure of the ECS itself. The FSM allows the ECS circulating commands (from top to bottom of the structure) and states (bottom-up), thus making possible the communications among the complete system.  Introduction

3. Muon Shifter Start Manual – July 08 3 The hierarchical structure of the Muon system DAQ is given on page 4 as an example of ECS hierarchy (the LV/HV/Tell1 branches are not included here). The structure consists of 3 types of objects: Device Units (DU), Control Units (CU), Logical Units (LU). Very briefly, a DU is an object controlling a hardware component (e.g. a CARDIAC board), a CU is just a hierarchical object, passing commands and states on a hierarchical node, an LU is useful to group different DU together and is rarely use in our case. The hierarchical structure allows also including and excluding portions of the system (for example, a complete branch starting from a given node). Following the general LHCb structure, also the Muon hierarchy is organized in two independent and totally symmetrical parts, MUONA and MUONC, controlled by a higher node, MUON. The deeper the hierarchical level, the wider the understanding needed of system and hardware details. However, in “normal” conditions it should not be necessary to go further than the MUONA/C level.

4. Muon Shifter Start Manual – July 08 4 MUON DAQ domain hierarchy MUONA_DAQ_Q1_M45A_R1_SBn Logical Unit Device Unit Control Unit MUONC_DAQ_Q4MUONC_DAQ_Q3MUONA_DAQ_Q2MUONA_DAQ_Q1 MUONA_DAQ_Q1_M1AMUONA_DAQ_Q1_M23AMUONA_DAQ_Q1_M45A MUONA_DAQ_Q1_M45PDM MUONA_DAQ_Q1_M45A_M4MUONA_DAQ_Q1_M45A_M5 MUONA_DAQ_Q1_M45A _M4_R4 MUONA_DAQ_Q1_M45A _M4_R3 MUONA_DAQ_Q1_M45A _M4_R2 MUONA_DAQ_Q1_M45A _M4_R1 MUONA_DAQ_MXA_RY_CMBlab MUONA_DAQ_Q1_M45A_M4_R1_ODE MUONA_DAQ_Q1_M45A_M4_R1_ HU_CMB MUONA_DAQ_Q1_M45A _M4_R1_HUn MUONA_DAQMUONC_DAQ MUONMUONAMUONC

5. Muon Shifter Start Manual – July 08 5 Panels and States ECS operation is based on control panels, giving information on system status and allowing intervention of the operator to trigger a status change. Although intuitive, it is important to give some explanations on the use of the panel buttons. { Sub-System buttons: clicking with the left mouse button opens the corresponding CU Sub-System state, visualizing the current state. Clicking with the left mouse button gives the list of possible actions which can be done from it. MUONA CU Panel Lock button: the system can be accessed/controlled by different parts of ECS. This button says who is presently TAKING the system and its inclusion/exclusion in the hierarchy. This info can be gained by placing the mouse tip on the lock. Before operating on a given system/subsystem you need to TAKE it (if possible). During Global data taking “your” system must be controlled by the global manager and the muon operator must release it properly (see next pages). Using the left mouse button it is possible to change the lock status. Presently loaded recipe. A recipe is the collection of all the configuration parameters/variables needed for a specific data-taking run. Usually the shifter should not choose one recipe rather than another (it is already loaded). If further information is needed on recipe handling, for the moment you have to refer to an expert. NEVER use this button to dismiss the panel ALWAYS USE the Close button

6. Muon Shifter Start Manual – July 08 6 UseComp name PVSS IdProject Name Feb 2&3/C MUDAQC03w 260 MUDAQC23 Feb 4&5/C MUDAQC04w 261 MUDAQC45 Feb 1/C MUDAQC01w 262 MUDAQC1 Feb 1/A MUDAQA01w 263 MUDAQA1 Feb 2&3/A MUDAQA03w 264 MUDAQA23 Feb 4&5/A MUDAQA04w 265 MUDAQA45 FSM/C MUECSC01W 279 MUDAQC FSM/A MUECSA01W 280 MUDAQA LV/C MULVC01w 210 MUDCSLVC LV/A MULVA01w 211 MUDCSLVA HV/C MUHVC01w 212 MUHVC01 HV/C MUHVC02w 213 MUHVC02 HV/A MUHVA01w 214 MUHVA01 HV/A MUHVA02w 215 MUHVA02 ODEQ3/C MUODEC01w 266 MUODEC01 ODEQ4/C MUODEC02w 267 MUODEC02 ODEQ1/A MUODEA01w 268 MUODEA01 ODEQ2/A MUODEA02w 269 MUODEA02 T&P MUDCS01w 270 MUDCSSEN TELL1 M5 : mutella01 (Q1/Q2) mutellc01 (Q4/Q3) M4 : mutella02 (Q1/Q2) mutellc02 (Q4/Q3) M3 : mutella03 (Q1/Q2) mutellc03 (Q4/Q3) M2 : mutella04 (Q1) mutellc04 (Q4) mutella05 (Q2) mutellc05 (Q3) MUON on-line PC and their use Comments: 1.Access to this machines to start/stop/operate the PVSS projects should normally not be needed but for experts. 2.As a general rule, PC names ending with W are Windows-based PCS, Linux otherwise. 3.Some of the reference experts are: R. Nobrega for FEBs, S. Cadeddu for FSM, M. Lenzi for LV and HV, M. Carletti for ODE, G. Graziani for Tell1 and Muon Monitor, C. Deplano.

7. Muon Shifter Start Manual – July 08 7 1. How to... Prepare the MUON system for global DAQ run when everything is ok. In normal conditions, the PVSS projects (FEBs, ODE, FSM) are up and running. This condition should be reached automatically at each power-on of the machines where the projects are installed (see list on next page). At the moment (June 08), this is implemented only for the LV control projects, but will be done soon also for the FEBs and the ODEs. Being in this condition, the steps to set-up the system for DAQ are the following: i.On any computer of the on-line cluster*, go to directory G:\online\ecs\NewShortcuts\MUON ii.Launch (double click) the two shortcuts MUSIDES_UI_DEN and MUSIDES_UI_FSM. This visualizes the two control windows for DEN (Device Editor Navigator) and FSM (Finite State Machine) Hierarchy (see next page). Launching the shortcuts does not start the DEN and FSM processes (which are already running within the PVSS project), but just allows using the corresponding control windows from your screen. (*you need an account within the on-line cluster: ask Niko Neufeld if you haven’t any.)

8. Muon Shifter Start Manual – July 08 8 FSM panel The FSM panel you should have opened allows visualizing the status of the full MUON hierarchy and opening panels related to any hierarchical level. Concerning the DU/CU status, the color code is as follows: grey for DEAD/NOT INCLUDED yellow for NOT READY orange for UNKNOWN/NOT ALLOCATED red for ERROR blue forREADY or ACTIVE (TFC case) green forRUNNING Now, placing the cursor tip on the MUON box and clicking the RIGHT mouse button, opens the MUON CU, which represents the top level of our hierarchy, see next page(s). This box accesses the TELL1 CU (refer to page 15)

9. Muon Shifter Start Manual – July 08 9 MUON CU panel In order to allow the global manager driving the MUON System, the MUON must be NOT_READY and its subsystems NOT_ALLOCATED. All the locks should be grey and open, without any slash on them (which means Not Included). The first operation is TAKING the MUON System under your control. Click (LEFT mouse button) on the lock and select TAKE. The lock goes green and closed. A panel automatically pops up, giving the list of LockedOut nodes and of CU which were not possible to take (more details on page 12). Now OPEN (double click) the two sides (A & C) Although this condition appears to be verified in the shown panel, it is equally necessary to check the MUONA and MUONC CU. Checking deeper levels is not required to a shifter.

10. Muon Shifter Start Manual – July 08 10 MUONA CU panel If everything is correct, the panel appears in the configuration shown. In this conditions, you can release the MUON system in order to make it possible the control by the global console (go to next page) (The MUONC panel has similar face)

11. Muon Shifter Start Manual – July 08 11 MUON CU panel In order to release the MUON system, click on the green lock and choose ReleaseAll in the pop-up menu (the Release button releases this level of CU but not those below it). The MUON status goes to NOT_READY and the system is free to be used by the global console. Note: Case of a subsystem taken by someone else. Placing the mouse on, you obtain info on owner and status. In Global DAQ, the global manager decides what is to be included/excluded. You have to take care only of MUON, putting it in regular shape.

12. Muon Shifter Start Manual – July 08 12 2. How to... Prepare the MUON system for global DAQ run when something is not the right way. Suppose that opening the MUONA panel, a different status is shown (see figure): Some subsystems appear to be locked out and the TFC is ACTIVE, while the right status is NOT_ALLOCATED for the TFC and NOT_READY for the others i.Release MUON (ReleaseAll) ii.TAKE MUONA (where the problem was found) iii.ACTIVE  Stop run  READY iv.READY  RESET v.NOT-READY  DEALLOCATE vi.ReleaseAll (in the lock) This should take again the MUONA in the right shape In such a case, these are the steps to follow: {

13. Muon Shifter Start Manual – July 08 13 DEN panel The DEN panel (you got from page 7) is to be used in case of DEAD states: click on the Start/Restart All button for the relevant stage of the hierarchy (use the FSM tab). This activate the FSM only on the relevant stage and should cure the DEAD state. DEAD states When you TAKE a System, an Action Report appears. In some cases a subsystem cannot be taken because its state is DEAD (i.e. The FSM cannot communicate with it, or the FSM is blocked there)

14. Muon Shifter Start Manual – July 08 14 TELL1 CCPC restart (1) When the the system is being reset or configured, it may happen that the system enter an ERROR state. This state propagates from the DU/CU which originates it, up to the top level of the hierarchy (MUON in our case). Frequently this is caused by the Tell1 CCard, needing to be restarted (see next page). (see next slide also to know how to get to the MUONA(C)_DAQL1 panel). Here “ERROR” appears

15. Muon Shifter Start Manual – July 08 15 1.Descend the hierachy starting from the MUON CU panel: MUON  MUONA (e.g.)  MUONA_DAQ  MUONA_DAQL1(see previous slide). Alternatively, you can access the Tell1 panel directly from the FSM (see page 8). 2.Spot the Tell1 which is in error and identify the corresponding CCPC (see subsystems in the panel and the given correspondance table). 3.Log in on the CCPC using your user/pwd and start the ccserver (using putty, for example). 4.Type the command “sudo service ccserv restart”. You should obtain a double ok. If not, try to repeat the command. This restarts the ccserver and should solve the ERROR Side A PC TELL1 mutella01 MUTELLA_M5Q12 mutella02 MUTELLA_M4Q12 mutella03 MUTELLA_M3Q12 mutella04 MUTELLA_M2Q2 mutella05 MUTELLA_M2Q1 Side C PC TELL1 mutellc01 MUTELLC_M5Q34 mutellc02 MUTELLC_M4Q34 mutellc03 MUTELLC_M3Q34 mutellc04 MUTELLC_M2Q4 mutellc05 MUTELLC_M2Q3 TELL1 CCPC restart (2) Here is how to (possibly) cure a TELL1 ERROR state

16. Muon Shifter Start Manual – July 08 16 Low Voltage panels As of today, the LV domain is not yet reachable from the MUON panel, but only from the DCS hierarchy. To launch the corresponding panel, go again to directory G:\online\ecs\NewShortcuts\MUON and click on the MUDCSLVA_UI_FSM shortcut (in case of A side). Click directly on the relevant CU (RIGHT mouse button), or start from the top level clicking on MUONA_DCS on the FSM panel. The corresponding panel appears. From this panel you can descend the hierarchy across quadrants and stations reaching the LV controls (see next slides)

17. Muon Shifter Start Manual – July 08 17 Low Voltage panels (2) Q1 panel Take before And release all when finished

18. Muon Shifter Start Manual – July 08 18 Q1M23A panel: DAQ tab At this level, the different sub-systems of LV are visible and accessible Act only on the FSM buttons to switch on/off the sub-systems. This part of the panel should be used only to check the effects of the action, not to cause them The DAQ tab refers to ODE, SB & PDM, IB crates

19. Muon Shifter Start Manual – July 08 19 The FEE tab refers to the CARDIAC boards Q1M23A panel: FEE tab

20. Muon Shifter Start Manual – July 08 20 Starting the MuonMoni Presenter The better way to check the global status of the detector is looking at the data quality by means of the online Presenter. To start the Presenter: 1.Launch Exceed on your PC. There is a small problem with the new Exceed: the default configuration settings are re-set by the installer. Host access is now per default *DISABLED*. To change this open Exceed -> Tools -> Configuration -> Security and remove the access control. 2.Log on mudaq01 (*) 3.type:. /group/muon/scripts/lhcbsetup.sh 4.set local display: export DISPLAY=pcname:0.0 (**) 5.run presenter: /group/muon/scripts/runpresenter (*) Log-in using putty: - session: mudaq01 - connection SSH X11 (enable x11 forwarding) open and login (**) PC name : see label glued on the monitor See the twiki page https://twiki.cern.ch/twiki/bin/view/LHCb/MuonDaqMonitoring about the use of the Presenterhttps://twiki.cern.ch/twiki/bin/view/LHCb/MuonDaqMonitoring