1 / 17

Commissioning Status & Plans of the Muon System

Commissioning Status & Plans of the Muon System. FOREWORDS This is not a talk , but a document to be used as a tool for circulating ideas, proposals and try to establish a (hopefully) reasonable and commonly agreed schedule of the commissioning activities.

brad
Download Presentation

Commissioning Status & Plans of the Muon System

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. Commissioning Status & Plans of the Muon System • FOREWORDS • This is not a talk, but a document to be used as a tool for circulating ideas, proposals and try to establish a (hopefully) reasonable and commonly agreed schedule of the commissioning activities. • The document is dynamic and will be updated (and fixed) at the end of each week, so that it could be used at a reference for the activity of the subsequent week. • The document is organized as follows: • The activities for system commissioning are distinguished by typology or “field of actions”. • For each “field of action” we show briefly the status and what actions are to be taken in the near future (one month). • Both the status and the actions to be taken are given for each system Quadrant, with the exception of ECS, where this distinction is of small significance. • For each action we indicate one or more people and, if it is the case, we signal the lack of people. No people = no actions (is that clear?). • After the tables given for each “field of action”, a summary is given containing the activity scheduled for the next week 28/3/2008 – Commissioning Coordination Slides

  2. INDEX of activities (to be completed) • Connectivity tests a. FEE to ODE … slides 4-5 b. ODE to L0Muon … slides 6-7 • Timing … slides 8-9 • TELL1 … slides 10-11 • ECS … slides 12-13 • Offline & Monitoring … slide 14 • M1 … slide 15 • Data taking program … slide 16 Summary for next week … slide 17 28/3/2008 – Commissioning Coordination Slides

  3. Man/woman power 28/3/2008 – Commissioning Coordination Slides

  4. 1. Connectivity tests: FEE  ODE Status (end of March) : Notes/Comments 28/3/2008 – Commissioning Coordination Slides

  5. 1. Connectivity tests: FEE  ODE Actions (April) : week what who Notes/comments 28/3/2008 – Commissioning Coordination Slides

  6. 1. Connectivity tests: ODE  L0Muon Status (end March) : Notes/Comments 28/3/2008 – Commissioning Coordination Slides

  7. 1. Connectivity tests: ODE  L0Muon Actions (April) : week what who Notes/comments 28/3/2008 – Commissioning Coordination Slides

  8. 2. Timing Status (end March) : Notes/Comments 28/3/2008 – Commissioning Coordination Slides

  9. 2. Timing Actions (April) : week what who Notes/comments Timing of side A after completion of side C 28/3/2008 – Commissioning Coordination Slides

  10. 3. Tell1: connectivity & more Status (end March) : Notes/Comments 28/3/2008 – Commissioning Coordination Slides

  11. 3. Tell1 Actions (April) : who week what Notes/comments 28/3/2008 – Commissioning Coordination Slides

  12. 4. ECS General Status (end of March): • The ECS structure is operative (FSM, panels) and tested successfully in Global Commissioning runs. • In practical activities, many functionalities to be realized and/or improved showed up. These are mandatory in order to have a reliable ECS, ready for general use. • In particular (Chambers): • Configuration takes too a long time (12 min vs ~2 min of the other sub-detectors). • A more flexible recipe-saving procedure is needed (partial update of the system recipes). This is very useful to save timing recipes. • SB & PDM are to be included in the FSM hierarchy • Panels are to be made accessible from the hierarchy PC. • “Normal user” (non expert) interface. • Other issues: • “Fat OPC server” effect (diagnosis & therapy) • Alerts/error messages and alert policy are completely lacking • For ODE: • - Firmware & software should be updated in all Quadrants • Error messages also lacking • “Normal user” (non expert) interface • HV/LV & Tell1 is almost in “final” shape • In general: debug, debug and debug… And when you have debugged, debugged and debugged, then start to debug… 28/3/2008 – Commissioning Coordination Slides

  13. 4. ECS Actions (April) : 28/3/2008 – Commissioning Coordination Slides

  14. 5. Offline (commissioning related issues) To be scheduled soon: Integration of Muon Monitoring on the Monitoring Farm during global commissioning runs (could be done next week 31/3) To discuss: Status of analysis tools for prompt cosmic run analysis (Als, GG). 28/3/2008 – Commissioning Coordination Slides

  15. 6. M1 installation & commissioning Very soon (hopefully), also M1 will join this flow of activities. AC, PC et al. are invited to provide details when and how they think that suitable. 28/3/2008 – Commissioning Coordination Slides

  16. 7. Planning of Data taking tests • This point deserves a dedicated and accurate discussion. • Several DAQ configuration have to/can be envisaged and tested: • Cosmics with Calorimeter trigger • Cosmics with Muon trigger • Coincidence between stations and gaps in OR • Coincidence between stations and gaps in AND • Trigger on M3, gaps in AND • Cosmics with Calorimeter & Muon triggers (correlation) • Random trigger to test the level of detector noise • Many others • In general, we must keep in mind that there is still a lot of work to do in order to have a “Mu machine” stable, reliable, reasonably efficient and we should not surrender to the temptation to use it as it is to obtain a quick and dirty result, because dirt has the bad habit to accumulate and sooner or later would submerge us . • My proposal (AL) is to schedule 1 full day per week to data taking tests and exercises (for example each Thursday) and plan a list of different configuration in a well reasoned order. • In the rest of the week we proceed with HW & SW commissioning. 28/3/2008 – Commissioning Coordination Slides

  17. Summary of activities and schedule for next week Monday Test of new recipe loading procedure for chambers (RN) Check of bugs found in the ODE ECS (MC, CD) Start of Q3 connectivity debug (CD, NB) Start of Q1 connectivity & BER tests ODE-L0mu (SC, Marseille) Tuesday Q3 connectivity debug (CD, NB). Connectivity on Q4 if possible Q1 connectivity & BER tests ODE-L0mu (SC, Marseille) Wednesday Q1 connectivity & BER tests ODE-L0mu (SC, Marseille) Q3 connectivity debug end (CD, NB). Connectivity on Q4 if possible. Start of timing debug on Q3 (CD). Test of TELL1 firmware on Q3 (CD, GG) Thursday DAQ in global commissioning. L0mu trigger, stations in coincidence, gaps in OR. If enough time, also runs with gaps in AND. Friday Program of previous day concludes. In the afternoon complete tests on Tell1 firmware, if still needed. 28/3/2008 – Commissioning Coordination Slides

More Related