Elegant users forum

The Advanced Photon Source has an opening for an Assistant Physicist in the Accelerator Operations and Physics Group. The position involves hands-on work on accelerators, simulation, and machine learning.

If interested, please click here.

--Michael

Zhenbiao, I've never used LiTrack, but I think the sign convention for R56 is the opposite of elegant's. Usually in elegant we define the bunch compressors explicitly using bending magnets. However, it is possible to use the EMATRIX element to simulate a matrix defined by the matrix elements. An exa...

Mikhail,

Please see the attached example. It converges in four iterations.

--Michael

Samira, The problem seems to be that your field file does not define a quadrupole magnet. To check this, I computed dBy/dx at y=0 and dBx/dy at x=0 as a function of z. sddssort fieldmap300.sdds -pipe=out -col=z -col=x -col=y | sddsbreak -pipe -change=z | sddsprocess -pipe -filter=col,y,-1e-6,1e-6 -p...

Minghao, Setting fiducialize=1 is recommended if you are performing one-pass momentum aperture in a system with large energy losses or gain. An example is a linac. For storage rings, it should be zero. soft_failure is used to control what happens when the momentum acceptance is not found one or more...

Mikhail,

The ability to perform (delta, x) and (delta, y) aperture finding will appear in the next release.

Thanks for the suggestion.

--Michael

Mikhail, I think the only way you can get what I understand you are looking for is to use something other than line-search mode. By definition, line-search mode searches along lines starting from the origin. The radial spacing along the lines is xmax/nx. You can always reduce nx if you want finer st...

Philippe,

The reason that happens in Pelegant is that the master processor is "non-working." It handles coordination among the slave processors, but (usually), doesn't do anything related to particle generation or tracking.

I'll add a check to the code for this problem.

--Michael

Philippe, This command ~borland/improv/beta/Pelegant_2023.4 tracktest.ele > pElegantMichael.output looks wrong. Are you using mpiexec to invoke Pelegant? E.g., to run with 8 cores you'd use mpiexec -np 8 Pelegant ... It shouldn't be possible to run it any other way, but it is behaving as if it is us...

The problem is a typo in the definition of the quadrupoles. You have a spurious quotation mark at the end of the lines containing FSE values. This confuses the parser and it ignores the rest of the element definition.

--Michael