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+ 2024, all entries  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
Entry  Wed Jun 26 11:59:12 2024, Ruijiu, Shahab, Carsten, Analysis, Prepare plots for Thomas's presentation 6x
data:
(env_OnlineDataAnalysisSystem) litv-exp@lxbk0497:/lustre/astrum/experiment_data/2024-05_E018/OnlineDataAnalysisSystem/data/iq/IQ_2024-06-
12_21-47-54$
The root file is at:
(env_OnlineDataAnalysisSystem) litv-exp@lxbk0497:/lustre/astrum/experiment_data/2024-05_E018/OnlineDataAnalysisSystem/data/iq/IQ_2024-06-
12_21-47-54$ root filtered_spectrum_670_750.root

The figure below shows the interface of the program "combine_injection". You can combine any tdms file with this program. To run this 
program, you need to log in to the server /luster/astrum/, and activate the conda environment. Then type the command "combine_injection" at 
the terminal. You will see the interface. 
Entry  Sat Jun 15 03:46:34 2024, Night shift, Accelerator, GSI down 
All quadrupole and dipole magnets at SIS and ESR are out of order. Repairs can be expected earliest tomorrow evening. No shifts will take place before 6pm. Have a look at your mails for details.
Entry  Fri Jun 14 14:44:51 2024, Afternoon shift, Runs, Afternoon shift 
Pizza shift

the scan direction is from higher wavelength to lower wavelength, even though it is noted otherwise here in the software.
From hardware side, the laser can only scan in one direction: long wave length to short wave length, independent of what is written in the tables.


Time Part. Det. Int ESR-intensity cooler-HV LMD-DAQ1 Files LMD-DAQ2 Files scan range(nm) number of positions dwell time(s) n loops comments
14.06.2024 12:45 38900 2e5 104411 72 89 549.6 - 550.4 201 1s 3 starting with 50 accumulation
14.06.2024 13:13 41400 2e5 104411 73 90 549.6 - 550.4 201 1s 3 there was a :10 crash during the injection, laser scan started normally.
14.06.2024 13:41 39500 2e5 104411 74 91 549.6 - 550.4 201 1s 3
14.06.2024 14:38 67750 2e5 104412 75 92 549.6 - 550.4 201 1s 3 afternoon shift takes over. After short break from hkr to optimize beam, proceeding with 30 injections, particle number detector might not have been reset, check next run
14.06.2024 15:02 34500 2e5 104412 76 93 549.6 - 550.4 201 1s 3
14.06.2024 15:38 27500 1e5 104412 77 94 549.6 - 550.4 201 1s 3
14.06.2024 16:01 25300 1e5 104412 78 95 549.6 - 550.4 201 1s 3
14.06.2024 16:23 28700 1e5 104412 79 96 549.6 - 550.4 201 1s 3 At around 550.2 nm the wavemeter is overexposed
14.06.2024 16:48 xxx xx xx 80 97 xx xx xx xx empty file , no laser scan, work on laser, while trying to adjust the wavemeter, we tried to move the laser using medusa, at some point, this caused the cobra to go into error mode again, onlz a restart could solve it. As a consequence, we still do not know if the wavemeter coupling is optimal
14.06.2024 17:17 30000 1e5 104412 81 98 549.6 - 550.4 201 1s 3 wavemeter coupling looks good now
14.06.2024 17:41 56900 1e5 104412 82 99 549.6 - 550.4 201 1s 3 ratemeter was probably not reset
14.06.2024 18:04 8100 1e5 104412 83 100 549.6 - 550.4 201 1s 3 really bad injection (looked fine (?)), low ion count from SIS, they exchanged a cathode @UNILAC
14.06.2024 18:42 3200 3e4 104412 84 101&102(automatically opened new file without command after 1GB?) 549.6 - 550.4 201 1s 3 problems with accelerator: after deacceleration the beam is gone. Scraper position has moved(?). The cooling water from GSI is too warm, so we had to shut down the laser. NTCAP restarted. And NTCAP restarted again @20:39 for test data for Shahan.
Entry  Fri Jun 14 13:14:29 2024, Konstantin, Bernhard, Peter, Lukas, General, DAQ crashes at :10 
10 Minutes past a full hour (XX:10) the windows PCs (sometimes) loose connection.
This causes the labview server & the laser remote ctrl to crash.

reset:
- "sto ac" on first DAQ1
- restart labview server (medusa - run - make data available for mbs off/on)
- "sta ac" on first DAQ1

It can make sense to try to avoid laser scans in this time window if those crashes occur more regularly.
Entry  Fri Jun 14 11:44:23 2024, Carsten Brandau, Accelerator, Cooling Time in SC7 increased from 9s to 12s 
Cooling Time in SC7 increased from 9s to 12s
Entry  Fri Jun 14 06:38:41 2024, Konstantin Mohr, Bernhard Maass, Peter Micke, Lukas Kau, Dounia Boudefla, Runs, Morning runs 
Very successful shift, no crashes until 11:10
Previous night shift had problems with the pulse laser starting around 3am.
Something was loose at the FCU. Rodolfo was called in and was able to fix it.

the scan direction is from higher wavelength to lower wavelength, even though it is noted otherwise here and in the software.

Time Part. Det. Int ESR-intensity cooler-HV LMD-DAQ1 Files LMD-DAQ2 Files scan range(nm) number of positions dwell time(s) n loops comments
14.06.2024 06:35 36500 7e5 104410 59 76 550.1 - 550.9 201 1s 3
14.06.2024 07:00 24600 8e5 104409 60 77 550.1 - 550.9 201 1s 3
14.06.2024 07:23 22900 8e5 104410 61 78 550.1 - 550.9 201 1s 3
14.06.2024 07:44 27000 8e5 104410 62 79 550.1 - 550.9 201 1s 3
14.06.2024 08:06 31000 7e5 104410 63 80 550.1 - 550.9 201 1s 3
14.06.2024 08:29 29500 8e5 104410 64 81 550.1 - 550.9 201 1s 3
14.06.2024 08:52 26800 8e5 104410 65 82 550.1 - 550.9 201 1s 3
14.06.2024 09:13 33500 8e5 104410 66 83 550.1 - 550.9 201 1s 3
14.06.2024 09:35 15700 8e5 104410 67 84 550.1 - 550.9 201 1s 3 only 10 shots accumulation
14.06.2024 09:59 35000 8e5 104410 68 85 550.1 - 550.9 201 1s 3 back to 30 shots accumulation
14.06.2024 10:24 33600 8e5 104410 69 86 550.1 - 550.9 201 1s 3
14.06.2024 10:48 35500 9e5 104410 70 87 550.1 - 550.9 201 1s 3
14.06.2024 11:09 8e5 104410 71 88 550.1 - 550.9 201 1s 3 data crash, labview disconnected


2024-06-14 (note added): Intensities from ESR trafo are not reliable at low internisties, offset can change substantially. Use trafo only with ion numbers sginificantly higher than 1e6.
Entry  Thu Jun 13 22:08:07 2024, Dayshift, Accelerator, Problems with Accelerator? IMG_6064.jpgIMG_6065.jpgIMG_6066.jpg
It seems to be that there are some problems with the injections in the ESR.
The last 2 accumulation cycles showed that wheter only a small amount of ions are injected into the ESR or the injection is missing.

Photos of the last 2 accumulation cycles are attached.

We ask if there are some problems with the ESR or with the SIS18, because the particle number in the SIS18 is also decreasing... 
Entry  Thu Jun 13 18:48:26 2024, Ruijiu Chen, David, Shahab, Yuri, Analysis, The ion identification of 229Th is correct. simulation_result.outLifetime_of_beam7.pdf
Harmonic: 124.0 , Bp: 7.796046 [Tm]
ion            fre[Hz]                       yield [pps]    
------------------------------------------------------------
237U+92        243732740.7822311819          8.6164e+03     
237Np+92       243732858.1891748905          1.9672e+02     

224Ac+87       243759120.6575988531          1.7025e+03     

229Pa+89       243784072.1343108118          2.5529e+03     
229Th+89       243784111.0000000000          3.3883e+03   
  
234Pa+91       243807737.9699291289          2.4721e+03     
234Np+91       243807852.4158236086          1.7745e+01     

The strongest line is 229Th+89/229Pa+89. The yield and frequency of 229Pa+89 and 229Th+89 are very close to each other.  We needed to 
install Al target to suppress Pa as much as possible. Al gives a better ratio of h-like to he-like than Be. Two peaks at left 
side are 237U+92/237Np+92 and 224Ac+87. One peak at right side is 
234Pa+91/234Np+91. 

Note added 2024-06-14 (Carsten): a) We will not produce Np, this is an artifact of Lise, b) relative intensities are for injection only. Line intensities for  237U/224Ac/234Pa are substantially lower after cooling/HF/deceleration.
Entry  Thu Jun 13 18:38:24 2024, Rodolfo Sanchez, Julian Palmes, Sebastian Klammes, Laser, Laser Dye change - new MRC settings - scraper checks of laser beam MRC-settings-13-06-2024-after-dye-change-at-3pm.JPG
We changed the dye at ~3pm.

After some fine adjustements of the laser we had to change the MRC settings, because the laser position changed.
Therefore we checked the position of the laser with the T-Scrapers with the settings from post 49 "First Scraper Scan".

New settings of MRC and screen pic is attached.
The position of the laser on the screen is now the 'same' as yesterday (see attachement).
Entry  Thu Jun 13 18:23:46 2024, Julian, Laser, Restarting the laser controller 
If the laser controller is locked up again, the little display will show an error message after an attempted medusa scan.
To restart it, follow these steps:
1.) Unlock the beam stabilization.
2.) shut down medusa and the wavemeter software
3.) Turn off the 2 laser stages
4.) Close the shutter of the pumping laser
5.) Turn off and on the power button of the pulsed laser inside of the black box of the pump laser insertion.

To start again go back through the list.
Entry  Thu Jun 13 18:03:36 2024, Afternoon shift, Runs, Continuation: First scans 2024_06_13_229Th_Lifetime_at_190MeV_afterscraping.png2024-06-13_23-13-55-242.png
Time Part. Det. Int ESR-intensity cooler-HV LMD-DAQ1 Files LMD-DAQ2 Files scan range(nm) number of positions dwell time(s) n loops comments
00:01 3e5 104438 13 27-29 550.1 - 550.9 201 2s 4 40 injections, there is still a fast decaying component, may be due to the higher electron current of 200 mA. Going back to 100 mA in next run and also put a "loose" scraper on the inside.


ntcap 2024-06-12_21-47-54

Time Part. Det. Int ESR-intensity cooler-HV LMD-DAQ1 Files LMD-DAQ2 Files scan range(nm) number of positions dwell time(s) n loops comments
00:50 ? 3e5 104438 14 28- 550.1 - 550.9 201 1s 6 30 injections, e-cooler current at 100mA, scraper GE01GD2ID (north arc, inner scraper) now at position +30mm, medusa crashed when started, laser position was lost and retrieved by resetting the beam position stabilization
01:43 25700 3e5 104438 15 31-32 550.1 - 550.9 201 1s 6 e-cooler current 100mA, NA position -30 activated, NI +28, SA -28, DS3HG +10
02:32 21750 4e5 104417 16 33 550.1 - 550.9 201 1s 3 reduced iterations due to short life time
02:54 29200 4e5 104417 17 34 550.1 - 550.9 201 1s 3
03:16 (?) 4e5 104417 18 35 550.1 - 550.9 201 1s 3
03:40 33700 5e5 104417 19 36 550.1 - 550.9 201 1s 3
04:03 31600 5e5 104417 20 37 550.1 - 550.9 201 1s 3
04:25 29200 4e5 104417 21 38 550.1 - 550.9 201 1s 3
04:46 27500 4e5 104417 22 39 550.1 - 550.9 201 1s 3
05:08 30400 4e5 104417 23 40 550.1 - 550.9 201 1s 3
05:31 31300 4e5 104417 24 41 550.1 - 550.9 201 1s 3
05:56 30000 3e5 104417 25 42 550.1 - 550.9 201 1s 3
06:18 24500 4e5 104417 26 43 550.1 - 550.9 201 1s 3 Morning shift took over: Constantine, Peter, Lukas, Jonas, Dounia
06:43 27 44 550.1 - 550.9 201 1s 3 Medusa crashed when starting the laser scan
06:57 4e5 104417 28 45-46 550.1 - 550.9 201 1s 3 DAQ1 started a bit later since we needed to restart and connect the file server again; after starting laser scan we noticed that the beam is gone on glass disk, reason was likely user error as medusa was set to send the laser to 500.9nm instead of 550.9nm
07:27 11800 4e5 104417 29 47 550.1 - 550.9 201 1s 3
07:51 23500 4e5 104417 30 48 550.1 - 550.9 201 1s 3
08:14 15000 5e5 104417 31 49 550.1 - 550.9 201 1s 3
08:37 35300 5e5 104417 32 50 550.1 - 550.9 201 1s 3
08:58 32800 5e5 104417 33 51 550.1 - 550.9 201 1s 3
13.06.2024 17:32 23 500 5e5 104412 35 52 550.1 - 550.9 201 1s 3First scan of afternoon shift. 30 Injections. Electron current was set to 30 mA. (Note added 2024.06.14 17:55 - Carsten: To what I remember electron current is 80mA) Dye was changed before this scan. Wavemeter overexposed on the second scan for 2-3 steps, not sure if during the stepping or actual measurement. In the middle of the third scan, medusa crashed.
13.06.2024 xx 5e5 104417 36 53 550.1 - 550.9 201 1s 3 25 Injections 75Hz particle detector south, medusa crashed immediately, laser controller was locked up. Restarting the laser controller solved the issue.
13.06.2024 18:30 28 200 5e5 104412 37 54 550.1 - 550.9 201 1s 3 25 Injections , DAQ1 no data collected (no start acquisition pressed)
13.06.2024 18:50 26 000 5e5 104412 38 55 550.1 - 550.9 201 1s 3 23 of 25 Injections, two were empty injections from SIS
13.06.2024 19:13 31 600 5e5 104412 39 56 550.1 - 550.9 201 1s 3 29 of 30 Injections, one was empty injections from SIS
13.06.2024 19:45 34 700 5e5 104411 40 57 550.1 - 550.9 201 1s 3 30 of 30 Injections
13.06.2024 20:07 33 300 6e5 104411 41 58 550.1 - 550.9 201 1s 3 30 of 30 Injections. Note: before and after run, the laser was exactly in the middle of the screen, but went to its proper position (slightly left of the middle) during the scan.
13.06.2024 20:36 29 900 7e5 104411 42 59 550.1 - 550.9 201 1s 3 30 of 30 Injections. Note: Before the run ad during the first scan, the laser was above the middle. In the third scan, it was back in its proper position.
13.06.2024 20:57 28 900 7e5 104411 43 60 550.1 - 550.9 201 1s 3
13.06.2024 21:18 26 000 7e5 104411 44 61 550.1 - 550.9 201 1s 3 27 of 30 Injections
13.06.2024 21:40 18 000 6e5 104411 45 62 550.1 - 550.9 201 1s 3 out of the first injections 4 were with low energy and 4 did not arrive at all, for the rest, pretty much every second injection is missing. Checking with HKR.
13.06.2024 22:02 24 900 7e5 104411 46 63 550.1 - 550.9 201 1s 3 Same thing with injection.
13.06.2024 22:23 31 700 7e5 104411 47 64 550.1 - 550.9 201 1s 3
13.06.2024 22:46 30 900 7e5 104411 48 65 550.1 - 550.9 201 1s 3
13.06.2024 23:09 33 100 7e5 104411 49 66 550.1 - 550.9 201 1s 3 Laser shifted to the left
13.06.2024 23:33 25 200 7e5 104411 50 67 550.1 - 550.9 201 1s 3
13.06.2024 23:55 28 600 7e5 104411 51 68 550.1 - 550.9 201 1s 3 We moved the laser back to the original position using the MRC
14.06.2024 00:52 33 100 8e5 104410 52 69 549.85 - 550.9 239 1s 3 Widen scan range to account for the difference between wavelength vac. vs. wavelength air; Laser shifted to the left
14.06.2024 01:20 29 800 8e5 104410 53 70 549.85 - 550.9 239 1s 3
14.06.2024 01:44 -- 7e5 104410 54 71 549.85 - 550.9 239 1s 3 Medusa crashed and was restarted; measurement interrupted; connection of MBS to Labview server crashed and MBS and go4 were restarted (DAQ1)
14.06.2024 02:03 34 700 8e5 104410 55 72 549.85 - 550.9 239 1s 3
14.06.2024 02:26 31 400 7e5 104411 56 73 549.85 - 550.9 239 1s 3
14.06.2024 02:49 -- 7e5 104411 57 74 549.85 - 550.9 239 1s 3 Medusa crashed and was restarted; measurement interrupted
14.06.2024 02:51 -- 7e5 104411 58 75 549.85 - 550.9 239 1s 3 Medusa crashed and was restarted;


The Medusa crash also crashed the Cobra Laser. We tried to restart it but afterwards the power of the Laser was more than one order of magnitude lower than before. It is not clear what caused the problem, Rodolfo is on his way to GSI now to fix the issue.
Entry  Thu Jun 13 14:56:09 2024, Stefan Schippers, Accelerator, Estimated beam lifetime: About 150 s 
Estimate of storage lifetime using my code 'hydrocal':

 ion mass in u ...................................: 229
 ion nuclear charge ..............................: 90
 ion charge state ................................: 89
 beam energy in MeV ..............................: 45501.1
 beam energy in MeV/u ............................: 198.695
 beam beta .......................................: 0.566309
 beam rigidity in T m.............................: 5.4944
 ring circumference in m .........................: 108.36
 ring acceptance in mrad .........................: 2
 ring temperature in °C ..........................: 25
 ring vacuum pressure in mbar ....................: 3e-11
 residual gas density in m^-3 ....................: 7.28767e+11
 residual gas composition 
  Z   %
  1  93.43
  6   2.23
  7   0.75
  8   3.29
 18    0.3
 cooler length in m ..............................: 2.5
 electron current in A ...........................: 0.2
 magnetic expansion factor .......................: 1
 electron-beam diameter in mm ....................: 50.8
 electron density in cm^-3 .......................: 3.62844e+06
 cooler cathode temperature in meV ...............: 110
 cooling energy in eV ............................: 109000
 space_charge (0th iteration) in eV ..............: 44.3477
 space_charge (1st iteration) in eV ..............: 44.341
 transverse temperature in meV ...................: 110
 longitudinal temperature in meV .................: 0.2
 RR nmin .........................................: 1
 RR lmin .........................................: 0
 RR nele [no. electrons in subshell (nmin,lmin)] .: 1
 RR nmax .........................................: 128
 RR enhancement factor ...........................: 2.5
 RR alpha in cm^3 s^-1 ...........................: 8.04602e-08

 beam lifetime due to multiple scattering in s ...: 1.86e+06
 beam lifetime due to single scattering in s .....: 7.51886e+07
 beam lifetime due to charge capture in s ........: 3.5516e+06
 beam lifetime due to stripping in s .............: 1e+99
 beam lifetime due to recombination in cooler in s: 148.466
 beam lifetime with electron cooling in s ........: 148.46
 beam lifetime without electron cooling in s .....: 1.20121e+06

 detector count rates for 1E6 stored ions and a residual gas pressure of 3e-11 mbar: 

       recombination detector from ecool (Hz) ....: 4575.41
     recombination detector from res.gas (Hz) ....: 0.0545666
    total rate on recombination detector (Hz) ....: 4575.46

        ionization detector from res.gas (Hz) ....: 1.93798e-94
Entry  Thu Jun 13 14:41:22 2024, Ruijiu Chen, David, Analysis, Lifetime of beam during June 13 9:00~11:00 Lifetime_of_beam5.pdf
 
Entry  Thu Jun 13 14:35:27 2024, Ruijiu Chen, David, Analysis, Lifetime of beam during June 13 7:00~9:00 Lifetime_of_beam4.pdf
 
Entry  Thu Jun 13 14:20:36 2024, Ruijiu Chen, David, Analysis, Lifetime of beam during June 13 4:30:7:00 Lifetime_of_beam3.pdf
 
Entry  Thu Jun 13 13:29:47 2024, Ruijiu Chen, David, Analysis, Lifetime of beam during June 12 22:00- June 13 0:00 Lifetime_of_beam2.pdf
 
Entry  Thu Jun 13 12:37:14 2024, Ruijiu Chen, David, Analysis, Lifetime of beam in center of mass is 193 s. Lifetime_of_beam.pdf
 
Entry  Thu Jun 13 12:05:31 2024, Konstantin, Peter, Jonas, Accelerator, RF-amplitude Bunching80mA_BucketFill_10.pngBunching80mA_BucketFill_08.png
To realize the shortest bunches possible, we check the bunch length as a function of two different bunching amplitudes. With the bucket fill set to 1.0 we observe the spectra compiled in attachment 1. The second attachment is recorded with a bucket fill 0f 0.2.

For an RF amplitude of 0.2 we do not observe bunches any more but a coasting beam. In the shottky spectrum we can resolve a shift of the signal and thereby adjust the electron cooler voltage to the bunching frequency to within 1 V.

U_e-cooler = -104410 V
I_e-cooler = 80 mA
Entry  Thu Jun 13 10:42:02 2024, Danyal, General, Question 
What is the ion beam lifetime, according to the DCCT and Schottky? 
Can somebody measure it, please? 
Yesterday we could not see a fast drop in the "main" beam. 

Because the lifetime that is mentioned here is the one based on the particle detector and on the PMT countrate. 
If what is seen now is "only" some fast decaying component inside the beam, we could simply wait for its decay and then continue with the real measurement. 
Entry  Thu Jun 13 10:32:29 2024, Konstantin, Accelerator, (Proper) Cooler settings 
We change the acceleration voltage of the electron cooler and observe the platform high voltage and the count rate at the particle detector south.
Cooler current at 100mA.


set voltage measured voltage Schottky width
-40
80
-40
100
120
-40
-60
-80
-100
-120
-38
-40
-42
-44
-46
-48
-40
-38
-36
-34



with scraper driven in (first signal drop in attachment 2):

set voltage measured voltage Schottky width
-40
-38
-36
-34
-32
-30
-20 25kHz
-10 48kHz
-0 63kHz
-40
-42
-44
-46
-56 7kHz
-66 19kHz
-76 40kHz


5kHz Shottky width at proper cooling conditions.

Modified bunching HF in beam process 7 and 10 in Paramodi folder "Ring HF" to get coasting beam conditions.

Afterwards manipilated the electron current from 100mA to 200mA to 50mA in BP8.
Entry  Thu Jun 13 10:06:35 2024, Constantine, Peter, Lukas, Jonas, Dounia, Carsten, Accelerator, Suspected Beam Troubles (is it really 229-Thorium?) 
From experience, the lifetime of the beam in the storage ring should be on the order of magnitude of hours, however, we observer beam lifetimes of the order of 10ish minutes. This suggests either a beam loss mechanism, a totally wrong species or a combination of both.

Yesterday (Elog entry 46) it was verified that the main beam is indeed 229-Thorium in the ESR.

2024-06-13: After discussion (phone) with Markus the lifetimes are reasonable and are dominated by recombination in the cooler.
Entry  Thu Jun 13 02:05:04 2024, Carsten, Accelerator, Short Lifetime at 100 mA 2024_06_13_229Th_Short_Lifetime3.png
Lifetime still is short
Entry  Wed Jun 12 22:48:55 2024, Carsten, , Beam Halo 
The seamingly short live time reported in entry 53 is due to a halo from a different isotope (?). It can be scraped away from the outside. The 229Th89+ primary beam can be scaped away from the inside and the halo stays. There is some spacial headroom between the two components.

Scraping from the outside using GE02DS3HG @+6mm starts to scrape the halo in the south arc. Please note that the +6mm means that you move past central orbit (scraper starts from -130mm).
Using this scraper allows for using the particle detector behind the e-cooler (GE02DD2_G). Position PD south in event mode is -30mm (has to be verified with higher ion beam intensity and electron current for larger recombination rate=.

The primary 229Th89+ is touched from the inside with GE01DB2IG @+14mm (north arc).

Position of GE02DS3HG in event mode is +8mm.

Electron current in SC8 is increased from 100mA to 200mA for faster cooling at low energy in order to condition after deceleration and before scraping.


positions particle detectors and scrapers
NA position -30 activated
NI +28
SA -28
DS3HG +10
Entry  Wed Jun 12 21:21:15 2024, Yuri, Detectors, NTCap started 
Fcenter - 244.6 MHz
BW - 10 MHz
Entry  Wed Jun 12 18:48:43 2024, Afternoon shift, Runs, First laser scans 2024_06_12_229Th_Lifetime_at_190MeV.png
Time Part. Det. Int ESR-intensity cooler-HV LMD-DAQ1 Files LMD-DAQ2 Files scan range(nm) number of positions dwell time(s) n loops comments
19:15 38257 xx e x 104416 10 21-23 550.1 - 550.9 201 2s 8 40 SIS injections. Very short lifetime, further investigation is needed. preset_2024-06-12_19-08-23.mps
20:22 53056 xx e x 104416 11 24-25 550.1 - 550.9 201 1s 3 40 SIS injections. Only PDetector behing cooler, retracted by 8 mm. Still short lifetime.
20:58 40500 xx e x 104416 12 26-26 550.1 - 550.9 201 1s 2 40 SIS injections.
Entry  Wed Jun 12 17:12:13 2024, Julian, Danyal, Rodolfo, Laser, Timing für 229Th89+ Timing_229Th89_12-06-2024.JPG
We did the timing Ion-Beam Laser-beam time overlap.

The ion revolution frequency (and therefore the bunching frequency) is: 1.5429 MHz.
Entry  Wed Jun 12 12:12:44 2024, Konstantin Mohr, Julien Spahn, Jonas Koedel, Bernhard Maass, Accelerator, First Scraper Scan SpatialBeamOverlap.png
Thorium is in the ESR, we have time to check the beam position with the scrapers.
Beam Intensity in the ring 6E-5

Laser stabilization:
x1: -0.050
y1: -0.244
x2: 0.151
y2: -0.489

DS1VU: starting in negatives, touches beam at -0.1mm, beam gone at 0.5mm (laser gone)
due to betatron oscillation, vertical beam center is +0.5mm, beam diameter 1.2mm

DS1HA: starting in negatives, hf artifacts are gone at -25mm, touches beam at -17.2mm, beam gone at -16.4mm (laser gone)
DS1HA: starting in positives, hf artifacts are gone at +2mm, touches beam at -7.1mm, beam gone at -7.9mm
horizontal beam center is at -12.2mm, beam diameter 2.1mm (scraper is 8mm wide)


DS2VU: starting in negatives, touches beam at 0.4mm, beam gone at 1.0mm (laser gone)
due to betatron oscillation, vertical beam center is 1.0mm, beam diameter 1.2mm

DS2HA: starting in positives, hf artifacts are gone at 6mm, touches beam at -3.5mm, beam gone at -4.3mm (laser is scraped)
DS2HA: starting in negatives, hf artifacts are gone at -27mm, touches beam at -14.4mm, beam gone at -14.1mm (laser is scraped)

horizontal beam center is at -9.2mm, beam diameter 2.9mm (scraper is 8mm wide)

After the measurement of the ion beam position we superimposed the laser beam (see attachment 1).
Entry  Wed Jun 12 09:43:57 2024, Carsten, Accelerator, Stopped NTCAP at 9:43 
Setup at ESR is carried on - stopped the long-time NTCAP run from overnight,
Entry  Wed Jun 12 09:17:43 2024, Carsten, , Tests of background with ionization pumps on (from monday) mit_IZ_trending_sued_alles(blind_durch_IZ).pngmit_IZ_trending_mitte_Nord_mit_Strahl.pngmit_IZ_trending_mitte_Nord_ohne_Strahl.pngmit_IZ_trending_mitte_Nord_alles.png
On monday the ionization pumps were switch on to test the background, and if it is possible to run with the pumps switched on.
Results and comments, see below:

Later some data were recorded with DAQ1 to allow for a more thorough analysis - beam is 238U38+ at 401 MeV/u - file 0013
Please note the data of this file was recorded after the figures below were taken.

In short, we have switched off the the ionization pumps because the conclusion is somehow ambiguous. Background rates from real photons are considerably low at ~5Hz and 10Hz for the small-band PMTs (see figure), Yet, PMT south goes up to 350 Hz and sees a lot of photons from the plasma discharge. The few Hz of the small-band detector would be suppressed by the length of the ion bunch / full lenght of the ring. But what is not known is how much it would actually influence the local vacuum of the ring.

Semjon Strohmenger also checked that the valve to the turbos in front and behind the gas-jet is open (--yes). They are running the whole beam time.
I exchanged the prepump at a pocket located between gas-jet and VUV detection set-up. Here after baking a leak was found, and the pocket was pumped with an "old" prepump.
Vacumm in the pocket was ~1mBar. Installed a more powerful Edwards XDS i10. When we left ESR the pressure in the pocket was already at low 10^-2 mbar and still decreasing.
May be this helps to improve local pressure.
Entry  Wed Jun 12 01:51:51 2024, RuiJiu, David, Analysis, ID E142_TEline-ESR_229Th.lppsimulation_result.out229Th89_124h.png229Th89_125h.png
The preliminary identification has been thoroughly checked using the RionID software. We have confirmed that the identification is accurate.

Attached can be found the simulation file with each of the expected ions, their revolutions frequencies in the 125th harmonic and expected yield from the LISE file attached.
Also attached are some figures from RionID that highlight the region of interest for the 124th and 125th harmonics. The center frequency of the 245 MHz resonator is closer to the 124th harmonic for 229Th+89 which is located at 244.769 MHz. 

If necessary, we can slightly shift the resonator curve to higher frequencies to fine-tune the signal-to-noise ratio for 229Th+89.
Entry  Tue Jun 11 23:46:06 2024, Carsten )))), Accelerator, ID 
----
The frequency of the primary beam 238U82+ at the injection:
Ucool = -360 V
Frev = 1.974647 MHz without bump
Frev=1.97387 MHz with bump
---
ID:
246 MHz + kHz (+/- intensity) ID
521 +++ 238/92+
565 +.    230/89+
595 +++ 235/91+
642 +.    227/88+
670 +.    232/90+ 
693 +++ 237/92+ (strongest line)
721 +.      224/87+
744 ++.   229/89+ (our Th line)
767 ++.   234/91+
822 +.     226/88+
845 +.     231/90+
867 +.     236/92+
901 -       223/87+
922 +.     228/89+
942 +.     233/91+
1001 +.    225/88+    
1020 ++.  230/90+
1039 +.    235/92+ 
1100 +.     227/89+
1211 + <- far off
Entry  Tue Jun 11 22:59:06 2024, Carsten, Accelerator, Identification / NTCAP started 
ESR is set-up in most parts.We are trying to identify our 229Th89+. It is more cumbersome then exspected because of the thick target an d the according energy loss, the pattern has changed compared to the last beamtime.

Just started the NTCAP with center frequency 246,5 MHz, 10 MSamples/s and -25db.
Center frequency will later be changed back to about 244,5 Mhz.

Directory 06-11-22_55_15 (correct time stamp).
Entry  Tue Jun 11 21:38:35 2024, Julian, Imke, Rodolfo, Laser, Wavemeter HeNe long time stability HeNe_LangeMessung_11-06-2024.JPG
The HeNe was running over night and the measured laser frequency of the wavemeter was logged, see picture.
A significant drift of around 300 MHz is visible during the night.
It is possible, that the laser lab got too cold during the night, as the pulsed laser was not running.
For now, we put the wavemeter in a thermoinsulator box...
Entry  Tue Jun 11 21:23:11 2024, Julian, Imke, General, How to read out voltage medusa1.JPGmedusa3.pngmedusa4.png
1.) If not already opened, open the Medusa Laser Control software, see picture:
2.) In the "view" submenu, choose "proteus status".
3.) At the bottom of the list, the K250 shows the scaled voltage.
Entry  Tue Jun 11 09:17:46 2024, Julien, Konstantin, Lukas, DAQ, Important commands (DAQ1) SSH_Connection.pngMBS_Start.pngDAQ1_startup.pngRates.pngBildschirmfoto_2024-06-11_10-01-38.png
To connect to the DAQ1 pc, open a terminal and type:
ssh atplaser@r4l-41
Enter password for user atplaser (note that you're typing on an English keyboard).

To start MBS on DAQ1 go to folder mbsrun/E0052/DAQ1 via "cd mbsrun/E0052/DAQ1" and start mbs by typing "mbs". If you want to ensure that you are in the correct folder list the content of the folder by using "ls -l". You should see the list depicted in the second attachment.

Finally, to start the data acquisition (ensure that the 'medusa' is running on atppc023) use commands
@startup
sta ac
within the mbs prompt. You should see a similar result as in attachment 3. Particularly, note the important line
"-R4L-41 :read_meb :connected successfully to LabView Server. ".
A more detailed compilation of commands within mbs is given in Entry 10.

If one wants to observe the current acquisition, one must open a second terminal and establish another ssh-connection to R4l-41. The "rate" command will then show the incoming events on mbs (see attachment 4). If something went wrong you will see that the event-rate goes down. This might be an indication that the connection to medusa has crashed (see attachment 5).
Entry  Mon Jun 10 11:59:12 2024, Ruijiu Chen, Analysis, The ion identification of spectrum recorded on 2022 simulation_result.outE142_TEline-ESR_229Th.lppThe_ion_identification_of_spectrum_recorded_on_2022_v2.pdf
The simulated frequency is given in simulation_result.out. The yield is calculated by LISE file. The LISE file is attached here also.
Entry  Mon Jun 10 09:17:38 2024, Carsten, DAQ, Updated Channel List 2024_06_10_ChannelList.pdfChannelList.odt
 
Entry  Mon Jun 10 08:57:35 2024, Carsten/Konstantin, DAQ, Further Tests from Sunday 2024-06-09 - new voltages and tresholds for PMTs - testdata in files 
Voltages and thresholds increased for PMT Middle and North (in order to account for the ADC measurement in DAQ2

PMT South ("braodband") ET9422 1500 V thresh: 7
PMT Middle ("smallband") ET9423 2650 V thresh: 10
PMT North ("smallband") ET9423 2650 V thresh: 12


Tests with laser

Thresholds adjusted for PD SO and PD NO.
Smaller adjustements in the analysis cdoe of DAQ1 (directory 229Th) to deal with the proper alignment of laser steps (Step-spectra). Seems to solved now.

DAQ rate/trigger rate DAQ1 - interference with Labview
DAQ1 can be started without connection to Labview server after some timeout (~ 1min) or so the usual trigger rtate of 200 Hz can be seen in mbs (via: "sh acq" command)
If the Labview server is closed, e.g. during the run or between to laser runs - the DAQ rate drops to 30 Hz only. Very likely MBS is busy trying to fetch data from the non existing Labiew server.
The problem can be solved by leaving closing the the DAQ (MBS not Go4...) and restarting mbs/DAQ, e.g. via @shutdown, leave mbs, resl, start mbs, Qstartup, start acq.
Of course, also Go4 needs to be restarted to establish a new connection to MBS.
The DAQ rate of DAQ1 should be regularly checked with sh acq !


Test data
DAQ1: 005.lmd
DAQ2: 010.lmd
both rubbish, partially adjustments of threshilds etc.

~2.7e6 ions (238U92+)
201 laser steps 550nm, 549nm, 50 shots per step
DAQ1: 006.lmd
DAQ2: 011.lmd/012.lmd
Threshold for PD SO not adjusted

restart
DAQ1: 007.lmd
DAQ2 013-017.lmd

same with few 10^5 ions:
DAQ1: 008.lmd
DAQ2: 018-020.lmd
Entry  Sun Jun 9 10:20:38 2024, Carsten/Danyal, Detectors, Recap from yesterdays work with test beam (Detectors / beam /DAQ) 
In the ESR we had thw whole day (saturday) a 400MeV/u bunched 238U92+ test beam (about 2 MHz). The RF signal is cabled as input to the DAQ (seperate post/entry).
Intensity is artificially reduced to a few 10^6 (with some tests alsodone at 10^5).
In all the tests the both particle detectors were moved in pus the empty pocket on the inside to mimick the background conditions during the run (aka no other isoopes, no other charge state, clearing of orbit fromdonw-charged ions.

Noise background
With the bunched beam all three PMTs and the channeltron show an ~20MHz "noise beat" below the actual signal that seems to be phase stable. The "noise train" is repeated with about 2 MHz (very likely the bunch revolution frequency). The amplitude of the noise is rather low and can be easily discriminated for the three PMTs, but not so easy for the channeltron, as the channeltron signal is more "continuous" and has no clear gap for the threshold.
A working hypothesis could be that Al mirrors or something similar act as pickup electrodes for the real beam.
2024-06-10: Correction : Signal is not "phase-stable" - and 200 kHz (wrong reading and triggering of scope)

Channeltron
The signal of the CT is rather small. In order to get the singal of the CT out of the noise it needed to be opreated at about 2600V. With an according threshold setting the CT sees a signal that is clearly from the beam and absent with "no-beam". The signal is 6-7 kHz even at the lowest intensitiies of ~10^5 ions in the ring. Worse, it doesn't show any bunch timing peak in the spctrum.
We decided that under these conditions the CT cannot be used during the 229Th beamtime.

PMTs
Voltages of the PMTs and thresholds of the CAEN CFD are adjusted with a bunched beam with an intensity of few 1 to 3*10^6 ions (and thus should be ok for lower intensities):

PMT South ("braodband") ET9422 1500 V thresh: 7
PMT Middle ("smallband") ET9423 2550 V thresh: 9
PMT North ("smallband") ET9423 2600 V thresh: 11


Bunch signals in DAQ

Ion frequency (measured) used in DAQ1 in SetParameter.C: 1.9693 MHz, the divisiion factor is set to 88.

All three PMTs show very nice and small bunch-time signals with a very low background floor. Thresholds are adjusted to have at least "1CFD tick" extra margin.
The small-band PMTs have no-beam rates < 1Hz, PMT south < 10 Hz.

The clear visibility of the bunches on the small-band PMTs means, on the other hand, that we still have quite some background from collisions with the residual gas (albeit it seems to be lower that in the last beamtime, but no concrete (normalized) numbers are available. PMT North and Middle have about the same solid angle but PMT middle features the CaF2 window. The bunch singal rate of PMT middle is about twice the one of PMT north indicating that about half of the signal stems from hydrogen Ly-alpha (at 121.6 nm) that is cut-off by the CaF2-window (about 123 nm).

We should discuss a) if the vacuum can be further improved, e.g. using the turbo pump, b) if PMT north should get a CaF2 filter (not at the moment).

All these findings are for the 400 MeV/u 238U92+ beam and should be rechecked with decelerated 200 MeV/u beam.

For both DAQs data are accumulated with two data sets, the first at a a few 10^6 ions and the second at a few 10^5 ions:
files for run1 (mid int): 003.lmd (DAQ1), 006-006.lmd (DAQ2)
files for run2 (low int): xxx.lmd (DAQ1), yyy-yyy.lmd (DAQ2)

The timing signals can also be very nicely be seen in the 25 ps TDC of DAQ2.
DAQ2 records also th common Stop signal in the 25ps TDC. There are indications that the CS signal (derived from the bunch frequency) jitters. The discrimonation of the bunchsignal should be cheked.
In DAQ2 the thesholds and windows for Mesytec are not yet set properly, so thre is no ADC signal, and no "second" discriminated signal.
This is because the Mesytec MSFC16 module had to replaced by a different similar module but with non-ideal internal components. The module still needs ot be adjusted properly.
Entry  Sun Jun 9 10:08:24 2024, Carsten/Danyal, Detectors, Particle detectors - Recap of yesterdays work 
South (behind cooler) - "SA_SZ" - DD2...
We have put the particle detecotr North to the poistion behind the cooler (north) to replace the defective particle detector.
This detector is an old "Kozhuharov" style plastic szintillator that runs with a voltage of 1400-1500 V.
The signal line in the Messhütte / ESR is the #5 (normally we have #6).

North (behind target) - "NA_SZ" - ....
In the north we put one of my "spare" detectors that I assembled from "old" parts of not well known provenience (old plastic, old small 1 inch PMT). While machining the plastic szintillation material it seems that the mateerial got slightly to warm and shows micro cracks. Still the detecotr works without any issues and with good timing.
Please note that typical voltages here are ~600-700V.
The signal line in the Messhütte is the #5 (north outside)
Entry  Sat Jun 8 13:11:52 2024, Carsten, General, Put the go4login in atplaser .bashrc 
Put the go4login in atplaser .bashrc in order to avoid that one always has to go to the go4 directory to set the environment variable.
go4login64 is now executed automaticlally and the environments are now set every time you open a (bash) shell.
A fixed version 6.3 is used. The login file might be changed back after the beamtime.
Entry  Sat Jun 8 12:45:05 2024, Carsten, DAQ, Temporary change of RF signal 
The setting was 1.540974 MHz and division factor 68 (for a 200 MeV/u) beam, and the signal was taken from a signal generator.
I now switch to the "real" RF signal from the accelerator (~400MeV/u), that is 1.9693 MHz and the factor is set to 88.
This should be set back for laser tests or adjusted when we have the real decellerated beam.
Entry  Sat Jun 8 12:02:20 2024, Carsten, Detectors, Test Particle Detectors - Det South not working 
With the test beam from ESR I started to have a look at the PartDets.:
North outside: Works properly with a voltage of 1450 V
South outside (behind cooler) : no signal.

Later (when Danyal is here) we will check detectors cables etc., and if required put the north detector to position south and mount the untested (newly made, but with "old" material and PMT) spare detecotr to poistion north.
Entry  Fri Jun 7 17:10:45 2024, Sebastian, General, XUV LED 
Maximum XUV LED Voltage: 6.5V
Entry  Fri Jun 7 15:29:50 2024, Rodolfo, Detectors, Stored beam @ ESR Storedbeam@ESR_2024-06-07_15-25-18.png
One of the first PMT signals from the stored-ion beam @ ESR
Entry  Fri Jun 7 11:14:04 2024, Rodolfo, Laser, Trigger-signal for MRC MRC_TriggerSignal_T1_06-06-2024.jpgMRC_TriggerSignal_T2_Tmin_06-06-2024.jpgGeneratorSettings_for_MRC_06-06-2024.jpgMRC_Parameters_06-06-2024_18-30.JPG
We are using a 2-Channel Function Generator (from Textronik) to generate the trigger signal for the MRC Beam Stabilization.

The triggers are (according to the MRC nomenclature):
- Tmin = 500 us.
- T1 = 40 us.
- T2 = 460 us.
Entry  Fri Jun 7 09:15:31 2024, Carsten, DAQ, Updated Channel List ChannelList.pdfChannelList.odt
Entry  Thu Jun 6 19:51:11 2024, Carsten, Accelerator, ESR crew left after persisting problems with ESR magnets 
No beam today.--.
Entry  Thu Jun 6 19:47:01 2024, Carsten, DAQ, Exchange of Mesytec CFD/shaper - noise on signal lines from ESR magnets 
Jan exchanged the Mesytec CFD/shper since it could not be "remote controlled" anymore. The new one has different shaping times and delays.
It is noted the threshold range is rather small. 
With the new  shaper only the x100 signals could meaningfully discriminated etc.
After start of the ESR (magnets etc.) the signals of the 10x channels see quite some noise that makes it more difficult to adjust the thresholds for the low signals.
Entry  Thu Jun 6 19:42:20 2024, Carsten, Detectors, Exchange of amplifer channels / cables channels / HV voltage cables for PMT south 
In order to check if the problem of regular burst of pulses on the PMT south is related to amplfier channels and or the HV cable, the cheannels of the amplifiers in the ESR were changed. Likewise, a different HV cable is now used for the supply of the PS.

The problem still persists. It is visible on all three cable lines from ESR to Messhuette (100x DAQ1 cables , and 10x / 100x cables DAQ2).
Entry  Thu Jun 6 09:39:23 2024, Carsten, DAQ, Preliminary Channel Table (DAQ1 and DAQ2) ChannelList.pdfChannelList.odt
Entry  Thu Jun 6 09:23:53 2024, Konstantin Mohr, DAQ, Timing TimingSSH.pngDualTimer.jpegTimingAdjustment.JPG
The best way to adjust the bunch-laser timing is to start go4 (mbs must be running) from atppc023. Therefore use x2goclient and use the predefined session to access LXG1297. Start go4 as usual (Entry 10 + Entry 11).

With this preparation one can directly observe changes in the relative time between the common stop trigger and the photodiode signals (see Screenshot 3) when rotating the upper channel's fine adjustment wheel of the right dual timer above the laser table (see Screenshot 2, Don't touch the coarse adjustment wheel directly above!!!).

To ensure proper operation of Go4 make sure that it is closed in the ssh-session after the correct timing has been set!!!
Entry  Thu Jun 6 08:16:36 2024, Danyal, Accelerator, scraper info by Robert Boywitt Scraper_im_Cooler.pdfT_Scraper_ECEDS1__.PNGT_Scraper_ECEDS2__.PNGT_Scraper_ESR.JPEG
attched is more info about the T-scrapers (E-cooler) by Robert Boywitt (Tel: 2067 or 3357)
Entry  Thu Jun 6 07:54:15 2024, Danyal, General, pressure gauges and ion pumps  
yesterday (05.06.2024), firstly, the two ion pumps (underneath the fluorescence chamber) were switched off by the vacuum group (Björn Mai, Tel: 3438). Secondly, the two pressure gauges (located near the target) were switched off.  The pressure gauge at the fluo chamber is called E02VM3x and the pressure was 5.5e-11 mbar.  The other gauge is called IG2 and located further south, it measured 3.7e-11 mbar.  That was when ion pumps were still switched on.  Since ~10:45 (05.06.2024), the two ion pumps and the two ion gauges are switched off. There was no measurable change in the pressure after switching off the ion pumps.
Entry  Thu Jun 6 07:12:49 2024, Konstantin Mohr, Laser, T-Scraper 6x
The T-Scrapers can be driven by DeviceControl, which must be started from a console. To do so, first open the app-launcher and then select "Device Control", which is found under "Betrieb & Steuerung". Then select the appropriate context (should be the name of the experiment). After a short time the device icons will be present. The scrapers can be found in the last four columns and the second last row (see screenshot 1). By default, they should be colored like the following: DS1VU: green, DS1HA: yellow, DS2VU: green, DS2HA: yellow.

To test the scrapers, I made a measurement of the current laser position.

motor laser position (mm) screenshot
DS1VU (GECEDS1VU) 0 2
DS1HA (GECEDS1HA) -10 3
DS2VU (GECEDS2VU) 2 4
DS2HA (GECEDS2HA) -8 5


Note that the interlock of DS2VU is overridden when DS2HA is at 3mm. The interlock of DS1VU is overridden when DS1HA is at -4mm. The horizontal scrapers can only be moved when the corresponding vertical motors have reached their inner end positions.

Compared to the last position of Bi the horizontal and vertical positions deviate by approximately 5mm at all axes. However, since the electron cooler was completely dis- and reassembled in the meantime, it seems to be a reasonable starting point.
Entry  Wed Jun 5 19:22:43 2024, Carsten, Konstantin, Rodolfo, Detectors, PMT tests and preliminary thresholds SolarBlind_ET_9422_SN1042.pdfVoltagePMTs_05-06-2024.jpg
For all channels of the CAEN CFD the width of the logic signal is set to 255ns (maximum) to mitigate potential double pulses. For the very low count rates of the experiment this is not problem.

Tested and (partially) set-up UV PMTs and Chenneltron with a UV LED.

  • The UV LED does not give a useful signal for the small-band VUV PMTs.
  • In general, (using the new cables?) it seems that the cable noise is very low and can be easily discriminated.
  • PMT south (the broadband) sees a regular "strong" pulse-train/burst of photon signals. Therefore, the PMT was exchanged against a different one (SolarBlind ET Enterprises Model 9422, SN1042) - same result. New data sheet is attached.
  • The channeltron has a rather broad pulse height distribution but very low background. CFD thresholds can easily be set. Very likely the best detector to adjust the laser timing?
  • Channeltron Head : -2.5 kV , CFD threshold 8 mV.
  • PD SO threshold needs to be checked (in Go4 the number of counts of PD SO is much lower than of PD NO). Present values: both 10 mV.
  • Voltage PMT north / middle (both small-band) : -2600V, PMT south (replacement): -1500V. All thresholds: 15 mV
  • CAEN CFD must be switched back to LOCK or it otherwise produces additional background

Both DAQs run with about 2 laser scan cycles, 201 steps. 90 shots each...
date written to files.
Entry  Wed Jun 5 14:17:36 2024, Carsten, Accelerator, Distance Cooler Detector 
Calculation from Helmut Weick (copied from E142)
Distance e-cooler to particle detectors chamber:
“This is half of ESR plus distance target - detector. This even is on the web page”
54.28 m + 21.64 m
Entry  Tue Jun 4 22:54:02 2024, Rodolfo, Detectors, PMT - Manufacture - Test Result Data PMT_9423B_SN652_ETEnterprises_UniGießen.pdfPMT_9423B_SN653_ETEnterprises_TUDA.pdfPMT9422_SN1049_Datenblatt.pdf
 
Entry  Mon Jun 3 19:42:06 2024, Rodolfo, Laser, Laser-beam through E-Cooler LaserBeam-at-Screen_ESR-NO_08-06-2024.JPG
UV-laser beam is now going through the Electron-Cooler.

Telescope settings:
- Plan concave lens -500 mm
- Plan convex lens + 1000 mm
- Distance between the both linses: 535 mm
- Position at Long Travel Stage: 60,0 mm
Entry  Mon Jun 3 18:24:44 2024, Rodolfo, Detectors, PMT arrangement PMT_Arrangement_2024-06-03.jpgHV-Powersupply_PMTs_Thorium2024.jpg
The picture shows the actual configuration of the PMTs.

We are using a 4-Channel High-Voltage supply. The channels are labeled according to the PMTs names.

The suggested operation voltages are:

- PMT Nord (Type 9423, SN. 652): -2600 V
- PMT Mitte (Type 9423, SN. 653): -2500 V
- PMT Süd (Type 9422, SN. 1049): -1750 V
Entry  Sun Jun 2 00:01:46 2024, Carsten, DAQ, 25ps TDC CAEN V1290N DAQ2 lead to crash in DAQ2 due to a hardware issue 
On the CAEN V1290N TDC the piggy board for the lower 8 channels is not fixed well to the motherboard.
That prevented to the whole DAQ2 to trigger correctly or even crash every once in a while. Long attempt sot find the error in hard and in software.

I fixed/reattached the piggy board, but be careful with the attached Lemo cables. They might loose the board again (it used to fixed with hot glue).

DAQ2 now also seem to run smoothly.
Entry  Sat Jun 1 19:19:07 2024, Carsten, Detectors, Reminder: Check signals in scope and in DAQ of detectors with voltages switched off (vs. CFD threshold) 
When the ion pumps and vacuum gauges are switched off the scaler data of 
PMT_south, PMT_middle, PMT_north, PD_NO, PD_SO, PartDet North, PartDet South and (Channeltron) should be checked without voltages applied in dependence on the CFD thresholds to determine the "cable noise level" at which thre are NO entries other than 0 in hte spectra (minimum background).

Same for 2nd DAQ and Mesytec MSCF16
Entry  Sat Jun 1 19:00:57 2024, Carsten, DAQ, Change of (offline) frequency for common stop (CS) of VUPROMs (and 2nd TDC) and scaling factor 
Temporarily, for tests of the second DAQ I changed the frequency from the frequency generator and scaling factor that is used for the common stop signal to a value that is close to the expected value in the experiment.
Reason: For the second TDC (CAEN 25ps) TDC the time between to CS events must be of the order of 45 us. The TDC can store events up to about 51,x us and allows for overlap of these regions to be able to stitch together the events to a continuous time axis.

Since we plan to run at ~ beta= 0.5566 the revolution frequency is about

f=1.540974 MHz (0.6489 us)
This value is used in the frequency generator.

The scaling factor is set to 68.
=> 68 x 0,6489us = 44,1252 us between to CS.

Of course later the real RF value from the accelerator will be used.

Please leave or, if required to change, mark in ELog.
Entry  Sat Jun 1 18:55:18 2024, Carsten, Analysis, Go4 Analysis Version for DAQ1 (atplaser) 
Small enhancements and minor corrections / bug fixes are made to the original version of the online GO$ for DAQ1.
Assignment of channel names corrected, condition names adapted to present DAQ
Potential pitfalls are commented in the code.
The old version is untouched in its old directory.

The new version is in directory ~/go4/229Th. This version should be used for DAQ1 !

Some minor changes will still be needed to be done.
Please comment changes in the code with date and name and write into Elog.
Entry  Sat Jun 1 18:14:01 2024, Carsten, Analysis, DAQ and analysis directories 
DAQ1 (original):
-user atplaser
-runs on lxg1297
-go4 in ~/go4/229Th
-mbs in /esr/usr/atplaser/mbsrun/E0052/DAQ1
-data in lxg1297:/data.local2/229Th/
filenames follow the style 229ThDAQ1_nnnn.lmd (where nnnn is 4 digit integer number)
Data backup on WDBook lxg0155 local:
/media/stoe_exp/WDBook/E0052daq1 (/dev/sdc2)


Since the Go4 Code is still under development (clean up etc.), I still plan to submit regular updates, the last version before is always in ~go4/229Th
It is planned that all essential settings can be done via the automatically loaded script files SetParamters.C and SetConditions.C, so that no recompilation (and change of code) is required (work in progress).
Values in SetParamters.C and SetConditions.C have to be adjusted to the actual run.

DAQ2 (new / enhanced):
additional 25ps TDC, ADC and Vulom Scaler
-user stoe_exp
-runs on lxg0155
-go4 in ~/E0052/go4
-mbs in /esr/usr/atplaser/mbsrun/E0052/DAQ2
-data in lxg0155:/data.lcoal2/E0052/
filenames follow the style ThDAQ2_nnnn.lmd (where nnnn is 4 digit integer number)
Data backup on WDBook lxg1297 local:
/media/stoe_exp/WDBook/E0052daq2 (/dev/sdd2)


The following .scom in the directories will help to run the experiment
@startup in mbs -> Generic startup of all mbs tasks for data acquisition
@shutdown in mbs -> Ceans up everything before leaving mbs
@connectdisk -> connects to the rfio server on the data local disks.
or this, rawDispRFIO64, has to be started (locally __IN__ the data directory).
@openfile -> automatically opens a new file in the data local disks
@closefile -> closes the file
@disconndisk -> disconnects from the rfio server


Please note that the different path and file names are on purpose, so that they can be distinguished after the run.
Entry  Sat Jun 1 18:00:20 2024, Carsten, DAQ, ReadOut Trigger im Timer Scaler changed because of faulty signal from frequency generator ReadoutTrigger_from_FreqGen_2peaks.pngReadoutTrigger_from_Clock_1peak.png
Old readout trigger (~200 Hz) in 1MHz Scaler showed two nearby peaks indicating a jitter of the readout frequency or same faulty output driver of the frequency generator Metrix GX240 used to produce the readout frequency (see below).


Used the 1 kHz clok instead divided by 5 -> only a single peak in 1MHz spectrum in the scaler (see below).



This should be used during the beamtime.
Entry  Fri May 31 16:49:52 2024, Carsten, DAQ, Wiring DAQ 1 
Started to Check the wiring.

Status as of 2024-05-31

Inputs into 1. DAQ /TDC/Scaler - List according to file TLdaInputDescription.h in directory ~/go4/229Th

Cobra_Busy, // 0:
Next_Laserstep, // 1:
Laserscan_Complete, //2 :
{"PMT_South", 3, {3,11}},
{"PMT_Middle", 4, {4,11}},
{"PMT_North", 5, {5,11}},
{"Empty0", 6, {}},
{"ParDet_South", 7, {}},
{"ParDet_North", 8, {}},
{"QSwitch_500us", 9, {}}, // Important to mitigate missing Q-Switch
{"EmptyA", 10, {}},
{"Channeltron", 11, {9}}, //not yet wired
{"Bunch HF", 12, {}}, //not yet wired
{"PD_NorthEast", 13, {}},
{"PD_SouthEast", 14, {}},
QSwitch, //15
DC_Trafo, //16
{"Injection", 17, {}},
U_ECooler, // 18
I_ECooler, // 19
{"P_Gun", 20, {}},
{"P_Coll", 21, {}},
{"Common_Stop", 22, {}}, //? P_coll two times????
Clock_1MHz, // 23
{"Empty1", 24, {}},
{"Empty2", 25, {}},
{"Empty3", 26, {}},
{"Empty4", 27, {}},
{"Empty5", 28, {}},
{"Empty6", 29, {}},
{"Empty7", 30, {}},
{"Empty8", 31, {}},

Checked also the connections from the CFD to DAQ 1 (ok)
input connections to CFD are as labelled on the black laser Messhütte panel

CFD channels:

0: PMT south
1: PMT niddle
2: PMT north
3: PMT copper (not used)
4: PD NO
5: PD SO
6: Part Det South
7: Part Det North
8: empty
9: XUV front (not used)
10: XUV back (not used)
11:
12: Master Osci Bunchng HF (Süd)
13: empty
14: empty
15: Master Osci Bunchng HF (Nord)

PD_NO and PD_SO are terminated with 50 Ohm at input (conflicts with 50 Ohm input termination of CFD)
Entry  Fri May 31 15:53:06 2024, Ruijiu Chen, DAQ, run NTCAP system 
NTCAP is working again. 
Connect the RF cable and the scaler cables to NTCAP system.
The map of signal is recorded in following link. 
https://elog.gsi.de/esr/E0018/2
Test it with IQ rate of 10 MSamples/s.
E0052/IQ_2024-05-31_15-04-34 
E0052/SC_2024-05-31_15-04-34
Entry  Wed May 29 10:54:21 2024, Shahab, Jan, General, Gas Target Events with new timing system 2024-05-29_11-07-40-259.pngIMG_0465.JPGIMG_0466.JPGIMG_0467.JPG
Using the new timing system, it is possible to grab any events as pulses, but also as long inter event gates under GENESYS. Many instances of GENESYS can be running on ACO computers, so that there is no conflict, if an instance is running in main control room or another in ESR-Messhütte.

GENESYS Settings:

Inter-Event for 162 up and 163 down, signaling the gas target cycle. The signal can either be:

  • Controlled automatically by the control system (sub chain patterns)
  • Set to manual operation during setup or experiment.


"activating" the condition in GENESYS by clicking on the small "A" button in the condition. (B) us achieved by "deactivating" the condition in GENESYS, by clicking again on the "A", it turns into a "-". After this, it is possible to manually set the level "hi" or "low" on the left box. As a result a orange bar goes up and down as an indicator. Any time you can switch to automatic change by pressing on "-" again.


Using this new timing system, the old hardware in the main control room is not needed anymore.



Additional Information:


In the old experiments, we used the new control system events but still using the old hardware in the main control room. Please see:

https://elog.gsi.de/esr/E121/13
Entry  Wed May 29 09:49:30 2024, Rodolfo, Laser, Laser-beam profile Laserstrahl-at-EKühler_2024-05-03_#014.jpgLaserstrahl-at-EKühler_2024-05-03_Photo.jpg
Using a telescope (Plan-concave lens -500 mm and Plan-convex lens +1000 mm) after the pulsed-dye laser system we got the following laser-beam profile at the Electron-Cooler's position. Dye Laser @ 550 nm / 275 nm
Entry  Mon May 27 13:37:31 2024, Jan, DAQ, MesyTec Shaper Control Screenshot2_MSCFGUI.pngScreenshot3_MSCFGUI.png
For the 2nd DAQ the MesyTec Shaper (MSCF manual) is used as a spectroscopy amplifier and CFD.
It is controlled via the MesyControlGUI, which is installed on SADPC055 with a USB->mesyBUS connection to the MSCF.
The GUI can be started on any lxg-machine with the litv-exp account using the command/alias "E0052_shaper".

litv-exp@lxgXXXX:~$ E0052_shaper

The GUI will find connected devices automatically and should show this:

Double click on the connection icon of "5 MSCF-16" to open the full config pane

In order to save the settings to a local config file (bottom right), select "combined" writing mode on the top left. It is set to "hardware" by default.

Gain and ShapingTime can be set per group of 4 channles, PZ and CFD Thresholds can be set per channel.

Be aware that the "total gain" shown in the Gain panel is not correct by default. To calculate the proper gain factors, you need to go to the "Settings" tab of the device and set the follwong values:
Entry  Thu Apr 25 16:34:05 2024, Rodolfo, Laser, Efficiency of Fluorescein27 Fluorescein27_Efficiency.png
The figure below shows the efficiency of Fluorescein27 vs. Wavelength. Each point was averaged over 500 laser shots.

Dye Laser: Sirah, Cobra Strech.
- Solvent: Ethanol + H2O.
- Concentration Oszillator: 0.4 g + 0,2 g/l NaOH.
- Concentration Main Amplifier: (1/8) Concentration Oscillator .

Pump Laser: InnoLas, SpitLight 1500-30
- Seeding energy: 550 mJ / Pulse.

Note. Dye was mixed on 28.04.2022
Entry  Tue Apr 16 16:28:21 2024, Danyal, General, Great 
Thanks Jan!
Entry  Tue Apr 16 14:42:37 2024, Jan, General, G-PAC Proposal G-22-00052.pdf
 
ELOG V3.1.5-fc6679b