Known Bugs, Problems, and Limitations

• Setting CHANGE_T=1 on RFCA and RFCW elements can give invalid results when tracking beams with very large time spread compared to the bunch length.
• Twiss output contains entries for the higher-order dispersion, tune shifts with amplitude, higher-order chromaticity, and tune spreads due to chromaticity and amplitude even when these are not calculated, which is potentially misleading. The values are zero when the calculation is not requested.
• Computation of closed orbits and Twiss parameters will not always include the effects of synchrotron radiation losses when these are imposed using SREFFECTS elements. See the documentation for SREFFECTS for details.
• Computation of beam moments does not include synchrotron radiation effects from CWIGGLER, WIGGLER, or UKICKMAP elements.
• The file created with the parameters field of run_setup does not contain any non-numerical parameters of the lattice.
• When transmute_elements is used to turn a sextupole into a quadrupole, several problems are seen. Some of the quadrupole parameters are filled with garbage values. When alter_elements or save_lattice are subsequently used, elegant crashes. These problems were reported by V. Sajaev (ANL).
• Computation of radiation integrals does not include the effect of steering magnets.
• There is a bug related to using ILMATRIX that will result in a crash if one does not request computation of the twiss parameters. If you encounter this problem, just add the following statement after the run_setup command:

  &twiss_output
          matched = 1
  &end