LSA optics processing Marek Strzelczyk M Strzelczyk LSA










- Slides: 10
LSA optics processing Marek Strzelczyk M. Strzelczyk - LSA optics processing AB/OP
Overview n n Introduction What do we need in LSA n n n How do we process n n Optics data model Some LSA concepts related to optics Twiss generation Optics upload Further optics usage Remarks, questions, discussion. . . 15/09/2020 M. Strzelczyk - LSA optics processing 2
What do we need in LSA requirements n n Optic - named set of strengths per logical hardware Link between optic and its source (file) – for on-line model Ordered set of optics in time – beamprocess type Data model n n n 15/09/2020 Optics Twiss_outputs Optic_strenghts Optic_parameters Optic_table M. Strzelczyk - LSA optics processing 3
Optics processing n Input: n n n Optics definition files MAD-X job definition file Output: n Optics n n Twiss outputs Strength (K) for each of logical hardware Optics parameters Tools: n n 15/09/2020 Perl script MAD-X M. Strzelczyk - LSA optics processing 4
Process overview n Twiss generation (MAD-X) n n Twiss upload to LSA DB n n Result: twiss_outputs, optics & optics_parameters tables filled Optics population within LSA DB n n Result: Twiss output (files) Result: optic_strengths table filled Further use in LSA n n 15/09/2020 Settings generation On-line model M. Strzelczyk - LSA optics processing 5
Twiss output generation n Loop over optics definition files (in a given path) n MAD-X job definition file substitution n n Betas at IP (in meters) should be clearly defined in source files Source file naming convention (ex. IP 5_beta 11. 0 p. str) Call to MAD-X Output files n n 15/09/2020 Naming convention (ex. lhc. a 1100 c 1100 a 1000 l 1000 p. b 2. data) File name is then used to name an optic M. Strzelczyk - LSA optics processing 6
Optics upload and population in LSA DB n Insert new optics into optics table n n Load all Twiss output files to twiss_outputs table n n n Optic name and beam originating from Twiss output file name Split MCBX. *, MCX 3. *, MCSOX. *, MCDO. * Fill optic_parameters table Loop over all Twiss outputs of a given optics set n Loop over all elements n Take appropriate value from file (K 0 L, K 1 L, VKICK, K 1 S, . . . ) § Resolve using element type (RBEND, QUADRUPOLE, VKICKER, . . . ) and element name n 15/09/2020 Put the strength into optic_strengths table M. Strzelczyk - LSA optics processing 7
Error handling n Check for: n n n Overwriting the existing optic Not existing elements Missing strengths Strength differences among elements of the same logical hardware. . . Create a log file 15/09/2020 M. Strzelczyk - LSA optics processing 8
Remarks. . . n n Process of Twiss output generation and optics upload is automatised It relies on some conventions Procedure is well established. . . but still evolving n n 15/09/2020 New requirements are being precised Improvements are being done M. Strzelczyk - LSA optics processing 9
Questions? n . . . 15/09/2020 M. Strzelczyk - LSA optics processing 10