Continuing with the measurements of the last shift, also at 300mA. Creating new file, as beam got killed during last run.

[TABLE border="1"]
Time |File | PTB 32 | PTB 33 | Ohmlabs | ESR intensity SC8 | Typical SIS injections | comments |-
8:42 | 42 | 205826 | 205827 | 205820 | 4e5 | 4e8 | opened new file |-
9:07 | 42 | 205826 | 205827 | 205820 | 4e5 | 4e8 |-|-
9:34 | 42 | 205826 | 205827 | 205820 | 3e5 | 4e8 |-|-
9:59 | 42 | 205826 | 205827 | 205820 | 0 | 4e8 | DS3HG went to  position 20.4, killing the beam |-
10:24 | 43 | 205826 | 205827 | 205820 | 3e5 | 4e8 | opened new file |-
10:51 | 43 | 205826 | 205827 | 205820 | 0 | 4e8 | Beam in the ESR got killed again. DS3HG is at normal position though, so we don't know why |-
11:17 | 44 | 205826 | 205827 | 205820 | 0 | 4e8 | opened new file, DS3HG killed the beam again |-
11:41 | 45 | 205826 | 205827 | 205820 | 2e5 | 4e8 | opened new file |-
12:07 | 45 | 205826 | 205827 | 205820 | 0 | 4e8 | DS3HG killed the beam by going too far for just a second and then going to normal position. Maybe that was the reason some previous beams got killed even though when we looked at the scraper it was in the normal position. Stopped measurements so Sergey can maybe fix the issue with the scraper. Slightly adjusting the setpoints of the scraper should fix the problem of it going too far. Last file got closed. |-
[/TABLE]