see subject.

Voltage SA_SZ (capture behind cooler): 1500 V (thin plastic scintillator)
Voltage NA_SZ (capture behind target): 750V (thick plastic, short absorption length)

Voltages and thershholds from thorium run, still to be verified.

The NTCap DAQ computer in the HKR (Schottky logbook) is started, and all preparations for data taking (mounting of NAS etc.) are done.
Parameters for NTCAP DAQ will be adjusted as soon as beam is available. 

The ESR pattern is enhanced compared to the thorium experiment by additional machines that can be  used for cooling/waiting in order to optimize 208Bi yield.
As a consequence, the sub chain numbers (previous: virtuelle Beschleuniger) are changed. The new numbers still have to be dialed in into the devices in the Messhütte and the automatic in/out of the XUV-detector tested-

After a phone call with Wilfried I implemented an offset to all hit channels of the stacked / accumulated spectra where one chekcs the timing peaks.

Therfore, I made a copy of the analysis in 208Bi1 (one "1" at the end). And here, in the file TLdaAnlProc.cxx I added an offset of +70 to the hit channel (variable UInt_t hit, around line 335 /336 of the code).
Pleasse note that I just inlcuded one line with a "magic" number here, since I cannnot test teh compiling and was afraid to introduce an error.

So the lines were

UInt_t hit =tdcSE[i][j];

changed to 

UInt_t hit =tdcSE[i][j];
hit = hit + 70;

Plesaede note that you need to recompile and check and set all conditions for the time-preak window.

So , you now use the analysis in 208Bi1

time = 20:00 

The RF has been adjusted so that it bunches at the correct frequency for 209Bi 

For 208Bi the settings ("frequency mismatch") were: 
-0.102 in SC5 
-0,102 in SC11  


For 209Bi the settings ("frequency mismatch") are (and were yesterday): 
-0.83 in SC5 
-0,83 in SC11  

We deactivated the automation of the XUV detector. It stays out now.

SASZ and NASZ voltages were switched off bevor we went back to 209Bi. Laser beam stabilization turned off.

The "dead" Q-Switch signal was converted 
two times... This explains why in the 
Thorium experiment the Q-Switch signal 
(ch15) was empty. 

First conversion from TTL to NIM in the 
ESR Laserlab and unfortunately the signal 
was plugged in a second Level Adapter as 
TTL in 
the Messhütte and was "again" converted 
into a NIM for DAQ1/2.

Now the Q-Switch is converted from TTL to 
NIM in the ESR Laserlab. The NIM is 
afterwards guided through a Logic Fan 
In/Out to the 2 DAQs. 

I have switched off the XUV detector on 1 June at about 17:00. 
The high voltages of the MCP (in ESR laser lab) were turned off and inside the ESR cave the power supplies (coils and cathode) and the crate were turned off. 
Also the new "control box" for the detector was switched off. 
And I checked (visually) that the XUV detector (and the Cu detector too) were indeed "moved out". 

Danyal

Dear all,

unfortunately, the E128 experiment must now come to an early end. 
The problem(s) with the injection septum are severe and no work around solution (with acceptable risks) could be found. 
Several things were tried, but without hope. 

Many thanks to everybody involved during the preparation time and the shifts during the beamtime. 

Best wishes,

Wilfried

Attached are the MSCF shaper settings applied on Tue May 10 at 22:30.

9:27 XUV-Detector is running again.

-5V cathode, 8A main coil, 2.4A sec.coil
Rate without beam was: 
Park position: ~300Hz 

Pump beneath the detector is now shut down, new rate: <10Hz.

Threshold was adjusted to trigger only on "nice" signals. 

Rate with beam in and laser:
Park position: ~400Hz
147mm: ~1.4kHz
 
with 2e6 ions

During the setup of the ion beam the voltage range of the Keysight DMM was changed from 10V to 1V. Additionally, the name of the high-voltage divider was adjusted (this changes only the filename of the file, which is stored at the local pc decpc003).

1. Create relevant histograms (change of variable MAX_STEP from 10 to 13 and insertion of histogram names "QSWP1MS", "NORTH_GATED" and "MIDDLE_GATED" in the std::string array stepNames.
   Both adaptions were made in TLdaInputDescription.h)
   
   
2. Fill the respective histograms. Changed lines of files TLdaAnlProc.cxx, TLdaAnlProc.h are listed below.
   

XUV-Detector shows up to 100 kHz and, therefore, was turned off.

Timing for the final measurements on 209Bi was determined for the new frequency 1.93777MHz. Peak positions are

PD NO 106
PD SO 141.5
PMT MIDDLE 45 (due to the broad temporal structure difficult to determine)

Center between PDs is 123.75. Difference to PMT MIDDLE is 78.75. This is ~3 bins larger than the half period of 75. 

During the last run, PMT North showed some weird noise.

The PMT was replaced by the deep UV PMT with small aceptance range (100-200nm) but there was still a lot of noise on the output channel in the Messhütte, see attached photo. The intensity of the noise signal was as strong as a normal signal count.

I replaced all cables and used other preamplifier channels. The noise is gone and the baseline is flat now. However, the timing of PMT north will be a bit different now, so we should use PMT middle for the laser/ion overlap as we did before.

Graziano opened the valves for the laser and turned off the vacuum gauges and emergency lights. The background of the UV PMT looks normal (Middle 10 Hz, North 1 Hz) so I think we are fine here.

We recorded files with high wavemeter readout rate and saved it at the atplaser network drive (Q:) - Bismuth - wavemeter folder.

Could be used to calibrate the laser steps. The MBS readout rate is 4 Hz, here 30 Hz, so there are a few more values.

We did not see any signal at PMT North which was the narrowband PMT. Changed it to the old solar blind PMT. Now we see the resonance. It is about 3 times larger as PMT middle, most likely because of the larger window. CFD threshold was set. I also increased the CFD threshold for PMT middle slightly.


HV for  PMT North: 1600 V

Since 13:30 we have no beam in the ESR. There is a problem with the ESR septum.
The magnets department is investigating.

until 15:15 we have measured with I_e = 100 mA (3 loops per file) 
E_cool HV = 225255 V 


after that (at 15:26) we changed to I_e = 200 mA (2 loops per file) 
E_cool HV = 225272 V 

after that (at 17:15) we changed to I_e = 50 mA (first 4 then 6 loops per file) 
E_cool HV = 225247 V 

At 17:15 we changed again the E-cooler current I_e = 50 mA  
(4 laser scan loops per injection) 
E-cool HV = 225248 V 

We overlapped the laser and ion bunch in the time domain. 
Therefore we delayed the bunching HF in order to see the PMT signal between bin 10 and 22. Before the signal Peak was in channel ~145-5 and difficult to gate on.
Afterwards we also have to shift the laser.
The new values are:

PD NO: 77.5
PD SO: 113
Ion bunch: 16.5 

We checked all three signals in the Messhütte. Laser scan and laser step are OK.
The Laser busy signal is for large increments (0.1nm) also fine. For short increments like our usual 0.005nm increment the signal is irregularly.
Likely the laser busy status is too short.

• In between a measurement the scrapers stopped working in the device control. Therefore, we had to go into the electronics room.
  
• Position to scratch charge transferred beam: S1HA at -35.
  
• Beam diameter is roughly 6-7 mm (horizontally) and 4 mm vertically (as opposed to 1-2 mm).
  
• The charge transferred ion beam seems to shift the position of the main beam over time (1cm / 2h) as the main beam "transfers its intensity".
  

It is necessary to start go4 before you start the laser scan. Otherwise you get an offset in the laser Step plots.

We overlapped the laser and ion bunch in the time domain. The delay has to be set on the module above the laser and NOT in the ESR Messhütte!

The values are:

PD NO: 63
PD SO: 98.5
Ion bunch: 150 

The problem at the ESR septum is serious. They have to remove the broken part and try to repair it.
Maybe tomorrow in the morning briefing there will be more information about this.

The night shift will not take place!
The morning shift starts at 9:00 or on further notice!

The PMTs are switched off and the laser also.

To accumulate more data into the opened go4, do not restart MBS, but just

sto ac
clo fi
open file lxg1297:/data.local2/208Bi/208Bi -auto -rfio
sta ac

Note: This does not work, because go4 somehow accumulates ~5 extra laser steps when starting a new scan which results in an x-axis-offset between the runs.

The final timings are (in bins +-1):

PD NO: 103
PD SO: 138
PMT middle: 44
e-cooler = (PD NO + PD SO) / 2: 121
e-cooler - PMT middle: 77
roundtrip / 2: 75
roundtrip / 2 + 10ns: 78

In run 8134 - 8135 PMT North showed a super high background rate. After the scan we checked the signal cables.

Incoming signal was still good until CFD. We changed channel from 2 to 12. New threshold is 36, was 10.

We coupled the laser through a multi-mode fiber into the wavemeter.
With the main amplifier enabled, we got enough power behind the fiber (0.5 - 1.5 mW) to use the wavemeter with 34 ms exposure time (1s / 30Hz to prevent jumps in the wavemeter readout).

Pictures below: 
1: First test scan with 34ms exp. time.
2: Comp. too large laser power (2. scan duoblet) vs. attenuated power (right scan doublet). The latter has less hickups.
3: Laser scan with attenuated power in go4.

The measured frequencies in the first scan step are unstable in any case.

Spikes (rather "second wavelength the laser is regulrarly jumping to") can be removed by adjusting the fiber coupling with the mirrors (change of interference pattern) or the L/2-waveplate (change of coupled power).
However, during (and after) the scan the spikes seem to reappear.

Since we have ions in the ring now, we looked at the PMT thresholds and the widths. In order to do so we looked at the Raw Signal directly before the CFD and its output simultaneously. You can now set the threshold just above the noise. If the threshold is too low you will also see flat lines in the oscilloscope when triggered on the CFD output. New values:

PMT Mitte
---
Width: 200 -> 220 (60ns -> 90ns)
Threshold: 20 -> 5

PMT Nord
---
Width: 200 -> 220 (60ns -> 90ns)
Threshold: 12 -> 10

PMT Süd
---
blind.

> Dear all,
> 
> unfortunately, the E128 experiment must now come to an early end. 
> The problem(s) with the injection septum are severe and no work around solution (with acceptable risks) could be found. 
> Several things were tried, but without hope. 
> 
> Many thanks to everybody involved during the preparation time and the shifts during the beamtime. 
> 
> Best wishes,
> 
> Wilfried

There is beam again in the ESR. The plan is to take beam until tomorrow morning. 

There is no beam in the ESR due to some problem in the UNILAC.

Beam is back in the ESR.

There is no beam in the ESR again.

12:50 Beam is back again in the ring.
12:52-until now Kicker problem in the ESR.

The T-Scrapers at the electron cooler have an issue. They can't be moved in the horizontal direction using the DeviceControl.

Testing the new Wavemeter (HighFinesse, WS6, SN3950) with the QRAY laser light @ 532 nm. Multimode fiber von High Finesse:FC/PC S (Corning, MM, OM2)

It is now possible to stabilize and move the laser with both stages.

The software and hardware settings are attached.
For synchronizing with the laser pulse we use following frequency generator settings:
period: 200us
high: 5V
low: 0V
duty: 50% 

The frequency generator is triggered with the external Q-switch trigger signal, that is in coincidence with the ESR HF.
To use the stabilization one has to use the external and NOT the q-switch mode of the laser. 

We found a "Bug" in the control of the Sirah dye system.

Due that we don't use the FCU and the temperature control unit we could not start the Sirah software without getting numerous errors. 
The fix was to plug in the BBO oven again, move the FCU to "origin", than move to a specific location that the FCU goes in an "idle" mode. 
Than the Sirah software can be started again without getting erros. 

"Laser step complete" and "laser scan complete" are working again.

Problems:
1) Connections were wrong in the Software. 
2) Sometimes the connection to "laser scan complete" was lost (Wackelkontakt).
3) The VI was initialized with the wrong LabJack Channels.

Now:
1) fixed connections in the software.
2) switch to an other "channel" of the LabJack device for "laser scan complete".
3) The channels in the Cobra VI are for...
laser scan complete -> Channel 5
laser step complete -> 6

We definetely should keep an eye and check frequently the signals, that we do not have a lost connection (Wackelkontakt) again of these 2 channels.

Carrier frequency:244MHz
IQ rate: 10M Samples/seconds
Reference level: -25
RF-Attenuation(dB):40
IF-Attenuation(dB):19.9288
Samples/Record:2^18=262144
Records/File:2^12=4096
Masterpath:p:\208Bi\iq\IQ_2022-05-10_17-06-29
           p:\208Bi\sc\IQ_2022-05-10_17-06-29
Free space of hard disk: 34.9TB.

Current status: 
Laser busy signal works correctly (5V if the grating moves, 0V if not) if the laser is operated by the Sirah software.

When the laser is controled by the "Thorium Main VI" the laser busy signal is always 0V.

Solution for a working laser busy / dye out signal was to disable the FCU and set the FCU status to "False" (see attached picture).

Remark: FCU unit will not be used for Bismuth experiment!

I changed the laser step complete cabling from a quad coinc (see attached picture) to a Logic Fan In / Fan out (same as laser scan complete).
The "detour" through the quad coinc yielded to a very short laser step complete signal of ~500ns...

Due to the change it is now ~15µs long and has the same length as the laser scan complete signal (~15µs).

There is still no Beam in the ESR.

The beam is currently at TE3 - between SIS and ESR

The lower limit (to position) of the Cobra control VI has to be one increment smaller.
This means for moving from 601,95 to 601,74 the "to position" has to be 601.735.

We also checked the displayed HV values in Go4 with the shown values of the HV VI.

Both values in go4 and in the VI show the same value and are changing "simultaneously" (depending on the refresh time of go4 and Labview).

new shift started.

We changed PMT north and PMT south and tested them at 1500 V.

Both new PMTs are broadband.

PMT north and middle see between 2 and 7 kHz signal rate with a threshold close to the background noise.
PMT south still has the plastic cap on and is intended to be used as a reference for electro-magnetic disruptions. No signal was seen at 1500 V.
We fixed the signal cable of PMT south to the NIM-crate to get rid of background noise picked up by the cable.

We performed an autocalibration (attached picture 1) of the Keysight 34465A DMM (TUD Keysight).

The position and the "cabling" to the cooler platform was also adjusted (picture 2,3).

In entry 36 one finds an additional PD NO peak around bin 100.
This was caused by signal reflection in the cable.
The problem was solved by adjusting the CFD threshold from 10 to 30.
 

The scaler channel laser scan complete and laser step complete is interchanged in go4. Carsten will fix this on the software side.
Additionally the laser scan complete signal was not there in the first place. After checking the signal on multiple points, the signal was suddenly back in the DAQ.
Possibly there is a bad cable/contact somewhere (on the Labjack?). The signal should be checked in go4 from time to time. 

The resonance in 209Bi has been seen during the night.
Reducing the intensity by a factor~1000, to simulate 208Bi conditions
Running low intensity since ~6:15-6:20
The present intensity is so low that DCCT does not see the beam.
On Schottky the beam is clearly seen as ~30-40 dB over the background.
The real intensity is to be determined from the NTCap, which is running (checked).

The main control room started setting up the Bi beam this morning, but quickly stopped in order to solve some problems around the UNILAC. Therefore we 
should not plan to receive ions earlier than late in the evening on Monday, or probably Tuesday during the day.

The main control room is setting up the SIS for extraction. At the moment there are 2.5E8 particles in the SIS. Later they will check the transport and the devices for the 
ESR injection. The ESR operators might (! no info available) take over later in the evening, but there will definitely be no beam for the experiment before tomorrow morning.

=> the night shift will not take place, unless some laser adjustments need to be done (so far we see no problems)
=> the morning shift does not need to come at 6AM. My guess is that before the morning briefing at 8:30 there will be no news.

The ESR cave is closed again. Talk to the main control room if you need access.

> The main control room is setting up the SIS for extraction. At the moment there are 2.5E8 particles in the SIS. Later they will check the transport 
and the devices for the 
> ESR injection. The ESR operators might (! no info available) take over later in the evening, but there will definitely be no beam for the experiment 
before tomorrow morning.
> 
> => the night shift will not take place, unless some laser adjustments need to be done (so far we see no problems)
> => the morning shift does not need to come at 6AM. My guess is that before the morning briefing at 8:30 there will be no news.
> 
> The ESR cave is closed again. Talk to the main control room if you need access.

Status SIS on Monday evening. ESR setting up starting on Tuesday morning. There is some prospect of getting more ions by setting up multi-multiturn 
injection, however still uncertain.

For some reason the beam was lost in the SIS soon after taking the ESR beam this evening, reason unknown. Solved by sending teh full context to the SIS machine and having 
operators to manually set the voltage of the SIS extraction kicker. Afterwards a slight readjustment of the transfer beamline was necessary:

In the SIS: GTE5 KY1, MU0, QD21, QD22 as well as in the ESR: GE01MU4I (5 -> 6 mrad)

This brought back around 1E7 particle in the ESR after 5 accumulated SIS injections.