Discrepany in R26 and R56 for transversely offset KQUAD

Moderators: cyao, michael_borland

Post Reply
Zamank
Posts: 58
Joined: 03 Dec 2013, 10:57

Discrepany in R26 and R56 for transversely offset KQUAD

Post by Zamank » 29 Nov 2023, 06:55

Hi Michael,

I am creating a beamline with an DX-offset quadrupole to induce some fine-tuned dispersion. But I noticed when I look at the R-matrix for the offset quadrupole there is no effect on the R56. Additionally when I cross-reference with another particle tracking code (Bmad) I get completely different R56 and R26 as well. I did try toggling all the parameters I could find in the KQUAD element to "turn-on" the R56 but with no luck.

Would you have any insight on this matter? I've attached a sample file.

Thanks in advance!
Attachments
kquad.zip
(3 KiB) Downloaded 25 times

michael_borland
Posts: 1933
Joined: 19 May 2008, 09:33
Location: Argonne National Laboratory
Contact:

Re: Discrepany in R26 and R56 for transversely offset KQUAD

Post by michael_borland » 19 Dec 2023, 18:42

I'll have to look into why that term is missing. Meanwhile, you can add "TRACKING_MATRIX=2" to the definition of the KQUAD element to get a tracking-based matrix, which includes this term.

I suppose that other R5X and RX6 terms will also change as a result.

One thing to be aware of in comparing to other codes is that elegant uses s as the longitudinal coordinate, whereas most other codes use s0-s. So there's a sign change in all terms R5X and RX5.

--Michael

Zamank
Posts: 58
Joined: 03 Dec 2013, 10:57

Re: Discrepany in R26 and R56 for transversely offset KQUAD

Post by Zamank » 27 Dec 2023, 13:45

Great! Thanks for the reply Michael, I'm currently looking into the discrepancy as switching the "TRACKING_MATRIX=2" did turn on the R56 term but the magnitudes of the R16, R26, and R56 are slightly off.

Post Reply