Shift

http://atf.kek.jp/twiki/bin/view/ATFlogbook/Log20130409d

http://atf.kek.jp/twiki/bin/view/ATFlogbook/Log20130409s

present: Alexey, Jochem, Young-Im, Stewart (remotely)

Checkout and tune

There is no ipbpm reference x signal, need to check it in the tunnel

Tune all references

- C-band reference tune : parameter upload falied

- S-band/IPBPM reference tune : fine

- MFB2FF : Mover is moving but signals are super saturated (only moved less than +- 1mm range)

* IP Area

Tuning : 10000 ADC counts is good for tuning

PreIP (x,y) both tune : don't work, tried to increase ADC counts and number of pulses but don't work.

** Suggestion : ATF2 Orbit FB ON for tuning then off for the calibraion

Calibration

3:18 Calibration start from QM16FF

QM16FF calibration was done at 0.3-0.4 x 10^10 then Kubo-san came and try to increase beam intensity.]

QD10BFF position scale factor (old scale) for x and y are -105.9616 and -115.9470. 10 times smaller??

Intensity at EXT is ~ 0.56 x 10^10, calibration QM15FF.

Intensity at EXT is ~ 0.85 x 10^10, calibration start from QM14FF.

* QM13FFx calibration falied to upload scale and I-Q rotation due to mover moved 4 steps. Do it again.

QD10BFF has unexpectedly no attenuator. new position scales again 10 times smaller.

We don't manage to get low amplitude for proper calibration in y (partly saturated), but calibration looks good.

QF9AFF svd calibration uploaded position scale with opposite sign as screen output!! to be checked later, actually all the BPM scale factors are negative.

Unrelated, svd calibration gives an error "iqCalibrationStepAverage returned not an error" (possible due to low number of pulses (5*20)? )

19:15 charge down to EXT ~ 0.40 x 10^10.

20:30 charge up to EXT 0.7

20:52 QD2AFF y pos scale to 9200?! redo calibration, same result

file names:

bpmAllLog_20130409_205224.dat.gz

bpmMoverCalibration_20130409_205235.dat.gz

bpmAllMoverCalibration_20130409_205235.dat.gz

2nd calibration:

bpmAllLog_20130409_205727.dat.gz

bpmMoverCalibration_20130409_205738.dat.gz

bpmAllMoverCalibration_20130409_205738.dat.gz

22:35

QF21X-y create bump with ZV11X and ZV1FF to steer through the center of BPM

But after that QF21X-y bump calibration didn't go well (2 times)

file names:

bpmFsBumpCalibration_20130409_223442.dat.gz

bpmFsBumpCalibration_20130409_223700.dat.gz

22:40

trying to save bpm constants:

ERROR When saving cal constants: error in ../transport.c, line 721: logic error in real to string

bpmCasr>
Bpm.Casr.init
Bpm.Casr.save
filename="../transport.c" line number=721
logic error in real to string
filename="../transport.c" line number=721
logic error in real to string
filename="../transport.c" line number=721
logic error in real to string
filename="../transport.c" line number=721
logic error in real to string

22:45

Before moving to IP region trying to improve orbit a little bit

First with Flight Simulator, nice orbit in EXT but not in FF. Going back to saved constants.

Then try manual orbit steering, not much better

23:45

bump calibration IPA, IPB, POSTIP

IPA-x, IPA-y both fail, in processing (BPMBumpCalFS.py:92; polynomial.py: "expected non-empty vector in x"). Data is recorded:

IPA-x

bpmFsBumpCalibration_20130409_234213.dat.gz

IPA-y

bpmFsBumpCalibration_20130409_234514.dat.gz

IPB-x

bpmFsBumpCalibration_20130409_234807.dat.gz

IPB-y

bpmFsBumpCalibration_20130409_235150.dat.gz

Bump Calibration Traceback:

Calculations:BumpCalibration:__init__>  IPB 43 y
Traceback (most recent call last):
  File "./bpmFsBumpCal.py", line 92, in ?
    main()
  File "./bpmFsBumpCal.py", line 54, in main
    fsbc = Calculations.BumpCalibration(dfn)
  File "Calculations.py", line 2218, in __init__
    self.iqc = iqCalibrationStepAverage(self.ra,self.a,self.i,self.q,self.pos,npulse, refampcut = 250)
  File "Calculations.py", line 2450, in __init__
    self.calculate()
  File "Calculations.py", line 2507, in calculate
    self.iqrf  = pl.polyfit(self.icut,self.qcut,1)
  File "/usr/lib/python2.4/site-packages/numpy/lib/polynomial.py", line 486, in polyfit
    raise TypeError, "expected non-empty vector for x"
TypeError: expected non-empty vector for x

00:15 try MQF21-y again. seems in better position. working this time.

summary: except for IPA, IPB, PRE-IP all BPMs calibrated

Resolution studies

00:25

500 pulses saved at different intensity settings for resolution measurements:

01:10 software bug fixed, IPA-y IPB-y calibrated.

01:40 software bug fixed, PRE-IP and POST-IP retuned and calibrated

all except IPA-x and IPB-x calibrated.

constants saved: bpmCasr_20130410_015119.dat

short discussion to decide what to do in last hour: fix IP-REFX or do 2d resolution scan. decided for 2d resolution scan.

Resolution analysis after the calibration

bpmAllLog_20130410_020251.dat.gz

res20130410.pdf

xOrbit20130410.pdf

yOrbit20130410.pdf

resvsoffset20130411.pdf

02:00 2d resolution scans

SD4FF (fast mover, magnet off), x position changed from -250 to +250 in 5 steps, y-calibration from -250 to +250 in 5 steps at each step with 100 points per position.

02:35 2d resolution scan with QM16FF (no attenuator)

QM16FF, x position changed from -1000 to 1000 in 5 steps, y-calibration from -250 to +250 in 5 steps with 100 points per step.

Post-shift resolution data

bpmAllLog_20130411_001229.dat.gz
bpmAllLog_20130411_075751.dat.gz
bpmAllLog_20130411_112347.dat.gz

res20130411.pdf

xOrbit20130411.pdf

yOrbit20130411.pdf

bpmAllLog_20130411_131859.dat.gz

• bpmAllLog_20130411_131859_orbit.pdf: bpmAllLog_20130411_131859_orbit.pdf

• bpmAllLog_20130411_131859_jitter.pdf: bpmAllLog_20130411_131859_jitter.pdf

• bpmAllLog_20130411_131859_resolution.pdf: bpmAllLog_20130411_131859_resolution.pdf

• bpmAllLog_20130411_131859_orbit.png:
  

• bpmAllLog_20130411_131859_jitter.png:
  

• bpmAllLog_20130411_131859_resolution.png:
  
• QM15FF x and y, QM14FF x, FB2FF X and y, QM13FF x and y : super saturated

• bpmAllLog_20130411_160933_orbit.pdf: bpmAllLog_20130411_160933_orbit.pdf

• bpmAllLog_20130411_160933_orbit.png:
  

• bpmAllLog_20130411_160933_jitter.pdf: bpmAllLog_20130411_160933_jitter.pdf

• bpmAllLog_20130411_160933_jitter.png:
  

• bpmAllLog_20130411_160933_resolution.pdf: bpmAllLog_20130411_160933_resolution.pdf

• bpmAllLog_20130411_160933_resolution.png:
  
• QM13FF y, FB2FF x and y (less saturated than before but still), QD10BFF : saturated. It seems better to make sure orbit is stable, optics is correct (10x1 optics) than move individual bpm or steer orbit.

More resolution data ~0.3e10
bpmAllLog_20130411_183035.dat.gz
bpmAllLog_20130411_194332.dat.gz