20
Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

Embed Size (px)

Citation preview

Page 1: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

Beam StudiesDecember 2014

Runs: 7820 – 7860

December 27, 2014

Page 2: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

2

Outline

• FADC and TDC Data Synchronization:– Mott_SemiInt Mode: good (only one run was taken – 7860)– Mott_Sample Mode: TDC data is off by one event (except first

four runs: 7820, 7821, 7822, and 7823*)

* After Run 7823, TDC stop signal offset (NIM740) was adjusted before going to DISC (NIM708) but nothing obvious on scope

• Beam Rep = 31 MHz (C Laser)• Beam Rep = 62 MHz (C Laser)• Beam Rep = 499 MHz (A Laser)• Background

Page 3: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

3

Mott_SemiInt – Run 7860

Page 4: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

4

Mott_Sample – Run 7673

TDC Shift =0

TDC Shift =1

TDC Shift =2

Run from May 2014

Page 5: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

5

Extra TDC stripes because four

detectors have slightly different

time offsets

Page 6: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

6

Mott_Sample – Run 7859 – 31 MHz

TDC Shift =0

TDC Shift =1

TDC Shift =2

TDC is off by one event

Page 7: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

7

Run 7858 – Thru Hole TDC Shift =1

Page 8: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

8

Run 7824 – 62 MHz TDC Shift =1

Page 9: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

9

Run 7839 – 499 MHz TDC Shift =1

Page 10: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

10

Solution

• B. Moffit thinks it's possible that loss of synchronization was actually coming from fadc250, instead of TDC.

• With prescription that was in current readout-lists may have left data on fadc250 that was not cleared before next run.

• This would explain why changing configuration, or resetting and downloading again would clear it up.

• Added a faClear(..) into start-of-run to see if this should help.

Page 11: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

11

Background

• Rep Rate = 499 MHz (A Laser):– Runs: 7821, 7822, 7833-7838 → yes background– Runs: 7839-7850, 7852-7858 → no background

• Rep Rate = 62 MHz (C Laser):– Runs: 7820, 7823-7829 → yes background– Run: 7824* → no background * C Laser, amp=2.0W, A-slit = 60mm

• Rep Rate = 31 MHz (C Laser):– Runs: 7831, 7832, 7833 → yes background– Runs: 7851, 7858, 7859 → no background

All runs before 7839

(except for Run 7824) have background

Page 12: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

12

BPM0L02 x-positionBefore Run

7839, BPM0L02X was changed from

1.5 to -4.5 mm

Page 13: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

13

Beam Current

Page 14: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

14

Mott Events

Page 15: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

15

Detector Events

Page 16: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

16

E Events

Page 17: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

17

dE Events

Page 18: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

18

Run 7838 – 499 MHz TDC Shift =1

Page 19: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

19

Run 7830 – 31 MHz TDC Shift =1

Background events from beam scraping apertures upstream of target

Page 20: Beam Studies December 2014 Runs: 7820 – 7860 December 27, 2014

20

Run 7825 – 62 MHz TDC Shift =1