You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am doing some tests of the matching of the chromatic functions in an insertion line.
If I use a periodic cell (like an arc cell), the matching of second-order dispersion works well.
However, if I use a non-periodic lattice, there are 2 issues.
In the documentation, that is not written that you have to add the flag "use_chromatic_functions = True" in the match (or twiss) functions. That would be nice to add it in the preambule of the match and twiss functions.
When I put this flag True, I can have the second-order dispersion calculated but the matching becomes very slow.
Indeed, at each function call, Xsuite compiles again the line, which makes the matching very slow.
Is there any way to ask not to do that? Xsuite does not do that for matching lattice functions or in a periodic lattice.
Thank you in advance,
I am sure that I have missed something.
The text was updated successfully, but these errors were encountered:
Dear all,
I am doing some tests of the matching of the chromatic functions in an insertion line.
If I use a periodic cell (like an arc cell), the matching of second-order dispersion works well.
However, if I use a non-periodic lattice, there are 2 issues.
In the documentation, that is not written that you have to add the flag "use_chromatic_functions = True" in the match (or twiss) functions. That would be nice to add it in the preambule of the match and twiss functions.
When I put this flag True, I can have the second-order dispersion calculated but the matching becomes very slow.
Indeed, at each function call, Xsuite compiles again the line, which makes the matching very slow.
Is there any way to ask not to do that? Xsuite does not do that for matching lattice functions or in a periodic lattice.
Thank you in advance,
I am sure that I have missed something.
The text was updated successfully, but these errors were encountered: