momentum scan

[amereghe]

Few specs:

• make dpini variable with an internal (to SixDesk) loop --> kind of DA scan with dpini as parameter: will always scan amplitude/angles, no matter the value of dpini;
• no need of one-turn jobs;
• track folder:
  • if dpini has only one value, no explicit name in track dir structure (kind of backward compatibility);
  • if dpini is scanned, put point in momentum scan before amplitude variations in track dir structure;

Get synchronised with sixdb

[amereghe]

From some fort.10 sample results, particle dp seems to either increase or decrease monotonically, with variations at the 9th digit after the comma (exp notation) -> numerical noise in RF motion?

[amereghe]

Actually, column 9 in fort.10 echoes the initial relative momentum off-set of the particle, as before adding the closed orbit.

A bit of workflow:

• daten :
  • values of delta are stored in exz(1,6) and exz(2,6) ;
  • dp1 is set equal to exz(1,6) ;
• main :
  • dp00 , dp0 and dp10 are set to dp1;
  • dpsv(ib2) is set to dp10 (ib2 loops over napx);
  • dpsv(i3) is set to dpsv(ia)*sqrt(bet0s1)+tas(ia,ii,jj)*x1(jj) (where ia is the index of the first coupled particle, ii is 6, jj loops between 1 and 6, and i3 actually loops over napx via a more intricated loop);

Hence, only the value of dp of the first particle in the INIT block matters, and it does the actual job!