Difference: PythonTrackerV1list ( vs. 1)

Revision 117 Aug 2009 - StephenMolloy

Line: 1 to 1
META TOPICPARENT name="PythonTracker"

Capabilities required for release of Version #1


  1. Drift
  2. Quadrupole: Calculation of 'thick' R and T matrices. Twiss propagation. Tracking (with or without synchrotron radiation).
  3. Sextupole: Calculation of 'thick' R and T matrices. Twiss propagation. Tracking (with or without synchrotron radiation). Inclusion of an additional element to perform the same operations for a thin sextupole.
  4. Basic diagnostics (BPM, screen, wirescanner, OTR/ODR (with limitations), laserwire (with limitations)
  5. Sector bend
  6. Accelerating cavity
  7. Transverse deflecting cavity
  8. Solenoid
  9. Thin multipole

Processing of Diagnostic Elements

The measurements for diagnostic elements is done on the beam distribution as it enters the element (i.e. all measurements are done at the upstream face), so care should be taken when designing the lattice that this is accounted for.

  1. BPMs should return the total charge of the beam (C), the x & y centroids (m), plus the S location (m) of the device. Each device will have an intrinsic resolution that is represented by adding Gaussian noise to the x & y centroid readings. This resolution will be defined for the design charge, and will degrade in the case where charge has been lost upstream (i.e. for those particles whose 6D position contains NaN).
  2. Screens should return the 2D transverse distribution of the particles, as well as the RMS of the x & y spreads.
  3. OTRs are a simple subclass of Screens, and will be processed in exactly the same way.
  4. Wirescanners should return the x, y, & u, distribution of the beam.
  5. Laserwires are a simple subclass of Wirescanners and will be processed in exactly the same way.
  6. ICTs simply return the charge of the beam.



The Track() method will properly track the 6D representation of the particles through all the elements mentioned in the "Elements" subsection of this page, where "properly" implies that the correct 1st and 2nd order matrices will be used, and that any other appropriate effects mentioned on this page (e.g. synchrotron losses or processing of diagnostics output) will be taken care of.

Twiss Propagation

It will be possible to propagate the standard set of Twiss parameters through the lattice, and to acquire their expected values for each element in the line.

Matching (and other optimisation problems)

It will be possible to define an optimisation procedure (using Minuit) that allows tweaking of quad values to achieve a particular set of values for the Twiss parameters at set points in the line. This will allow the matching of two different beamline (e.g. two sections of a transport line), or the matching of the start and end conditions of a ring.

This will be written in such a way that generic optimisation routines are possible.


Settings just to customise this page

  • Set STYLESIDEBAR = off
  • Set ALLOWTOPICVIEW = TWikiGuest, JohnAdamsInstituteGroup
  • Set MYTITLE = - Version 1 Capabilities of the Charged Particle Tracker
  • Set MYDESCR =
  • Set MYKEYS =
-- StephenMolloy - 17 Aug 2009
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding RHUL Physics Department TWiki? Send feedback