Trajectory correction issue
Posted: 28 Nov 2011, 08:46
Hello Michael,
I've been running trajectory correction simulations with Elegant v24.1Beta1 on Ubuntu 11.10 (I compiled it from the available source this summer). The trajectory correction algorithm converges nicely after applying the error model and I get realistic kick strengths and trajectory deviations. This behaviour was reproduced by another colleague using Linux but installing from the available binaries instead. However, sending the same input files to several colleagues running Elegant v24.0.1 on Windows (installed via the available binaries) the simulation diverges and results in an extremely long bunch length. At this point the simulation fails due to the bunch being longer than the defined linac wake fields.
As the only change made between the versions was altering all '/' to '\' for the file name references in the max4.ele file, I am somewhat confused at the result: I didn't see anything regarding trajectory correction listed under known bugs. Did something change in Elegant's trajectory correction routines between the two versions?
Regards,
/Magnus Sjöström
PS
Note that the file daresburyastrain.sdds, which contains the beam input data, is missing in the archive. It is about 4 MB, which is the reason I could not add it. I can mail it if needed.
I've been running trajectory correction simulations with Elegant v24.1Beta1 on Ubuntu 11.10 (I compiled it from the available source this summer). The trajectory correction algorithm converges nicely after applying the error model and I get realistic kick strengths and trajectory deviations. This behaviour was reproduced by another colleague using Linux but installing from the available binaries instead. However, sending the same input files to several colleagues running Elegant v24.0.1 on Windows (installed via the available binaries) the simulation diverges and results in an extremely long bunch length. At this point the simulation fails due to the bunch being longer than the defined linac wake fields.
As the only change made between the versions was altering all '/' to '\' for the file name references in the max4.ele file, I am somewhat confused at the result: I didn't see anything regarding trajectory correction listed under known bugs. Did something change in Elegant's trajectory correction routines between the two versions?
Regards,
/Magnus Sjöström
PS
Note that the file daresburyastrain.sdds, which contains the beam input data, is missing in the archive. It is about 4 MB, which is the reason I could not add it. I can mail it if needed.