Elegant users forum

Hi Sun, I don't see any problem with the input files. For linear chromaticity we use dnux/dp and dnuy/dp instead of h11001 and h00111 is because the h coefficients are calculated only at the quadrupole and sextupole locations (1/rho^2 is not counted either); therefore the result is not as precise as...

Hi Sun,

I need your lattice file before I can tell if the results are correct.

Regards,

Weiming

Attached is an example file that optimizes dynamic aperture through resonance term minimization.

Instructions can be found in the file.

Good luck,

Weiming Guo

Michael,

Thanks a lot! I guess I'll just use the alter_elements command for that purpose.

Weiming

Hi Michael, I found the tracking is very slow if I assign files to the fields of Systematic_multipoles and random_multipoles in KQUAD and KSEXT. I guess the element module retrieves the files each time? The multipole specs are usually the same for a family, therefore in most cases it is not needed t...

Michael,

Thanks a lot! Guess how much time I have saved.

Weiming

Michael, To input the higher order multipoles, I use the parameters like systematic_multipoles and random_multipoles for KSEXT and KQUAD. However, I felt inconvenient because I had to manually type this information into the lte file, even though the file names are the same. I can't use the load_para...

Michael,

Nice example. Thanks!

Weiming

Michael, I am using a malign element to offset the energy as following: MA1: MALIGN,ON_PASS=0,dp=0.02 Then I compute close_orbit and beta functions, expecting that Elegant would give optical functions at the desired momentum offset. If I set on_pass = 0, the beta functions are only slight different ...

I checked my original problem. It occurred while I use the command find_aperture. In the lte file I defined two beam lines: ring1 = (MA1,beamline1, beamline2) ring2 = (beamline1,MA1,beamline2) and I searched for dynamic aperture for both beam-lines and I was expecting to get different dynamic apertu...