Trafo was set to 0

Beam is back; It is now being optimized

All quadrupoles went off, waiting for the on-call service

Maybe, our degrader in FRS was removed by hand at (~13:40 26/05/21)
It is put back now (~13:10 27/05/21)
All runs taken in this period have to be double checked!

However, the xray lines from this night show Te for k_alpha and K-KREC

It is also possible that the readout of this degrader motor was just wrong due to its state as hand-controlled.

By checking the log files we realized that from yesterday 26.05. 13:44 - today 13:05 the FRS degrader was shown as out.
TS3ET7US should be at -420.0mm not at -580mm (=out). This 3.26mm Sci is used as a degrader and is essential.

After recognizing we set the drive controller back to remote and moved the degrader to -420mm (at 13:02)
The wrong values start on 26.05. at 13:44 and show variation until 16:11 until over night it was always shown as out.

It was tested today (~14h) that if you really move it out no beam is injected into ESR, but beam and even Te was observed in ESR last night.

The drive controller was in manual mode and it may not have given correct updates.
But it was also tested today that drives on the same crate get updates even in manual mode (at ~16h with TS1DG5_S and TS3ED7DS).

We also checked graylog. No drive command was issued yesterday in this time period, whereas the drive commands for testing today can be clearly seen.
Yesterday other drives in S4 area on the same controller were tested. This is most likely the reason for the manual mode.

The p,n channel opening for the 111Sn+p reaction is at 5.8895 MeV/u beam energy. Therefore, when choosing as 6MeV/u, 7MeV/u, 8MeV/u beam energies, there is not much kinetic energy left for the outgoing neutron --> there are "less" nuclear levels populated above groundstate in 111Sb, they can be handled explicitly. My simulations are based on TALYS results. The following steps did I made:

1, choose an energy for the 111Sn beam. for this example let it be 8AMeV. 

after 9hours of measurement we see only 19 counts on our targetON silicon detector histo. this low count rate can indicate two scenarios:
-we have a mismatch between the beam and the target (not much if any overlap)
-mabye the very low intersity of the beam (we cannot really monitor this, there are only estimates...)

Which tells us that we dont intersect with the target, that on the Xray spectras we dont see any peaks at 90 and 145 angles. There are two peaks in 35 angle, but they are maybe only from Pb conversion 75keV, etc...

now with the MCP we can see clearly the effect of the target :) (scintillation?)
so we want to scan through the target thickness with the beam and choose the best position afterwards.

We are making 3shoots for each bumb position (we change the bumb to make the intersection between beam and target) starting at ~14:

the data will be saved at the lxg1299 data.local2/hillenbrand/Laszlo folder

We got 30 counts out of this afternoon 118Te run on our Si TargetON histo.
That 1 count at bin (6,10) I dont understand.

Now i can see peaks both at the 35 and 90 angle Xray spectra but not much on the 145 one.
At the end the target density stayed at 8.6E13.

there was a drop again from 8.6e13 to 7e13 in the target density

We filled the Xray detectors.
Yuri is sill tuning FRS for primary beam.