1 / 11

LHC Central Timing: Planning

LHC Central Timing: Planning. Summary. LHC central timing : Overview CO consolidation project Deployment foreseen week 42 New requests from OP CO consolidation project Impacts Future plans Conclusion. LHC central timing: overview. Applications (LHC Sequencer,…). SMPV.

yetta-benjamin
Download Presentation

LHC Central Timing: Planning

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. LHC Central Timing: Planning Jean-Claude BAU / BE-CO-HT

  2. Summary • LHC central timing : Overview • CO consolidation project • Deployment foreseen week 42 • New requests from OP • CO consolidation project • Impacts • Future plans • Conclusion Jean-Claude BAU / BE-CO-HT

  3. LHC central timing: overview Applications (LHC Sequencer,…) SMPV LHCMTG FESA class(Telegram, Beam request) • SMPV GMT cable • Safe Beam permit flags DTM events distribution LHCTM FESA class(Timing tables) Hardware Software SPS GMT cable H a r d w a r e Software CBCM LHCGW LHCA LHCB FEC LHC SRV LHC FEC LHC SRV LHC FEC LHC SRV LHC FEC LHC SRV LHC Beam resquests Hardware LHC GMT cable Jean-Claude BAU / BE-CO-HT

  4. CO consolidation project • It was deployed for the LHC startup and fulfilled its job well during the short phase of the LHC startup and in the dry runs performed since then.   • Developed in a very short time: • No documentation • Difficult to test new features to add in the system • Some technical decisions made are not optimal • Lack of automated and performance tests, validation and test procedures • Only 2 people can intervene in the system • … Jean-Claude BAU / BE-CO-HT

  5. CO consolidation project • Objectives to reach: • Make the system more robust • Simplify the design, reduce critical software and hardware • Improve reaction of the system in case of failures in a HW component, NFS or network problems • Thoroughly test new versions before releasing • Improve documentation and tools • Reduce intervention time in case of problems and upgrades Jean-Claude BAU

  6. Deployment foreseen week 42 • New requests from OP • Optics ID • New group in the telegram “OPTID” • New event HX.OPTID-CT • New management of the LHC Telegram will allow modifications of the telegram through timing tables Jean-Claude BAU / BE-CO-HT

  7. Deployment foreseen week 42 • New requests from OP (continued) • LHC Injection Test Mode • Allows simulation of LHC injection • First software version was installed using a inhibit/request button in CCC • New version with hardware card implementing the requested logic • New patch in CCC with key buttons • 2 keys per button • 1 key in CCC • 1 key to Brennan Goddard • In case of hardware problems, the patch will be replace by CO with a different set of keys. Jean-Claude BAU / BE-CO-HT

  8. Deployment foreseen week 42 • CO consolidation project (Step 1) • New reflective memory driver • New MTT driver and VHDL • SMPV GMT cable connected to MTT module • Management of priority for timing and telegram events • Versioning for configuration data and binaries • Optimization of FESA classes • Master/Slave synchronization • … Jean-Claude BAU / BE-CO-HT

  9. Deployment foreseen week 42 • Impacts • New hardware, new wiring, software deployment • LHC timing distribution will be perturbed • Need a dedicated MD half a day • No modifications are needed for applications Jean-Claude BAU / BE-CO-HT

  10. Future plans • Step 2 of the consolidation (Shutdown 2010) • Change communication protocol with the CBCM • Improve the management of the injection mechanism • … • During the LHC run • Only deployments with low impacts (Telegram changes, new timing events, bug fixes, …) • Prepare next release for shutdown 2010 Jean-Claude BAU / BE-CO-HT

  11. Conclusion • New deployed version for the LHC startup. • The effort of that consolidation project will continue during the LHC run. • We will keep one stable version during the LHC run • The next releasewill be made during the next shutdown. They will imply modifications of the CBCM and the LHC central timing. Jean-Claude BAU / BE-CO-HT

More Related