1. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 LHC COLLIMATION SYSTEM STUDIES USING SIXTRACK Ralph Assmann, Stefano Redaelli, Guillaume Robert-Demolaize

2. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 Outline Status of the tracking code Tracking Models (injection & collision) CPU Limitations How to Simulate ? – Results for IR8 studies Conclusion - Current Work

3. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 Status of the tracking code For all our studies, we use an extended version of SIXTRACK for Collimation: -- based on element-by-element method, we implemented K2 scattering routines to introduce the LHC Cleaning System into the normal tracking procedure, -- a database file has been created, in which we have the design parameters of every ring collimator, both mechanical and optical, used as input for the LHC Aperture Model -- we record the trajectories of all halo particles during the tracking, along with saving the locations of particles impact within the collimation system; the corresponding files are then used as input for the LHC Aperture Model. => complete set of tools for detailed studies: inefficiency curves, loss maps…

4. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 Tracking Models Case studied so far: -- “Perfect Machine” with the Full System, i.e. nominal optics and beam parameters for the LHC Lattice, both for Injection and Collision Optics, -- Closed Orbit deformation with static (injection optics) and dynamic (collision optics) model (only performed for the horizontal plane so far, results still being analyzed). Collimators setting used are also the nominal one, but for Phase 1 only by now, with: -- TCLP.4R1.B1 & TCLP.4R5.B1 (Phase 3) not included, -- TCSMs collimators are not treated (but are included in the code), -- TCLAs in IR3 & IR7 + TDI included, -- Scrapers not included.

5. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005

7. CPU Limitations Code is now running on CERN LSF-Batch system; the Collimation System is designed to have inefficiency values of the order of 10 -5, so one needs to track ~ 5 million particles to have relevant statistics for loss maps. SIXTRACK was originally limited to 64 particles per run => a loop has been implemented in order to track thousands of particles within the same run. Even with this upgrade, a compromise for computing facilities was to be found => currently, jobs are running with 50 packs of 64 particles over 200 turns: need to launch 1600 jobs to achieve 5 million particles (estimated average computing time required: ~ 20 hours for injection case, ~ 30-35 hours for collision case).

8. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 How to simulate ? What we simulate: taking into account the normal losses mechanisms, we assume a drift speed of 5.3 nm/turn. One way to do our simulations is to generate a distribution of the particles that will hit the collimator jaws, i.e. the external part of the beam which has already drifted above 6 σ. First runs were done taking normal losses into account, then we implement the various imperfections (beta-beating, alignment error, coupling…) and accident scenarios. For each run, beam halo is only generated in one plane, either horizontal or vertical: both types are needed for a complete picture of losses.

9. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 How to simulate ? Whenever one of the tracked particles becomes part of the secondary halo (i.e. when it touches a primary collimator), we start saving its trajectory for a later use in a detailed aperture program of the LHC Ring:

10. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 Notes on the renormalization of losses Overall loss rate: for 3e14 p and a lifetime of 3.6e4 s (=10h) we obtain: Rate_loss (LHC) = 3e14/3.6e4 = 8.3e9 p/s Loss rate on the considered collimator TCTH.L8.B1: for 10h beam lifetime due to horizontal losses and the provided simulation: Rate_loss (TCTH.L8.B1) = (1555/4995512) * 8.3e9 p/s = 2.6e6 p/s

11. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 Change in the IR8 Closed Orbit scheme It was found recently that the vertical closed orbit scheme in IR8 for optics version V6.5 was not correct (left: old scheme; right: corrected scheme):

12. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 Influence on the global inefficiency => Files for losses in tertiary collimators should be OK; nevertheless, we do recommend to use the latest results produced (available on demand)

13. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 Results of Simulations for Collision Optics

14. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 Results of Simulations for Collision Optics

15. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 Output files for IR8 studies From the simulations, we can also get the transverse distribution of the inelastic interaction of tracked particles within any given collimator jaw:

16. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 Output files for IR8 studies From the simulations, we can also get the transverse distribution of the inelastic interaction of tracked particles within any given collimator jaw:

17. GRD - Collimation Simulation with SIXTRACK - MIB WG - October 2005 Conclusion – Current Work We can now work with a complete set of detailed tools for the complete LHC Collimation System: -- a tracking tool which treats every single collimator with correct energy change and kick calculation (complete 6D tracking), -- this program can produce input files for both a detailed aperture program (with a 10 cm resolution) and energy deposition studies (distribution of absorptions within any given jaw). Current studies include the description of various halo shapes, the integration of complete error models (orbit, coupling, magnet non- linearities) and scenarios of accident cases. Uncertainty is expected though due to the implementation of error models: the loss rate can easily be a factor 10 higher (system would then be 10 times less efficient) !!!