New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weak focusing for thin dipoles in TWISS #888
Comments
After a short discussion with Riccardo which pointed me in the right direction I also found this : It is very clear that there is a geometrical term and a kind of bending term and my proposed change is therefore correct. |
I think |
Absolutely! I was just changing that now |
Thanks for the comment... Just realized that the "angle" is only for horizontal dipoles, not impossible to change but a bit tricky.. I think we can leave it like this for now.. |
Can't you use |
If you make the vertical dipole from the horizontal using tilt you will get the same result indeed but if you instead would have ksl and an angle then the angle would still be in the horizontal plane. I wasn't the one who implemented this and don't know how well this is documented.. I will have a look. |
This is fixed in PR #887 |
I saw an issue where the chromaticity using the CHROM option and the "normal" was not giving the same result for a case with 0 coupling. It seems to me to come from the weak focusing for a thin dipole
It seems that there is a division with the (1+dp)^2 for the thin focusing when I think it should only be scaled with (1+dp). The line looks like:
re(2,1) = re(2,1) - dipr*dipr/elrad, where dipr = k0L/(1+dp). => re21 = (k0/(1+deltap))^2/lrad
If I add multiply the line above with (1+dp) (it is easier to do it in this way because of all the rotations that takes place before.. ) then re21 = (k0^2/(1+deltap))/lrad
After this modifications the results then becomes consistent with both MAD-X without (chrom option) SixTrack and PTC.
You can see the changes in the code in PR #887 (this also fixes so that chromaticity is given as DQ/DPT even when the chrom option is in use.
The link to an example is attached below.
Anyone has any thoughts? @rdemaria @alatina @ldeniau
The text was updated successfully, but these errors were encountered: