Beams and Lattices

Lattices

In order of how up to date each lattice is (first is most up to date):

0. FrontEnd_current: always redirects to the most recent version
1. FrontEnd_v1.1_IDR_discrete: version of FrontEnd_v1.0_IDR_base with reduced number of RF cavities designed to be a bit cheaper
2. FrontEnd_v1.0_IDR_base: shorter version of FrontEnd_v0.0_FS2A_p63a front end lattice designed to produce a shorter bunch train
3. FrontEnd_v0.0_FS2A_p63a: original front end lattice from ISS report

Target_FS2_2009-04-13 is included for reference but is certainly not the most recent version of the lattice

Beams

Beams for input into the front end are stored in FrontEnd_Beam.  Beams output from front end (for input into Linac) are stored in Linac_Beam.

In the FrontEnd_Beam directory there is a beam_plotter script - this is supposed to be the start of a QA process for input beams.  For now just plots interesting quantities for input beam.

Codes

We use two codes for the front end - G4Beamline and ICOOL. Because the physics model in these codes can change from version to version, we officially sanction:

• G4Beamline version 2.06
• ICOOL version 3.20
• ecalc9f version 2.09 (version 2.10 seems to have a bug)

For physics analysis, we either use ICOOL ecalc9f code or XBOA code.  People sometimes roll their own.

Note

Nb: this site replicates functionality that one would get from a proper VCS like mercurial, git, svn, bzr, cvs.  Maybe would be better to do this + sourceforge (or whatever) for an http interface?