ELOG E142

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 3 of 12

Not logged in

Find | Login | Help

Full | Summary | Threaded | Collapse | Expand

228 Entries

Goto page Previous 1, 2, 3, 4 ... 10, 11, 12 Next All

Sun Apr 10 11:11:18 2022, Kristian, Max, Laser, 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.

Sun Apr 10 08:53:26 2022, Kristian, Max, Laser, 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.

Sun Apr 10 06:39:16 2022, Kristian, Marek, Max, Runs, 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

Sun Apr 10 06:34:49 2022, Kristian, Max, DAQ, 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

Sun Apr 10 04:37:29 2022, Patrick, DAQ, 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.

Sun Apr 10 04:07:53 2022, Patrick, DAQ, 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.

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)

Sun Apr 10 02:20:17 2022, Patrick, DAQ, 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.

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 };

Sat Apr 9 19:09:57 2022, Rodolfo, Laser, 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.

Sat Apr 9 16:55:19 2022, Rodolfo, Laser,

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.

Sat Apr 9 15:47:21 2022, Carsten, Rodolfo, Sarper, Patrick, Runs, 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)

Sat Apr 9 14:15:44 2022, Kristian, Max, Konstantin, DAQ, 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

Sat Apr 9 13:45:42 2022, Max, Kristian, Runs, first 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

Time	SIS-intensity	cooler-HV	LMD-DAQ1 start-end	LMD-DAQ2 start-end	scan range(nm)	step width(nm)	dwell time(s)	comments
11:25	1.0e9	209622	0102 - 102	7839-7839	323.2 - 322.8	0.002	3s	LV readout problem solved. WM readout is wrong (Cobra set is good)
12:15	old beam	209622	0103 - 103	7840-7840	323.2 - 322.8	0.002	3s	WM readout is wrong
12:50	2.3e9	209617	0104 - 104	7841-7841	323.2 - 322.8	0.002	3s	couldnt open go4 stream view, stopped after one good scan, WM readout is wrong .
13:20	2.0e9	209617	0104 - 105	7842-7842	323.2 - 322.8	0.002	3s	first scan with LV correct
13:40	1.2e9	209618	0106 - 106	7843-7843	323.2 - 322.8	0.002	3s	3 loops
14:20	1.5e9	209612	0107 - 107	7844-7844	323.2 - 322.8	0.002	3s	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)

Sat Apr 9 06:42:23 2022, Kristian, Laser, Laser step size

We changed the laser step size to 0.002 nm which corresponds to 5.75 GHz.

Sat Apr 9 06:25:22 2022, Max, Kristian, Runs, morning 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

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	00xx	78xx	32x.x - 32x.x	0.01	x	sketch for filling the table
06:40	1.7e9	209619	0098-0099	7836	323.2 - 321.2	0.002	4s	laser pulse energy is @ ~12mJ after SHG
09:35	1.4e9	209624	0101-0101	7838-7838	323.2 - 322.8	0.002	3s	only 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:25	1.0e9	209622	0102 - 102	7839-7839	323.2 - 322.8	0.002	3s	LV readout problem solved. WM readout is wrong (Cobra set is good)
12:15	old beam	209622	0103 - 103	7840-7840	323.2 - 322.8	0.002	3s	WM readout is wrong
12:50	2.3e9	209617	0104 - 104	7841-7841	323.2 - 322.8	0.002	3s	couldnt open go4 stream view, stopped after one good scan
13:20	2.0e9	209617	0104 - 105	7842-7842	323.2 - 322.8	0.002	3s	first scan with LV correct

Sat Apr 9 05:26:25 2022, Patrick, Laser, Wavemeter

The wavemeter still shows large spikes from time to time. The exposure time is still at 34ms.

Sat Apr 9 05:00:11 2022, Carsten, General, Draft Docs and cheat sheet

Please check the attached files,

and correct or enhance them.

Print out a copy

Sat Apr 9 04:40:01 2022, Patrick, DAQ, Bugged Trending plots?

The problem from yesterday (ID:147) still persists. All the plots (not only the labview stuff) comes in too late in go4. However, the time axis is correct, see picture.

Sat Apr 9 04:01:35 2022, Carsten, , 2nd DAQ

Switched the CAEN TDC back on and changed the threshoolds for the ADC to:

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

Goto page Previous 1, 2, 3, 4 ... 10, 11, 12 Next All

ELOG V3.1.5-fc6679b