The tracking results of pyAT and AT are different. #931
ascetic0515
started this conversation in
Python AT
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, after I import and generate a Lattice in MATLAB, I copy the ".m" file to pyAT. I've noticed that the parameters obtained from ringpara in MATLAB and get_radiation() in pyAT have slight differences, such as chromaticity differing by one in a thousand, and the working point differing by an even smaller magnitude. Then, when I use Tracking for particle tracking, I find that the particle loss locations in pyAT and MATLAB are inconsistent. I observed that the difference in chromaticity obtained from get_radiation() and get_chrom() is due to one having a default empty energy dispersion value and the other having a default value of 0. However, even after I modified this, the issue still persists. I'm wondering if it's possible for the particle tracking loss locations to be different.
Beta Was this translation helpful? Give feedback.
All reactions