Inconsistence in particleID generated with bunched_beam using Elegant and Pelegant
Posted: 02 Feb 2020, 23:17
Hi Michael,
As shown in the attached example, I attempted to use the first_is_fiducial mode in run_control and bunched_beam, to generate a first beam with a single particle for fiducialization and then track the second beam with the desired beam distribution. If I execute Elegant, the particleIDs of the second beam starts from 2. In contrast, if I execute Pelegant, the particleIDs of the second beam starts from 1. This could lead to some inconsistence if one wants to alter the DT of MALIGN among a range of particleIDs, say, only for the second beam.
Best,
Zhe
As shown in the attached example, I attempted to use the first_is_fiducial mode in run_control and bunched_beam, to generate a first beam with a single particle for fiducialization and then track the second beam with the desired beam distribution. If I execute Elegant, the particleIDs of the second beam starts from 2. In contrast, if I execute Pelegant, the particleIDs of the second beam starts from 1. This could lead to some inconsistence if one wants to alter the DT of MALIGN among a range of particleIDs, say, only for the second beam.
Best,
Zhe