Fast SixTrack Space Charge module JB. Lagrange, H. Bartosik, R. De - - PowerPoint PPT Presentation

fast sixtrack space charge module
SMART_READER_LITE
LIVE PREVIEW

Fast SixTrack Space Charge module JB. Lagrange, H. Bartosik, R. De - - PowerPoint PPT Presentation

Fast SixTrack Space Charge module JB. Lagrange, H. Bartosik, R. De Maria, K. Sjbk, F. Schmidt 1 Disclaimer JB Lagrange - SC Workshop 2017 2 SixTrack Code developed by F. Schmidt (based on an earlier program from DESY)


slide-1
SLIDE 1

Fast SixTrack Space Charge module

  • JB. Lagrange, H. Bartosik, R. De Maria,
  • K. Sjøbæk, F. Schmidt

1

slide-2
SLIDE 2

JB Lagrange - SC Workshop 2017

Disclaimer

2

slide-3
SLIDE 3

JB Lagrange - SC Workshop 2017

SixTrack

3

Code developed by F. Schmidt (based on an earlier program from DESY)

  • Features:

written in Fortran, Symplectic, written in the optics of tracking speed, used and developed by a wide community, conversion routine in MAD-X to create SixTrack input

slide-4
SLIDE 4

JB Lagrange - SC Workshop 2017

Motivation

4

MAD-X SC implemented, but limited parallel computing possibility (built for the adaptive mode). Need for study of very long term space charge effects in several rings at CERN (PS, SPS, LHC,…). Frozen space charge is enough in some studies. Frozen space charge in SixTrack could be heavily parallelised (~100 times faster). Implementation of frozen SC module in SixTrack

slide-5
SLIDE 5

JB Lagrange - SC Workshop 2017

Code versions

5

MAD-X SC 1.01.01 (based on MAD-X 5.02.07) SixTrack 4.7.8

http://github.com/SixTrack/SixTrack

slide-6
SLIDE 6

JB Lagrange - SC Workshop 2017

Beam-Beam & Space Charge

6

Horizontal 4D Beam-Beam kick

(opposite direction, proton-proton, on momentum, round beam): colliding if ultra-relativist,≃1

Horizontal 4D Space Charge kick:

beam direction

= 1 γ2β2

∆x0 = +2Nrcl γ · x ρ2 · 1 + β2 2β2 ✓ 1 − e

−ρ2 2σ2 x

◆ ∆x0 = +2Nrcl γBf · x ρ2 · 1 − β2 β2 ✓ 1 − e

−ρ2 2σ2 x

slide-7
SLIDE 7

JB Lagrange - SC Workshop 2017

MAD-X SC module

7

Use of the MAD-X beam-beam module with specific preparation MAD-X macros and fortran executables. Split the elements to add the SC kick in between. Ultra-relativistic option (flag bb_ultra_relati=true). the factor is added to the charge unit previously. the bunch factor is added to the number of particles previously.

1 γ2β2

slide-8
SLIDE 8

JB Lagrange - SC Workshop 2017

SixTrack beam-beam module & input from MAD-X

8

Very similar than MAD-X beam-beam module. Ultra-relativistic hypothesis by default. Off-momentum behaviour in BB kick included. Input directly produced from MAD-X-SC (SIXTRACK command at the end of the macro)

slide-9
SLIDE 9

JB Lagrange - SC Workshop 2017

Tune spread

9

SPS, 1.5 1011 protons, bunch length 0.22 m, 1000 particles MAD-X-SC SIXTRACK-SC

bare tune

  • max. theoretical

depressed tune bare tune

  • max. theoretical

depressed tune

slide-10
SLIDE 10

JB Lagrange - SC Workshop 2017

10

SixTrack is a fast code with high capability of parallelised computation. In the same way than in MAD-X-SC, the beam-beam module can be used for a frozen space charge study. The input can be produced directly by MAD-X (bug for the SC kicks in dipoles, being investigated). Full benchmark with experiments and other codes (pyORBIT, MAD-X_SC) under way.

Summary & future plans

slide-11
SLIDE 11

Benchmark of PTC-ORBIT and pyORBIT

  • JB. Lagrange, H. Bartosik, F. Schmidt

11

slide-12
SLIDE 12

JB Lagrange - SC Workshop 2017

Motivation

12

PTC-ORBIT not maintained anymore.

  • switch to pyORBIT
  • However:

pyORBIT never used for acceleration and injection all simulations for PS Booster done with PTC-ORBIT Need for a proper benchmarking between the 2 codes.

  • M. Kowalska started a few months ago, I recently took over.
slide-13
SLIDE 13

JB Lagrange - SC Workshop 2017

Simulation parameters used for benchmark

13

PTC-ORBIT:

/afs/cern.ch/project/LIUsc/space_charge/Codes/PTC22.10.2014-ORBIT10_SLC6_mpich2

pyORBIT

/afs/cern.ch/project/LIUsc/space_charge/Codes/py-orbit_revison1291_dev_FrozenPIC

100 000 tracked particles, The 2.5D space charge (SC) method is used in both codes. 100 000 particles,

10 000 turns in the PS Booster (nominal case), SC grid 128x128x64

slide-14
SLIDE 14

JB Lagrange - SC Workshop 2017

Longitudinal binning update

14

PTC-ORBIT updates longitudinal binning only in the longitudinal SC node, and accepts only 1 LSC in the lattice. If we put 200 LSC in PTC-ORBIT, the difference in momentum spread is corrected.

slide-15
SLIDE 15

JB Lagrange - SC Workshop 2017

Smooth longitudinal binning

15

slide-16
SLIDE 16

JB Lagrange - SC Workshop 2017

Injection and acceleration

16

Bug found in pyORBIT, when Twiss parameters are updated in the presence of acceleration, the children nodes are reinitialized and no SC kick is applied. Bug fixed, good agreement after 10 turns.

(5 105 particles injected over 100 turns and tracked for 10 turns)

slide-17
SLIDE 17

JB Lagrange - SC Workshop 2017

Difference in emittance computation

17

in pyORBIT, the emittance is computed only from the beam parameters:

εx = s✓ cov(x, x) − cov(x, ∆E)2 cov(∆E, ∆E) ◆ ✓ cov(x0, x0) − cov(x0, ∆E)2 cov(∆E, ∆E) ◆ − ✓ cov(x, x0) − cov(x, ∆E)cov(x0, ∆E) cov(∆E, ∆E) ◆2

in PTC-ORBIT, the emittance is computed with the ring dispersion for dealing with the momentum spread in horizontal.

slide-18
SLIDE 18

JB Lagrange - SC Workshop 2017

Injection and acceleration (10 first turns)

18

slide-19
SLIDE 19

JB Lagrange - SC Workshop 2017

Summary

19

Good agreement between the 2 codes Some bugs and inconsistencies found in both codes and corrected in pyORBIT