Elegant users forum

Hello Michael, many thanks for your useful explanation. I wanted to confirm that indeed, the correct_tune ELEGANT command seems to have resolved the issue, at least from a preliminary review of the results I ran on the cluster over the weekend. In line with the use of that command, in addition of th...

Dear Sir, In one of the elegant examples, which is also on this website ( https://www3.aps.anl.gov/forums/elegant/viewtopic.php?f=9&t=88&p=292&hilit=tune+scan#p292 ), a tune scan for best dynamic aperture search is provided. I aim to use it as complementary information to the genetic optimization, w...

Hi Bob, you are absolutely right. I just fixed that and it now works !

thanks again to you both.

regards,

- Faissal

Dear Michael and Bob Many thanks, using the sddsprocess does work indeed. At this stage I can proceed with the work I was doing....on Windows, but I have a final question for "documentational purpose". Since the sddsfluxcurve executable is not present (or, does not seem) in my Unixdistribution, I ha...

Hi soliday In the Unix version (at least, the one installed here), it is not present in the /usr/bin directory, however there is a *.c file in: /dls_sw/prod/tools/RHEL6-x86_64/elegant/32-0-0/src/oag/apps/src/elegant/sddsbrightness/sddsfluxcurve.c also, since sddsfluxcurve takes only the last row of ...

Thanks Michael for your prompt reply. This was definitely helpful. Just a last question: if sddsfluxcurve uses only the last row, how would it work if we want to compute the flux density emitted at a particular location of the lattice? Do I have to "rotate" the lattice in the twiss file? regards, - ...

Dear all, I am using sddsfluxcurve to calculate the angular flux density of several harmonics of an undulator in a non-zero emittance case. I type: sddsfluxcurve VMX.twi out.twi -mode=density -harmonics=7 -method=dejus -electronBeam=current=0.3,coupling=0.03 -undulator=Period=0.022,numberOfPeriods=9...

Dear Michael, The solution suggested makes sense since it's a linac so putting matched=0 removes the issue. But sometimes the above warning message can also occurs in situations when a ring is simulated. It does not necessarily prevent the optimization to go on, but does this message mean that somet...

Many thanks Michael and Bob !

regards,

- Faissal

Dear Michael, thank you for having pointed out the blank to my attention. I did some further trial and errors and managed to make things work, by writing: (inside an *.ele file) &subprocess command = " sddsprocess input.twi output.sdds -match=col,ElementType=\"KQUAD,ElementType=KSEXT,|\" " &end or, ...