1 / 28

Status of LHC applications

E-LTC march 2008 – Session 6 Readiness of Controls. Status of LHC applications. Delphine Jacquet (AB/OP) Thanks to all persons named in the presentation. OVERVIEW OF NEEDED APPLICATIONS. 1. SETTINGS MANAGEMENT. SETTINGS GENERATION. Responsible persons

clea
Télécharger la présentation

Status of LHC applications

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. E-LTC march 2008 – Session 6Readiness of Controls Status of LHC applications Delphine Jacquet (AB/OP) Thanks to all persons named in the presentation

  2. OVERVIEW OF NEEDED APPLICATIONS 1

  3. SETTINGS MANAGEMENT

  4. SETTINGS GENERATION • Responsible persons • Lasse Normann, Mike Lamont, Marek Strzelczyk, Delphine Jacquet (AB/OP) • Status • Generic application, used and tested in SPS and LEIR • Actual settings : can generate from a cycle, incorporation into next cycle to be done. • Value generators and makerules to be completed 2

  5. TRIM APPLICATION / DRIVE HARDWARE • Responsible person • Greg Kruk (AB/CO/AP) • Status • Generic applications, used in SPS and LEIR • Trim of discrete and actual settings can be improved 3

  6. OPTICS APPLICATIONS • Responsible persons • Jutta Netzel for LSA (AB/CO) • Ilya Agapov for the online model server • Status • Knob application : knob creation from a file  used in SPS and transfer lines already.New : knob creation from the online model : v1 in place, to be tested. • Trim simulation application (using OM Server): first version in place 4

  7. EQUIPEMENT

  8. EQUIP STATE • Responsible person • Greg Kruk (AB/CO) • Status • Generic application, used and tested in SPS and for HWC • Properties and commands definition to be completed (80% is there) 5

  9. BEAM DUMP (Status – control) • Responsible person • Markus Albert (AB/OP) • Status • v1 operational, tested during beam dump dry run. 6

  10. XPOC • Responsible persons • Jerome Axensalva (AB/OP) • Eric Gallet(AB/BT) • Status • acquisition server and 50% of the online analysis has been tested during the beam dump dry run. • Operational GUI : prototype • Still to do • Complete the online analysis • Communication with the sequencer • Application reliability 7

  11. INJECTION KICKERS • Responsible person • GH Hemelsoet (AB/OP) • Status • v1 operational. • Has to be included in LSA and use the trim package. 8

  12. RF SLOW CONTROL • Responsible person • Delphine Jacquet (AB/OP) • Status • v1 operational and tested. • To be put in users hands for feedback 9

  13. RF LOW LEVELTRANSVERSE & LONGITIDINAL FEEDBACK • Responsible person • Delphine Jacquet (AB/OP) • Status • FESA class to be completed • Parameter space definition : waiting for RF people feedback • Access to RF FGC from LSA : started • The settings generation and trim applications will be used for RF_FGC settings  value generators and makerules 10

  14. COLLIMATORS • Responsible person • Stefano Raedelli (AB/OP) • Status • Beam based alignment application (1 coll) : V1 tested in transfer lines • Parameter space and makerules are defined and tested. • A dedicated trim application has been developed • Fixed Display : work in progress 11

  15. INSTRUMENTATION

  16. BEAM LOSS APPLICATION • Responsible persons • Fabio Follin, Laurette Ponce (AB/OP) • Status • BLM readings from the concentrator  V1 in place • Threshold management  Database configuration, operational application : in progress, 60% done • Fixed Display almost ready. 12

  17. BTV • Responsible person : • Fabio Follin (AB/OP) • Status • Generic application used in SPS • Ready for LHC BTVI 13

  18. TUNE/CHROMATICITY MEASUREMENTAND FEEDBACK (BQBBQ & BQHT) • Responsible persons • Ralph Steinhagen (AB/BI) • Jorg Wenninger, Fabio Follin (AB/OP) • Status • The BI-Expert application will be used in operation • It has been already tested during SPS MD’s (see Ralph’s talk) 14

  19. BPM : YASP, Orbit feedback • Responsible person • Jorg Wenninger (AB/OP) for YASP • Ralph Steinhagen(AB/BI) for the feedback • Status • YASP is ready for LHC. • Orbit feedback will be controlled from YASP (see Jorg’s talk) • BPM fixed display : prototype in place 15

  20. BPM : MULTITURN ANALYSIS • Responsibleperson • Verena Kain (AB/OP) • Status • Most of the functionality is ready • Send timing event to trigger acquisition, interfaces to BPM concentrator • Settings and sensitivity control • Harmonic analysis • To be completed • Synchronized acquisition with MKQ excitation • Phase advance and phase space plots 16

  21. FAST RINGS BCT, BCT • Responsible person • Markus Albert (AB/OP) • Status • Fast BCT  V1 is ready, measurement and device configuration. • BCT  fixed display in place. 17

  22. SYNCHROTRON RADIATION MONITOR / WIRESCANNER • Responsible persons • Wirescanner : Elliot McCrory (LAFS) and Guy Crockford(AB/OP) • SRMA : Elliot McCrory and Laurette Ponce (AB/OP) • Status • Functionalities in place, bug fixing • Wirescanner : needs the bunch spacing definition, it ‘s hard-coded until it is defined in a database. 18

  23. OTHER INSTRUMENTS • Ionization Gas Monitor (BGI) • Elliot McCrory. • Waiting for the FESA class to be ready. • A lot will be re-used from the wirescanner and SRMA applications. • Schottky (BQS) • not clear who and how between LARS and LAFS. • Luminosity monitors(BRA) • Elliot McCrory, fixed display and luminosity scan application are needed. • Abort Gap Monitor(BSRA) • Laurette Ponce (AB/OP)  development is starting now. • K-modulation • Bernt Dehning (AB/BI) • Wall current monitor • FESA class to be developed by RF • Beta beating • Rogelio Thomas Garcia (AB/ABP) : first prototype in place, it uses data from the steering and the multi-turn applications 19

  24. GENERAL APPLICATION

  25. SEQUENCER • Responsible persons • Reyes Alemani (AB/OP) • Vito Bagglionni (AB/CO) • Status • New LHC sequencer has been tested during dry runs • Lots of works to be done on sequences definitions(see Reyes’ talk). 20

  26. TIMING • Responsible persons • Stephane Deghaye (AB/CO) • Delphine Jacquet (AB/OP) • Status • The timing editor has been used during injection and beam dump dry runs • send event • create/edit/load timing table • monitor/edit telegram • Still to be implemented • check of duplicate events in loaded timing tables • prevention of traffic jam. 21

  27. OTHERS • Interlocks • PIC application • Markus Zerlaut (AB/CO)  ready, already used for HWC (Markus Zerlaut). • BIS • generic application, used in SPS Bruno Puccio (AB/CO)  responsible for the softwareAlick McPherson  responsible for the configuration • SIS • generic application, used in SPS Jakub Wozniak (AB/CO)  responsible for the softwareJorg Wenninger (AB/OP)  responsible for the configuration • Logging / Alarms/ Post mortem • Responsibility of AB/CO • Generic applications used for hardware commissioning and in SPS. • This tools now have to be configured for LHC operation. The responsible persons for the configuration have to be defined. • Radiation monitor • A simple fixed display will be done by OP. The acquisition through japc has been tested. • Final State Machine • Specifications will be written with LAFS collaboration 22

  28. CONCLUSION • Some applications are generic, already used and tested in other accelerators or in HWC. • For most of the applications needed for a sector test and at phase 1, a working version is already in place : • Basic functionality in place. • Needs to be completed and tested. • RF low level and damper control application • FESA classes have to be completed, • parameters space definition has to be validated.  We need a first version for day 1. • For some instruments, the application development not started • Some are not critical for day 1, some are expected to be developed quickly. • Many DRY RUNS are planned, they are essential to • Debug the applications • Test the functionalities, find what is missing • Get the users feedback 23

More Related