Elegant users forum

Hi, I'm trying to ramp some elements in a ring lattice while at the same time including a computation of the closed orbit so I can use "center_on_orbit=1" in the track command. More specifically, I have some elements with values defined in the lattice which I want to ramp up from zero to their latti...

Thanks a lot for the quick fix, your excellent support is very much appreciated!

Dear Michael and Bob, coupled_twiss_output seems to be broken from version 2022.1 on. I'm running the standard Elegant on Windows. The attached files demonstrate the problem: when running cpldtwiss.ele, Elegant will crash once it starts processing the coupled_twiss_output command. The error occurs ...

Dear Michael and Bob, coupled_twiss_output seems to be broken from version 2022.1 on. I'm running the standard Elegant on Windows. The attached files demonstrate the problem: when running cpldtwiss.ele, Elegant will crash once it starts processing the coupled_twiss_output command. The error occurs f...

Dear Michael, I have a related question regarding the APCONTOUR element: I seem to understand that this element is basically a drift space with an arbitrary (polygon shaped) aperture, given that it has a length item. More importantly, it does not behave like MAXAMP, which allows to define the apertu...

Dear Michael, thanks for the clarification. I can certainly use the MALIGN approach. I don't remember exactly why I started trying the non-working approach. But I was probably misinterpreting the documentation on the start_from_dp_centroid item of the closed_orbit command in the Elegant, which says:...

Dear all, I'm having troubles getting the closed_orbit command to work with off-momentum particles. What I'm trying to do is calculate orbit and Twiss for an off-momentum particle. There is one way I can get what I want, by inserting a MALIGN element and using its DP item to shift the momentum. This...

Hi Michael,

thanks for the quickly. I should've tried that myself, though.

Regards, David

Hi there! I'm having troubles using the #INCLUDE feature in an elegant lattice under Linux. The program seems to always convert the include path to uppercase letters. Since Linux paths are case sensitive, I get a file not found error like this: Unable to find file /HOME/FSY/DONDREKA/LNX/OPTICS/ELEGA...

Michael,
what you suggest works, so thanks for the answer. However, having looked into the manual again, it is not clear to me why this works. Would it be possible to add a few lines to the manual explaining the way limit_in_4d=1 works in mathematical terms?
Cheers, David