bunched_beam

• type: setup command.
• function: set up for tracking of particle coordinates with various distributions.

&bunched_beam
    STRING bunch = NULL;
    long n_particles_per_bunch = 1;
    double time_start = 0;
    STRING matched_to_cell = NULL;
    double emit_x  = 0;
    double emit_nx  = 0;
    double beta_x  = 1.0;
    double alpha_x = 0.0;
    double eta_x   = 0.0;
    double etap_x  = 0.0;
    double emit_y  = 0;
    double emit_ny  = 0;
    double beta_y  = 1.0;
    double alpha_y = 0.0;
    double eta_y   = 0.0;
    double etap_y  = 0.0;
    long use_twiss_command_values = 0;
    double Po = 0.0;
    double sigma_dp = 0.0;
    double sigma_s = 0.0;
    double dp_s_coupling = 0;
    double emit_z = 0;
    double beta_z = 0;
    double alpha_z = 0;
    double momentum_chirp = 0;
    long one_random_bunch = 1;
    long symmetrize = 0;
    long halton_sequence[3] = {0, 0, 0};
    long halton_radix[6] = {0, 0, 0, 0, 0, 0};
    long randomize_order[3] = {0, 0, 0};
    long limit_invariants = 0;
    long limit_in_4d = 0;
    long enforce_rms_values[3] = {0, 0, 0};
    double distribution_cutoff[3] = {2, 2, 2};
    STRING distribution_type[3] = {"gaussian","gaussian","gaussian"};
    double centroid[6] = {0.0, 0.0, 0.0, 0.0, 0.0, 0.0};
    long first_is_fiducial = 0;
    long save_initial_coordinates = 1;
&end

• bunch -- The (incomplete) name of an SDDS file to which the phase-space coordinates of the bunches are to be written. Recommended value: ``%s.bun''.
• n_particles_per_bunch -- Number of particles in each bunch.
• time_start -- The central value of the time coordinate for the bunch.
• matched_to_cell -- The name of a beamline from which the Twiss parameters of the bunch are to be computed.
• emit_X -- RMS emittance for the X plane.
• emit_nX -- RMS normalized emittance for the X plane. Ignored if emit_X is nonzero.
• beta_X, alpha_X, eta_X, etap_X -- Twiss parameters for the X plane.
• use_twiss_command_values -- If nonzero, then the values for $\beta$, $\alpha$, $\eta$, and $\eta^\prime$ are taken from the twiss_output command. It is an error if no twiss_output command has been given.
• Po -- Central momentum of the bunch.
• sigma_dp, sigma_s -- Fractional momentum spread, ${\rm\delta}$, and bunch length. Note that sigma_s is actually the length in $\beta_z*c*t$, so that for $\beta_z<<1$ the length of the bunch in time will be greater than one might expect.
• dp_s_coupling -- Specifies the coupling between s and ${\rm\delta}$, defined as ${\rm\langle s \delta \rangle/(\sigma_s\sigma_\delta)}$.
• emit_z, beta_z, alpha_z -- Provide another way to specify the longitudinal phase space, either separately from or in combination with sigma_dp, sigma_s, and dp_s_coupling.

  Basically, which values elegant uses depends on what one sets to nonzero values. If one sets emit_z, then sigma_dp, sigma_s, and dp_s_coupling are ignored. If one doesn't set emit_z, then elegant uses sigma_dp and sigma_s; it additionally uses alpha_z if it is nonzero, otherwise it uses dp_s_coupling. For reference, the relationship between them is $C = \frac{\Sigma_{56}}{\sqrt{\Sigma_{55}\Sigma_{66}}} = -\frac{\alpha}{\sqrt{1+\alpha^2}}$. Note that to impart a chirp that results in compression for $R_{56}<0$ (e.g., a normal four-dipole chicane), one must have $\alpha_z<0$ or $C>0$.

• momentum_chirp -- Permits imparting an additional momentum chirp to the beam, in units of 1/m. E.g., a value of 1 indicates that a 1mm long bunch has a linear variation in momentum of 0.1% from end-to-end. A positive chirp is needed to provide compression of a bunch with an ordinary $R_{56}<0$ four-dipole chicane.

• one_random_bunch -- If non-zero, then only one random particle distribution is generated. Otherwise, a new distribution will be generated for every simulation step.
• enforce_rms_values[3] -- Flags, one for each plane, indicating whether to force the distribution to have the specified RMS properties.

• distribution_cutoff[3] -- Distribution cutoff parameters for each plane. For gaussian distributions, this is the number of sigmas to use. For other distributions, this number simply multiplies the sizes. This is potentially confusing and hence it is suggested that the distribution cutoff be set to 1 for nongaussian beams.

• distribution_type[3] -- Distribution type for each plane. May be ``gaussian'', ``hard-edge'', ``uniform-ellipse'', ``shell'', ``dynamic-aperture'', ``line'', ``halo(gaussian)''.

  For the transverse plane, the interpretation of the emittance is different for the different beam types. For gaussian beams, the emittances are rms values. For all other types, $\sqrt{\epsilon*\beta}$ times the distribution cutoff defines the edge of the beam in position space, while $\sqrt{\epsilon*(1+\alpha^2)/\beta}$ times the distribution cutoff defines the edge of the beam in slope space.

  A hard-edge beam is a uniformly-filled parallelogram in phase space. A uniform-ellipse beam is a uniformly-filled ellipse in phase space. A shell beam is a hollow ellipse in phase space. A dynamic aperture beam has zero slope and uniform spacing in position coordinates. A line beam is a line in phase space. A ``halo(gaussian)'' beam is the part of the gaussian distribution beyond the distribution cutoff.

• limit_invariants -- If non-zero, the distribution cutoffs are applied to the invariants, rather than to the coordinates. This is useful for gaussian beams when the distribution cutoff is small.

• limit_in_4d -- If non-zero, then the transverse distribution is taken to be a 4-d gaussian or uniform distribution. One of these must be chosen using the distribution_type control. It must be the same for x and y. This is useful, for example, if you want to make a cylindrically symmetric beam.

• symmetrize -- If non-zero, the distribution is symmetric under changes of sign in the coordinates. Automatically results in a zero centroid for all coordinates.

• halton_sequence[3] and halton_radix[6] -- This provides a ``quiet-start'' feature by choosing Halton sequences in place of random number generation. There are three new variables that control this feature. halton_sequence is an array of three flags that permit turning on Halton sequence generation for the horizontal, vertical, or longitudinal planes. For example, halton_sequence[0] = 3*1 will turn on Halton sequences for all three planes, while halton_sequence[2] = 1, will turn it on for the longitudinal plane only.

  halton_radix is an array of six integers that permit giving the radix for each sequence (i.e., x, x', y, y', t, p). Each radix must be a prime number. One should never use the same prime for two sequences, unless one randomizes the order of the sequences relative to each other (see the next item). If these are left at zero, then elegant chooses values that eliminate phase-space banding to some extent. The user is cautioned to plot all coordinate combinations for the initial phase space to ensure that no unacceptable banding is present.

  A suggested way to use Halton sequences is to set halton_radix[0] = 2, 3, 2, 3, 2, 3 and to set randomize_order[0] = 2, 2, 2,. This avoids banding that may result from choosing larger radix values.

• randomize_order[3] -- Allows randomizing the order of assigned coordinates for the pairs (x, x'), (y, y'), and (t,p). 0 means no randomization; 1 means randomize (x, x', y, y', t, p) values independently, which destroys any x-x', y-y', and t-p correlations; 2 means randomize (x, x'), (y, y'), and (t, p) in pair-wise fashion. This is used with Halton sequences to remove banding. It is suggested that that the user employ sddsanalyzebeam to verify that the beam properties when randomization is used.

• centroid[6] -- Centroid offsets for each of the six coordinates.

• first_is_fiducial -- Specifies that the first beam generated shall be a single particle beam, which is suitable for fiducialization. See the section on ``Fiducialization in elegant'' for more discussion.

• save_initial_coordinates -- A flag that, if set, results in saving initial coordinates of tracked particles in memory. This is the default behavior. If unset, the initial coordinates are not saved, but are regenerated each time they are needed. This is more memory efficient and is useful for tracking very large numbers of particles.