HOME ESR EXPERIMENTS LABS etc
E121 E127 E132 E125 E143 laser_cooling_2021 E142 Ê128 E146 E0052 E0018 E0028 E0038
  Nuclear hyperfine mixing in 229Th89+, Page 1 of 12  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Author Category Subjectdown
  162   Fri Apr 8 14:12:57 2022 morning shiftDAQtiming for h=1
The timing for h=1 has been set up 

The time window is now twice as large as before! 
This means that we see the same ion bunch twice. 

(150 bins = 1 turn in the ESR) 

The PMT signal is exactly in between two cycles + the extra flight time (3 bins = 10 ns) from target to PMT north. 
Attachment 1: 2022-04-08_timing_h1_final.png
2022-04-08_timing_h1_final.png
  62   Sat Apr 2 01:27:25 2022 Jan GloriusRunstest runs 02.04.2022
Beam settings:
primary beam 
copper stripper
I_el=300mA
U_el=205.490kV (Ohm_labs)
3.5e7 ions at injection


MSCF/ADC settings: 
ch2 < Mid PMT x10
ch6 < Mid PMT x100
see attachment (setting_e142....) for detailed MSCF settings

Files/Runs [DAQ2]:

------------------new file-----------------
229Th0022.lmd
bunched beam [ESR in manip. at 7]
beam scraped using detector drives
-SA pos: 0
-NA pos: -10
-Ni pos: 40

no corresponding file in DAQ1

------------------new file-----------------
229Th0023.lmd
bunched beam [ESR in manip. at 7]
beam scraped using detector drives
-SA pos: 0
-NA pos: -10
-Ni pos: 40
laser scan active:
- steps: 21
- cycles: 5

file in DAQ1:
...7768.lmd

------------------new file-----------------
229Th0024.lmd
bunched beam [ESR in manip. at 7]
beam scraped using detector drives
-SA pos: out (-127)
-NA pos: -10
-Ni pos: 40
laser scan active:
- steps: 21
- cycles: 5

file in DAQ1:
...7770.lmd

------------------new file-----------------
229Th0025.lmd
bunched beam [ESR in manip. at 7]
beam scraped using detector drives
-SA pos: 0
-NA pos: -10
-Ni pos: 40
laser scan not:

VUPROM -> delay stop trigger ch12 

file in DAQ1:
no file

no laser scan

------------------new file-----------------
229Th0026.lmd
bunched beam [ESR in manip. at 7]
beam scraped using detector drives
-SA pos: 0
-NA pos: -10
-Ni pos: 40
laser scan active:
- steps: 21
- cycles: 5

VUPROM -> delay stop trigger ch12 

file in DAQ1:
...7772.lmd
Attachment 1: setting_e142.1648855568
1648855568
Sat Apr  2 01:26:08 CEST 2022
e127pi:mrcc:mscf2:getGainCommon 15
e127pi:mrcc:mscf2:getShapingTimeCommon 0
e127pi:mrcc:mscf2:getThresholdCommon 200
e127pi:mrcc:mscf2:getPzCommon  255
e127pi:mrcc:mscf2:getGain1     15
e127pi:mrcc:mscf2:getGain2     10
e127pi:mrcc:mscf2:getGain3     15
e127pi:mrcc:mscf2:getGain4     15
e127pi:mrcc:mscf2:getShapingTime1 0
e127pi:mrcc:mscf2:getShapingTime2 0
e127pi:mrcc:mscf2:getShapingTime3 0
e127pi:mrcc:mscf2:getShapingTime4 1
e127pi:mrcc:mscf2:getThreshold1 255
e127pi:mrcc:mscf2:getThreshold2 2
e127pi:mrcc:mscf2:getThreshold3 200
e127pi:mrcc:mscf2:getThreshold4 200
e127pi:mrcc:mscf2:getThreshold5 222
e127pi:mrcc:mscf2:getThreshold6 2
e127pi:mrcc:mscf2:getThreshold7 200
e127pi:mrcc:mscf2:getThreshold8 200
e127pi:mrcc:mscf2:getThreshold9 222
e127pi:mrcc:mscf2:getThreshold10 255
e127pi:mrcc:mscf2:getThreshold11 255
e127pi:mrcc:mscf2:getThreshold12 255
e127pi:mrcc:mscf2:getThreshold13 100
e127pi:mrcc:mscf2:getThreshold14 255
e127pi:mrcc:mscf2:getThreshold15 255
e127pi:mrcc:mscf2:getThreshold16 255
e127pi:mrcc:mscf2:getPz1       100
e127pi:mrcc:mscf2:getPz2       100
e127pi:mrcc:mscf2:getPz3       100
e127pi:mrcc:mscf2:getPz4       100
e127pi:mrcc:mscf2:getPz5       100
e127pi:mrcc:mscf2:getPz6       100
e127pi:mrcc:mscf2:getPz7       100
e127pi:mrcc:mscf2:getPz8       100
e127pi:mrcc:mscf2:getPz9       100
e127pi:mrcc:mscf2:getPz10      100
e127pi:mrcc:mscf2:getPz11      100
e127pi:mrcc:mscf2:getPz12      100
e127pi:mrcc:mscf2:getPz13      100
e127pi:mrcc:mscf2:getPz14      100
e127pi:mrcc:mscf2:getPz15      100
e127pi:mrcc:mscf2:getPz16      100
e127pi:mrcc:mscf2:getSingleChMode 1
e127pi:mrcc:mscf2:getRcMode    1
e127pi:mrcc:mscf2:getAutoPZ    18
e127pi:mrcc:mscf2:getMultiplicityHi 8
e127pi:mrcc:mscf2:getMultiplicityLo 0
e127pi:mrcc:mscf2:getSumTrgThresh 18
e127pi:mrcc:mscf2:getBlrOn     1
e127pi:mrcc:mscf2:getCoincTime 121
e127pi:mrcc:mscf2:getThreshOffset 70
e127pi:mrcc:mscf2:getShaperOffset 35
e127pi:mrcc:mscf2:getBlrThresh 25
e127pi:mrcc:mscf2:getECLDelay  18
  113   Wed Apr 6 18:51:33 2022 Danyal & CarstenAcceleratortarget bump
This afternoon, we found out that Sergey has also implemented a "target bump". 
Although we do not use a target, this bump is still convenient because 
we can move the ion beam such that is passes perfectly through the Cu mirror. 

The setting is -8 mm and 1.3 mrad  (if I am not mistaken) 
We tested the effect on the position of the ion beam using the 
horizontal scrapers at the target: GEEXDS1HA and GEEXDS2HA. 

With the target bump set to "zero" (0 mm and 0 mrad), 
the ion beam passed 6-8 mm to the outside. 
This way, it will e.g. not pass centrally through the slit in the Cu mirror. 


With the target bump set to -8 mm and 1.3 mrad, which is the default setting, the ion beam passed centrally. 
Therefore, we left the target bump like this. 
  105   Wed Apr 6 08:06:02 2022 DanyalDAQstopped NTCAP data acquisition
I stopped the NTCAP data acquisition at 8 AM.

Let's hope that the file contains good data.
  195   Sun Apr 10 06:39:16 2022 Kristian, Marek, MaxRunsruns morning shift 10.04.
These are the measurement runs of the morning shift (10.04.).


TimeSIS-intensitycooler-HVLMD-DAQ1 start-endLMD-DAQ2 start-endscan range(nm)step width(nm)dwell time(s)comments
06:xx3e82096xx0141-01417876-7876323.2 - 322.80.0025sjust one loop
06:392e92096210142-01427877-7877323.2 - 322.80.0025s
07:182.1e92096160143-01437878-7878323.2 - 322.80.0025s 8000 particles on counter
07:572.2e92096210144-01447879-7879323.2 - 322.80.0025s
08:371.9e92096200145-01457880-7880323.2 - 322.80.0025s 7200 particles on counter
09:242.1e92096210146-01467881-7881323.2 - 322.80.0025s laser pulse energy @ start of run: 488mJ green monitor, 11.6mJ UV, 7700 particles on counte
10:072.1e92096200147-01477882-7882323.2 - 322.80.0025s optimized WM coupling, the WM data is stretched in this run (buffer problem?), also possible for previous runs
11:042.1e92096200148-01487884-7884323.2 - 322.80.0025s restarted WM, still wrong WM data, stopped after 1 run
11:272.1e92096160149-01497885-7885323.2 - 322.80.0025s restarted WM + LV
12:112.0e92096160150-01507886-7886323.2 - 322.80.0025s wrong WM data
12:551.9e92096160151-01517887-7887323.2 - 322.80.0025s changed LV code (ID: 198), WM data works now!
13:371.8e92096200152-01527888-7888323.2 - 322.80.0025s
14:162.1e92096210153-01537889-7889323.2 - 322.80.0025s1 loop
  138   Thu Apr 7 14:04:36 2022 Paul IndelicatoGeneralno beam until 17:00
10:10  There is a problem with the UNILAC. 
The repair will take several hours. (4 hrs?) 

14:00  We just enquired about the status and when beam could be back. 
The current estimate is 17:00.

More work on laser aligment is required. 
Estimated time: 1 hour
  216   Tue Apr 12 12:41:20 2022 Alexandre, SebastianAcceleratorno beam in SIS18
  207   Mon Apr 11 10:31:07 2022 Kristian, Sebastian, Alexandre, Danyal, PaulGeneralnew laser wavelength scan range 322.41 - 322.00 nm
new wavelength scan range is 322.41 - 322.00 nm

at 10:31

TimeSIS-intensitycooler-HVLMD-DAQ1 file nr LMD-DAQ2 file nr scan range(nm)step width(nm)dwell time(s)particles countedcomments
10:31 1.75e9 209617 0180 7915 322.41 - 322.00 0.002 5s 2300 ABORT ... no laser ... beam stabilization was off
10:40 xxe9 209617 0181 7916 322.41 - 322.00 0.002 5s xxx ABORT ... laser did not start from 322.41 nm
10:42 xxe9 209615 0182 7917 322.41 - 322.00 0.002 5s xxx ABORT ... laser did not start from 322.41 nm
10:45 2.1e9 209616 0183 7918 322.41 - 322.00 0.002 5s 9236 HV E-cooler fluctuates slowly over 3 V
11:22 1.7e9 209616 0184 7919 322.41 - 322.00 0.002 5s xxx
12:02 2.0e9 209616 0185 7920 322.41 - 322.00 0.002 5s 9660
12:43 1.8e9 209618 0186 7921 322.41 - 322.00 0.002 5s 6533 HV E-cooler jump to ~209700k for ~10 seconds and than back to 209618
13:24 2.0e9 209617 0187 7922 322.41 - 322.00 0.002 5s 9500
14:05 2.0e9 209618 0188 7923 322.41 - 322.00 0.002 5s 9220
  222   Tue Apr 12 21:56:54 2022 Volker, David, Pierre-Michel & Danyal, Alexandre, SebastianGeneralnew laser wavelength scan range 321.62 - 321.10 nm
New wavelength scan range is 321.62 - 321.10 nm. Before the new scan range (compare old scan range in Entry 215) was applied,
the cooler settings were slightly modified. Current was changed from 50 mA to 40 mA, correction voltage was changed from 3943 V to 3948 V. Additionally, the positions
of scraper NA was changed from -10 mm to -8 mm and scraper NI from +10 mm to +8 mm.


TimeSIS-intensitycooler-HVLMD-DAQ2 file nr LMD-DAQ1 file nr scan range(nm)step width(nm)dwell time(s)particles countedcomments
21:57 1.55e9 209621 0226-0227 7962 321.62 - 321.10 0.002 5s 7835
22:54 1.4e9 209612 0228 7963 321.62 - 321.10 0.002 5s 3326 PMT south voltage reduced to 2400 V before run, Threshold now 80, Cooler Voltage changed to 209628 V at 23:19
23:45 2.0e9 209628 0229-0230 7964 321.62 - 321.10 0.002 5s 8560
00:34 1.7e9 209626 0231 7965 321.62 - 321.10 0.002 5s 7169
01:29 1.1e9 209624 0232 7966 321.62 - 321.10 0.002 5s 6412
02:19 1.75e9 209626 0233 7967 321.62 - 321.10 0.002 5s 7590
03:06 1.6e9 209630 0234 7968 321.62 - 321.10 0.002 5s 6329
03:58 1.7e9 209629 0235-0236 7969 321.62 - 321.10 0.002 5s 7710
04:43 1.8e9 209629 0237 7970 321.62 - 321.10 0.002 5s Electron cooler went red @04:48
05:48 1.5e9 209623 0238 7971 321.62 - 321.10 0.002 5s 9420
06:42 1.6e9 209616 0239 7972 321.62 - 321.10 0.002 5s 8250
07:32 1.7e9 209621 0240 7974 321.62 - 321.10 0.002 5s 8840 file 7943 was started accidentally too early and killed
08:22 1.85e9 209622 0241 7975 321.62 - 321.10 0.002 5s ABORTED: laser did not start scanning
08:33 1.90e9 209624 0242-243 7976 321.62 - 321.10 0.002 5s 9955
09:23 1.7e9 209624 0244-0245 7977 321.62 - 321.10 0.002 5s 9021 09:50 Ecooler 12V drop for a few seconds; 9:52 again 12V E-cooler drop
10:12 1.85e9 20962x 0246 7978 321.62 - 321.10 0.002 5s 8067
11:10 1.7e9 209615 0247-248 7979 321.62 - 321.10 0.002 5s 8905
11:59 1.94e9 209612 0249-0250 7980 321.62 - 321.10 0.002 5s 8203 drop in E-cooler voltage of 8V at about 12:16 (before there was a slow increase from .612 to .620)
12:48 2.0e9 209612 0251-0252 7981 321.62 - 321.10 0.002 5s 8018 E-cooler is not very stable (varies between .604 and .613) ; ~13:18 E-Cooler 18V jump to 209622V
13:36 1.7e9 209621 0253 7982 321.62 - 321.10 0.002 5s 8170
Attachment 1: Ecooler12VdropOn13_04_22_9_52am.png
Ecooler12VdropOn13_04_22_9_52am.png
Attachment 2: Ecooler18VEcoolerJumpOn13_04_22_13_18pm.png
Ecooler18VEcoolerJumpOn13_04_22_13_18pm.png
  139   Thu Apr 7 14:13:27 2022 DanyalDetectorsnew PMT south
I have replaced the PMT south (looks at the gas target). 
in the hope that this will produce less dark counts. 
Thus far, the dark countrate is low (few Hz). 

brand: ET enterprises 
type:  2" photomultiplier, 9423B 
High voltage: -2.45 kV  (up to -3.5 kV) 
spectral range: 110 - 230 nm 

The power comes from an additional 2.5 kV supply. 
(I have changed the cable: was CH0 before) 
  181   Sat Apr 9 06:25:22 2022 Max, KristianRunsmorning shift runs
DAQ1: lxg1927:/data.local2/BeamTimeTh22/
DAQ2: lxg0155:/data.local2/E142/
LMD file name DAQ1:229Thor
LMD file name DAQ2:229Th

Shottky marker pos: 243.973MHz

TimeSIS-intensitycooler-HVLMD-DAQ1 start-endLMD-DAQ2 start-endscan range(nm)step width(nm)dwell time(s)comments
xx:xxx.xe9209xxx00xx78xx32x.x - 32x.x0.01xsketch for filling the table
06:401.7e92096190098-00997836323.2 - 321.20.0024slaser pulse energy is @ ~12mJ after SHG
09:351.4e92096240101-01017838-7838323.2 - 322.80.0023sonly 0.5nm range, WM power + coupling tuned to scan range, Konstantin updated LV code to hold Cobra Set WL value, aborted LV readout problem
11:251.0e92096220102 - 1027839-7839323.2 - 322.80.0023sLV readout problem solved. WM readout is wrong (Cobra set is good)
12:15old beam2096220103 - 1037840-7840323.2 - 322.80.0023s WM readout is wrong
12:502.3e92096170104 - 1047841-7841323.2 - 322.80.0023s couldnt open go4 stream view, stopped after one good scan
13:202.0e92096170104 - 1057842-7842323.2 - 322.80.0023s first scan with LV correct
  6   Fri Aug 6 10:40:54 2021 RodolfoDAQmbs in atplaser
The "MBS program" (data acquisition) is now located within atplaser@r4l-41, in the folder "th21":


R4L-41 atplaser > pwd
/esr/usr/atplaser/mbsrun/th21

R4L-41 atplaser > ls -l
total 412
-rw-r--r-- 1 atplaser esr 3326 Jul 21 13:42 #Makefile#
-rw-r--r-- 1 atplaser esr 18675 Jul 19 10:43 #f_user.c.lc21wlv#
-rwxr--r-- 1 atplaser esr 3324 Jul 21 13:17 Makefile
-rw-r--r-- 1 atplaser esr 2803 Jul 13 10:59 Makefile.lynx
-rw-r--r-- 1 atplaser esr 3324 Jul 13 10:59 Makefile.test
drwxr-xr-x 2 atplaser esr 4096 Jul 13 10:59 dump
-rw-r--r-- 1 atplaser esr 8032 Aug 2 13:06 f_user.c
-rw-r--r-- 1 atplaser esr 18673 Jul 14 10:39 f_user.c.lc21wlv
-rw-r--r-- 1 atplaser esr 6368 Jul 21 11:01 f_user.c.lynx
-rwxr--r-- 1 atplaser esr 18843 Jul 23 11:09 f_user_wlvc.c
-rw-r--r-- 1 atplaser esr 49 Jul 13 10:59 filenum.set
-rw-r--r-- 1 atplaser esr 8181 Jul 13 10:59 include
-rwxr-xr-x 1 atplaser esr 162908 Aug 2 13:07 m_read_meb
-rw-rw-rw- 1 atplaser esr 81056 Aug 5 19:07 mbslog.l
drwxr-xr-x 2 atplaser esr 4096 Jul 13 10:59 scom
-rw-r--r-- 1 atplaser esr 13154 Jul 13 10:59 setup.usf
-rw-r--r-- 1 atplaser esr 94 Jul 13 10:59 shutdown.scom
-rw-r--r-- 1 atplaser esr 320 Jul 13 10:59 st.scom
-rw-r--r-- 1 atplaser esr 290 Jul 22 15:23 startup.scom
-rw-r--r-- 1 atplaser esr 525 Jul 13 10:59 startup.scom.lynx
drwxr-xr-x 2 atplaser esr 4096 Jul 13 10:59 suha
-rw-r--r-- 1 atplaser esr 18999 Jul 13 10:59 vuprom_tdc_v5.h


Note: This MBS-Version was used previously by Sebastian in "laser cooling 21".
  225   Thu Apr 14 06:29:18 2022 Max, SebastianAcceleratorlesser ESR injection intensity
We now have less ESR injection intensity (see screenshot attached).

This can also be seen in the count rate after "UNILAC/SIS failures".
Before failure: ~7k-8k
Now: 3k

The stored particles in the SIS are only in the range between 1.4 and 1.7e9 
Attachment 1: 2022_04_14-lowCountRate-LesserESRInjection-SchottkyIntensity.JPG
2022_04_14-lowCountRate-LesserESRInjection-SchottkyIntensity.JPG
  233   Fri Apr 15 12:42:18 2022 Max, Danyal, Carsten, Konstantin, Patrick, SimonGenerallaser wavelength range changed: 320.12 - 319.60 nm

Runs of the morning/afternoon/night shift. The wavelength range is now 320.12 - 319.60 nm.

TimeSIS-intensitycooler-HVLMD-DAQ2 file nr LMD-DAQ1 file nr scan range(nm)step width(nm)dwell time(s)particles countedcomments
12:51 1.2e9 209617 0321 8034 320.12 - 319.60 0.002 5s 5530 ERS Trafo 1.25e7 --> 1.2e9
13:43 1.2e9 209617 0322 8035 320.12 - 319.60 0.002 5s 6408 at 13:49 there was a short broadening of the ion beam in the Schottky spectrum
14:35 1.16e9 209618 0323 8036 320.12 - 319.60 0.002 5s 6585
15:30 1.08e9 209617 0324 8037 320.12 - 319.60 0.002 5s 5701
16:20 1.10e9 209617 0325 8038 320.12 - 319.60 0.002 5s 5470
17:11 1.11e9 209617 0326 8039 320.12 - 319.60 0.002 5s 5519
18:00 1.08e9 209616 0327 8040 320.12 - 319.60 0.002 5s 5402 Ecooler voltage suddenly jumped to 109619 around 18:30. Laser spot seems to drift slowly to an inner position (left on the screen). This might be due to an interplay between a decreasing laser power and the position sensitive detectors of the beam stabilization.
18:52 1.16e9 209620 0328 8041 320.12 - 319.60 0.002 5s 6948
20:39 1.13e9 209619 0329 8042 320.12 - 319.60 0.002 5s 6xxx Dye was changed before this run was started
20:32 1.20e9 209620 0330 8043 320.12 - 319.60 0.002 5s 6948
22:25 1.21e9 209619 0331 8044 320.12 - 319.60 0.002 5s 7120 Night shift took over (Patrick, Simon)
23:15 1.26e9 209619 0332 8045 320.12 - 319.60 0.002 5s 7080
00:06 1.25e9 209616 0333 8046 320.12 - 319.60 0.002 5s 6500
00:59 1.23e9 209616 0334 8047 320.12 - 319.60 0.002 5s 5380
01:50 1.30e9 209616 0335 8048 320.12 - 319.60 0.002 5s 6750
02:41 1.38e9 209616 0336 8049 320.12 - 319.60 0.002 5s 6970
03:32 1.37e9 209616 0337 8050 320.12 - 319.60 0.002 5s 7010
Attachment 1: VoltageJump1830.PNG
VoltageJump1830.PNG
  164   Fri Apr 8 14:43:50 2022 WilfriedDAQlaser timing - Q-switch start
below are my notes concerning laser timing / Q-switch start
Attachment 1: IMG_20220408_143753_resized_20220408_023840170.jpg
IMG_20220408_143753_resized_20220408_023840170.jpg
  165   Fri Apr 8 14:46:02 2022 Danyal & Sebastian & Volker & KenDetectorshigh dark countrate Cu PMT solved
The problem - "discovered" by Volker and Ken - of the high dark countrate of the Cu PMT has been solved. 

(when the Cu mirror was moved in, the dark countrate was very high ... also without ion beam) 

I asked Graziano Savino to check the vacuum gauges along the target side of the ESR (west side). 
The gauges at the laser window sections (which we do not use here!) - NW and SW - were still on. 
Volker remembered that, in the past, for the lowest dark countrate at the Cu PMT --> ALL GAUGES MUST BE SWITCHED OFF. 
Graziano turned them off and Sebastian and I checked the Cu PMT rate in DAQ1. 

Attached you can clearly see the difference: from 7500 cps to 400 cps. 

When the Cu mirror is retracted the dark countrate is 200 cps.  

Danyal

PS The slow increase in one plot is due to the fact that Graziano switched on the light in the ESR. 
Attachment 1: IMG_20220408_082804.jpg
IMG_20220408_082804.jpg
Attachment 2: IMG_20220408_083031.jpg
IMG_20220408_083031.jpg
  192   Sun Apr 10 04:07:53 2022 PatrickDAQgo4 shows wrong frequencies and wavelengths
Update (ID:194): In labview "Stop All", close labview, stop python script (ID:197), close wavemeter. Then restart wavemeter, python script, labview an mbs.

Both labview and the wavemeter software are displaying the scanned wavelength correctly (Fig. 1 & 2), but go4 shows something which looks just like a freely drifting wavelength (Fig. 3).
The Cobra set voltages are displayed correctly.
Attachment 1: 2022-04-10_measured_wavel.png
2022-04-10_measured_wavel.png
Attachment 2: 2022-04-10_measured_wavel2.png
2022-04-10_measured_wavel2.png
Attachment 3: 2022-04-10_measured_wavel_go4.png
2022-04-10_measured_wavel_go4.png
  183   Sat Apr 9 13:45:42 2022 Max, KristianRunsfirst scans with LV problem solved!
This is the first time with LV buffer problem solved (see Elog ID: 184). Before the PMT signals were out of sync with the wavelength data!
We concluded to scan with step sizes of 0.002nm, scan range of 0.5nm (f
nm), dwelltime = 150(5s), loops = 2 (approx.: 30min measurements).

DAQ1: lxg1927:/data.local2/BeamTimeTh22/
DAQ2: lxg0155:/data.local2/E142/
LMD file name DAQ1:229Thor
LMD file name DAQ2:229Th

Shottky marker pos: 243.973MHz

TimeSIS-intensitycooler-HVLMD-DAQ1 start-endLMD-DAQ2 start-endscan range(nm)step width(nm)dwell time(s)comments
11:251.0e92096220102 - 1027839-7839323.2 - 322.80.0023sLV readout problem solved. WM readout is wrong (Cobra set is good)
12:15old beam2096220103 - 1037840-7840323.2 - 322.80.0023s WM readout is wrong
12:502.3e92096170104 - 1047841-7841323.2 - 322.80.0023s couldnt open go4 stream view, stopped after one good scan, WM readout is wrong .
13:202.0e92096170104 - 1057842-7842323.2 - 322.80.0023s first scan with LV correct
13:401.2e92096180106 - 1067843-7843323.2 - 322.80.0023s 3 loops
14:201.5e92096120107 - 1077844-7844323.2 - 322.80.0023s 1 loop


Runs after this have the right cobra set value but propably the wrong WM data until 10.04.22 12:44 (see also ID:198)
  166   Fri Apr 8 15:39:36 2022 allRunsfirst data after timing set up
started taking data again

started at 15:40  
h=1  

file names 
229Th7821 DAQ 1  607 MB
229Th0082 DAQ 2  820 MB 

stopped at 16:25 


The laser was not really properly scanned. 
This was mainly a test run to see if everything was working. 
  136   Thu Apr 7 11:11:31 2022 Max, SebastianLaserdye changed, pulse energy measurements
We changed the dye at 10am.

We increased the pump power for the dye Laser to 480mJ (before 450mJ). New calibration factor is 29 for Quanta Ray monitor signal.

We get now 17mJ UV pulse energy after SHG. Pulse energy before was 14mJ.
ELOG V3.1.5-fc6679b