ELOG E142

Carsten, Rodolfo, Sarper, Patrick

Change in LV code

We changed the LV code so that the Cobra Set Wavelength is permanently sent. Before it was only sent once at the beginning of each laser step. This, however, lead to too much data for the LV->MBS server.
This was fixed by inserting a 250 ms wait in LV (in Krypton data VI). Basically, all LV values are now updated every 250 ms, which works fine with MBS

185

Sat Apr 9 15:47:21 2022

Afternoon and night shift runs

After the morning shift, we got new increment (nm) for the laser scanning. We are now scanning 2 nm of wavelength range in 5 big steps (5 x 0.4 nm). Started with 323.2 nm - 322.8 nm range. Every big step (0.4 nm) is scanned with 0.002 nm of wavelength increment.

Every scan takes ~ 18 min (0.4 nm range with 0.002 nm steps), we have scanned 2 loops. Total scanning time ~36 min.

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

Schottky marker pos: 243.973MHz

Time	SIS-intensity	cooler-HV	LMD-DAQ1 start-end	LMD-DAQ2 start-end	scan range(nm)	step width(nm)	dwell time(s)	comments
xx:xx	x.xe9	209xxx	0xxx	78xx	32x.x - 32x.x	0.002	x	sketch for filling the table
15:14	1.5e9	209624	0111-0111	7847-7847	323.2 - 322.8	0.002	5s	DAQ 2 no VUPROM TDC Pat south
xx:xx	1.5e9	209624	0111-0111	7847-7847	323.2 - 322.8	0.002	5s	DAQ 2 changed TDC part south from ch 8 to ch 10
17:05	2.2e9	209624	0113-0113	7848-7848	323.2 - 322.8	0.002	5s	successful scan
19:04	1.8e9	209616	0116-0116	7850-7850	323.2 - 322.8	0.002	5s	Intensity optimization, see below, DAQ 2 TDC part south back to channel 8 - ok, XUV detector and Cu mirror moved correctly, lost the laser beam after the half of the second loop
19:49	1.8e9	209614	0117-0117	7851-7851	323.2 - 322.8	0.002	5s	successful scan
20:28	2.0e9	209622	0118-0118	7852-7852	323.2 - 322.8	0.002	5s	successful scan
21:07	2.2e9	209623	0119-119	7853-7853	323.2 - 322.8	0.002	5s	successful scan
22:01	1.8e9	209621	0122-0122	7856-7856	323.2 - 322.8	0.002	5s	successful scan
22:41	?	209620	0123	7857	323.2 - 322.8	0.002	5s	First scan started by night shift
23:21	1.1e9	209620	0124	7858	323.2 - 322.8	0.002	5s	mbs crashed at 'sta ac'
23:32	1.3e9	209618	0125	7859	323.2 - 322.8	0.002	5s	e-cooler turned off
23:50	1.5e9	209xxx	0126	7860	323.2 - 322.8	0.002	5s	the stop point was not set
23:53	1.5e9	209611	0127	7861	323.2 - 322.8	0.002	5s	DAQ2 must have crashed between 23:30 - 23:50
00:07	1.9e9	209xxx	0128	7862	323.2 - 322.8	0.002	5s	mbs crashed at 'sta ac'
00:23	1.7e9	209623	0131	7864	323.2 - 322.8	0.002	5s	successful scan. we 'resl' after every measurement from now on. 'open file' is included in '@startup' now (ID:190).
01:08	1.6e9	209623	0132	7865	323.2 - 322.8	0.002	5s	successful scan
01:47	1.6e9	209623	0133	7866	323.2 - 322.8	0.002	5s	successful scan
02:35	1.3e9	209623	0134	7868	323.2 - 322.8	0.002	5s	successful scan
03:19	2.0e9	209622	0135	7869	323.2 - 322.8	0.002	5s	successful scan
04:04	1.3e9	209622	0136	7870	323.2 - 322.8	0.002	5s	successful scan
04:44	1.0e9	209622	0137	7871	323.2 - 322.8	0.002	5s	e-cooler turned off
05:25	1.9e9	209622	0140	7875	323.2 - 322.8	0.002	5s	successful scan. DAQ1 was started ~7s before DAQ2. The files between the last measurement an this one are essentially empty.

Carsten (19:00h): I notized that a lot of beam gets lost when starting scraping. I called Sergey Litvinov to help me to introduce some additional cooling/waiting (10s) after the ramp and before scraping and bunching. It increased the number of ions available for the measurement roughly by a factor of 3-5.

Some runs have wrong WM data. Set Wavelength is good.

Following files are saved differently, the command missed the 229Th in the end (/data.local2/BeamTimeTh22/229Thor -auto -rfio)
7850 (19:32)
7855 (21:56)
7856 (22:30)

186

Sat Apr 9 16:55:19 2022

Rodolfo

16:15 I have changed the dye (of both oscillator and amplifier).

16:27 I have increased the pump energy (@ 532 nm) from 476 mJ to 507 mJ.

- UV output energy @ 322,8 nm: 12 mJ. (Before was at 9 mJ).

- New calibration factor is 160 for Quanta Ray monitor signal.

188

Sat Apr 9 19:09:57 2022

Rodolfo

Optimization - Resonator of dye laser

I have tuned a bit the resonator of the dye laser.

The total output energy after the main amplifier is 86 mJ (@ 645,6 nm)

The laser wavelength read by the wavemeter appears to be more stable (on the windows computer). We can see the histogram once the present scanning is finished.

189

Sat Apr 9 19:50:40 2022

Carsten

New thresholds for ADC of DAQ2 (starting with file0117)

unsigned short caen_V785AH_threshold_mod0 [32] = 
                {0x0100 , 0x0004 , 0x0003 , 0x0004 , 0x0005 , 0x0004 , 0x0006 , 0x0005 ,
                 0x0006 , 0x0005 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 ,
                 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 ,
                 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 };

190

Sun Apr 10 02:20:17 2022

New mbs startup guide

Connecting to the rfio server and opening a file is included in '@startup' now. Since mbs crashes reliably every 3 or 4 runs, it may be preferable to use the following procedure (which did not crash yet):

	DAQ1	DAQ2
1	ssh atplaser@r4l-41	ssh stoe_exp@r4l-68
2	ThE142_2022	see ID:179
3	cd mbsrun/th22	cd mbsrun/th22cd /esr/usr/stoe_exp/E142Brandau/SCA... (auto complete with tab)
// loop start
4	resl	resl
5	mbs	mbs
6	@startup	@startup
7	// connect go4	// connect go4
8	sta ac	sta ac
9	// measure	// measure
10	sto ac	sto ac
11	clo fi	clo fi
12	exit	exit
13	// disconnect go4	// disconnect go4
14	// go to step 4	// go to step 4

Note: At least in DAQ1, step 13 is necessary to be able to reconnect mbs to the rfio server.

191

Sun Apr 10 03:56:56 2022

V. Hannen

Detectors

Low rate in PMT South

PMT south shows a much lower count rate than observed in elog entry 170.

Yesterday the voltage on this PMT was increased to 2400 V and the threshold setting of the CAEN CFD to 90 units, (from 70 units before) however the low readout rate was already apparent both for the analog and the discriminated signal then.

Update Sun Apr 10, 21:45: on advice from D. Winters, increased the PMT voltage to 2500 V (max. the HV supply can do, the PMT could handle up to 3000 V)

Attachment 1: 2022-04-10_PMTs_over_wavel-03_56.png

192

Sun Apr 10 04:07:53 2022

go4 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

Attachment 2: 2022-04-10_measured_wavel2.png

Attachment 3: 2022-04-10_measured_wavel_go4.png

193

Sun Apr 10 04:37:29 2022

Next wavelength range

Measurements with the next wavelength scan range should be started roughly around 12:00 noon. The plan is to go to lower wavelengths / higher energies.
So the next wavelength scan range would be 322.81 - 322.4 nm, again with a step size of 0.002 nm and 5s dwell time.

In the picture below you find some calculations/estimates for the current scan range.

Attachment 1: 2022-04-10_calculations_323nm.jpg

194

Sun Apr 10 06:34:49 2022

Wavemeter Readout

Problem solved. Ignore this entry








If the wavemeter reading is not shown correctly in Go4 - Step2 - Labview:

Close Labview, close WM software (all windows)

Start WM software, start Labview, restart MBS

195

Sun Apr 10 06:39:16 2022

Kristian, Marek, Max

runs morning shift 10.04.

These are the measurement runs of the morning shift (10.04.).

Time

SIS-intensity

cooler-HV

LMD-DAQ1 start-end

LMD-DAQ2 start-end

scan range(nm)

step width(nm)

dwell time(s)

comments

06:xx

3e8

2096xx

0141-0141

7876-7876

323.2 - 322.8

0.002

just one loop

06:39

2e9

209621

0142-0142

7877-7877

323.2 - 322.8

0.002

07:18

2.1e9

209616

0143-0143

7878-7878

323.2 - 322.8

0.002

8000 particles on counter

07:57

2.2e9

209621

0144-0144

7879-7879

323.2 - 322.8

0.002

08:37

1.9e9

209620

0145-0145

7880-7880

323.2 - 322.8

0.002

7200 particles on counter

09:24

2.1e9

209621

0146-0146

7881-7881

323.2 - 322.8

0.002

laser pulse energy @ start of run: 488mJ green monitor, 11.6mJ UV, 7700 particles on counte

10:07

2.1e9

209620

0147-0147

7882-7882

323.2 - 322.8

0.002

optimized WM coupling, the WM data is stretched in this run (buffer problem?), also possible for previous runs

11:04

2.1e9

209620

0148-0148

7884-7884

323.2 - 322.8

0.002

restarted WM, still wrong WM data, stopped after 1 run

11:27

2.1e9

209616

0149-0149

7885-7885

323.2 - 322.8

0.002

restarted WM + LV

12:11

2.0e9

209616

0150-0150

7886-7886

323.2 - 322.8

0.002

wrong WM data

12:55

1.9e9

209616

0151-0151

7887-7887

323.2 - 322.8

0.002

changed LV code (ID: 198), WM data works now!

13:37

1.8e9

209620

0152-0152

7888-7888

323.2 - 322.8

0.002

14:16

2.1e9

209621

0153-0153

7889-7889

323.2 - 322.8

0.002

1 loop

196

Sun Apr 10 08:53:26 2022

Timing verified

timing is still good.

we checked the relative timing between laser and ions. the time difference between photodiodes, PMTs and particle detectors is still the same as original (see ELOG ID 169). The common stop of changed a slightly so that everything appears one bin later.

197

Sun Apr 10 11:11:18 2022

additional WM readout

since the WM readout still does not work reliably, I started a python script at atppc023 that saves timestamp and wavemeter frequency. in folder wavemeter at the desktop. 

it is about 1 MB / h

Rename the old file and restart when you change the wavelength range.

198

Sun Apr 10 13:17:53 2022

Wavemeter readout

We changed the Labview code in order to reduce the amount of data that was overfilling the WM data queue. We removed the temperature and intensity values and added an additional 250ms wait.

We have the same wait in the Krypton VI and believed that it also slowed down the WM reading but this was obviously not the case.

Everything seems to work fine now!

Starting with the .lmd files 0151 / 7887 also the WM reading values are correct

199

Sun Apr 10 15:08:42 2022

Carsten

Backup of Data from 1rst Scanrange to extrenal RAID1 HDDs

I just performed a backup of all data (+log-Files) that were collected until now to the two RAID HDDs.

For DAQ1: /media/sdc2 - last file 229Thor7889.lmd. Please note, that the naming sceme on DAQ1 is inconsistent - please look for the filenumnbering
For DAQ2: /media/sdd2 - last file 229Th0153.lmd

200

Sun Apr 10 15:16:19 2022

Carsten, Rodolfo, Sarper

Runs afternoon shifts 10.04

These are the measurement runs of the afternoon shift (10.04.).

Wavelength range is changed from 323.2 - 322.8 nm to 322.81 - 322.40 nm.

Time

SIS-intensity

cooler-HV

LMD-DAQ1 start-end

LMD-DAQ2 start-end

scan range(nm)

step width(nm)

dwell time(s)

comments

16:26

1.95e9

209620

0155-0155

7891-7891

322.81 - 322.40

0.002

laser scan did not work, labview (Thorium_main.vi) communication issue

16:51

1.8e9

209620

0156-0156

7892-7892

322.81 - 322.40

0.002

17:33

1.6e9

209618

0157-0157

7893-7893

322.81 - 322.40

0.002

7894 particles on the counter

18:17

1.6e9

209618

0158-0158

7894-7894

322.81 - 322.40

0.002

8200 particles on the counter

19:06

1.8e9

209618

0159-0159

7895-7895

322.81 - 322.40

0.002

8650 particles on the counter

19:44

1.9e9

209618

0160-0160

7896-7896

322.81 - 322.40

0.002

8600 particles on the counter

20:24

1.7e9

209620

0161-0161

7897-7897

322.81 - 322.40

0.002

4200 particles on the counter

21:04

1.7e9

209619

0162-0162

7898-7898

322.81 - 322.40

0.002

8380 particles on the counter

21:45

1.8e9

209619

0163-0163

7899-7899

322.81 - 322.40

0.002

8550 particles on the counter

22:24

1.8e9

209619

0164-0164

7900-7900

322.81 - 322.40

0.002

8016 particles on the counter

201

Sun Apr 10 15:29:37 2022

Carsten,Sarper

Accelerator

Ecooler failed

Ecooler failed @15:23 Carsten is fixing it
Fixed @16:00

202

Sun Apr 10 15:29:53 2022

Rodolfo

Patrick, Volker, Prannay, Danyal, Alexandre, Sebastian, Kristian

Status - Laser system

We have checked the laser system.

- The pump laser has ~ 23Mio shots. The total output energy has dropped to about 475 mJ. Maybe it is time to install new fresh flashlamps. In case the accelerator is going to have any mantainance tomorrow (Monday) then we can take the oportunity to exchange the flashlaps.
- The dye laser is pumped with 470 mJ (angle of lambda/2 plate = 112°).
- The energy after the second harmonic is 11,3 mJ @ 646 nm. We are using the Sarper's calibration table (635 nm - 646 nm)

203

Sun Apr 10 22:47:05 2022

Runs night shift 10.04 + morning shift 11.04

These are the measurement runs of the night shift (10/11.04.).

Wavelength range is still 322.81 - 322.40 nm.

Time	SIS-intensity	cooler-HV	LMD-DAQ1 start-end	LMD-DAQ2 start-end	scan range(nm)	step width(nm)	dwell time(s)	particles counted	comments
23:05	1.75e9	209620	0165 - 0165	7901-7901	322.81 - 322.40	0.002	5s	8500
23:57	1.?e9	209620	0166 - 0166	7902-7902	322.81 - 322.40	0.002	5s	8500	The HV of PMT south was changed from 2.5kV to 3kV
00:35	1.4e9	209620	0167 - 0167	7903-7903	322.81 - 322.40	0.002	5s	4100
01:18	1.75e9	209620	0168 - 0168	7904-7904	322.81 - 322.40	0.002	5s	4400
01:58	1.4e9	209620	0169 - 0169	7905-7905	322.81 - 322.40	0.002	5s	7700	The ESR went red after this run. The on-call service was called because of some power supply failure, ETA: 45min.
04:12	1.75e9	209620	0171 - 0171	7906-7906	322.81 - 322.40	0.002	5s	7600	With the start of this run, the wavemeter, labview and the python script were restarted. The python script was slightly adjusted.
04:50	1.6e9	209620	0172 - 0172	7907-7907	322.81 - 322.40	0.002	5s	8300
05:31	1.6e9	209619	0173 - 0173	7908-7908	322.81 - 322.40	0.002	5s	8100
06:09	1.6e9	209615	0174 - 0174	7909-7909	322.81 - 322.40	0.002	5s	8000
06:52	1.8e9	209615	0175 - 0175	7910-7910	322.81 - 322.40	0.002	5s	8800	at 07:08 the cooler voltage jumped from 209615 V to 209619 V
07:30	1.9e9	209619	0176 - 0176	7911-7911	322.81 - 322.40	0.002	5s	forgotten	at 07:50 the cooler voltage jumped from 209619 to 209610 V and back again at to 209619 V
08:18	1.8e9	209619	0177 - 0177	7912-7912	322.81 - 322.40	0.002	5s	9100	08:47 the cooler voltage jumped from 209618 to 209614 V and back again at to 209618 V
08:55	1.75e9	209619	0178 - 0178	7913-7913	322.81 - 322.40	0.002	5s	8300
09:36	1.6e9	209619	0179 - 0179	7914-7914	322.81 - 322.40	0.002	5s	8194

The SIS intensity is taken directly before injection to ESR. Not the SIS peak intensity as in yesterday's table.

204

Mon Apr 11 04:26:53 2022