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, Page 1 of 4  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Author Categorydown Subject
  53   Wed Jun 12 18:48:43 2024 Afternoon shiftRunsFirst laser scans
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.
Attachment 1: 2024_06_12_229Th_Lifetime_at_190MeV.png
2024_06_12_229Th_Lifetime_at_190MeV.png
  68   Thu Jun 13 18:03:36 2024 Afternoon shiftRunsContinuation: First scans
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.
Attachment 1: 2024_06_13_229Th_Lifetime_at_190MeV_afterscraping.png
2024_06_13_229Th_Lifetime_at_190MeV_afterscraping.png
Attachment 2: 2024-06-13_23-13-55-242.png
2024-06-13_23-13-55-242.png
  73   Fri Jun 14 06:38:41 2024 Konstantin Mohr, Bernhard Maass, Peter Micke, Lukas Kau, Dounia BoudeflaRunsMorning 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.
  77   Fri Jun 14 14:44:51 2024 Afternoon shiftRunsAfternoon 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.
  3   Thu Apr 25 16:34:05 2024 RodolfoLaserEfficiency of Fluorescein27
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
Attachment 1: Fluorescein27_Efficiency.png
Fluorescein27_Efficiency.png
  5   Wed May 29 09:49:30 2024 RodolfoLaserLaser-beam profile
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
Attachment 1: Laserstrahl-at-EKühler_2024-05-03_#014.jpg
Laserstrahl-at-EKühler_2024-05-03_#014.jpg
Attachment 2: Laserstrahl-at-EKühler_2024-05-03_Photo.jpg
Laserstrahl-at-EKühler_2024-05-03_Photo.jpg
  16   Mon Jun 3 19:42:06 2024 RodolfoLaserLaser-beam through E-Cooler
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
Attachment 1: LaserBeam-at-Screen_ESR-NO_08-06-2024.JPG
LaserBeam-at-Screen_ESR-NO_08-06-2024.JPG
  20   Thu Jun 6 07:12:49 2024 Konstantin MohrLaserT-Scraper
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.
Attachment 1: 2024-06-06_07-15-20-802.png
2024-06-06_07-15-20-802.png
Attachment 2: 2024-06-06_07-19-33-924.png
2024-06-06_07-19-33-924.png
Attachment 3: 2024-06-06_07-48-36-884.png
2024-06-06_07-48-36-884.png
Attachment 4: 2024-06-06_07-52-31-343.png
2024-06-06_07-52-31-343.png
Attachment 5: 2024-06-06_07-54-53-972.png
2024-06-06_07-54-53-972.png
Attachment 6: MRC_Parameters_06-06-2024.JPG
MRC_Parameters_06-06-2024.JPG
  30   Fri Jun 7 11:14:04 2024 RodolfoLaserTrigger-signal for MRC
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.
Attachment 1: MRC_TriggerSignal_T1_06-06-2024.jpg
MRC_TriggerSignal_T1_06-06-2024.jpg
Attachment 2: MRC_TriggerSignal_T2_Tmin_06-06-2024.jpg
MRC_TriggerSignal_T2_Tmin_06-06-2024.jpg
Attachment 3: GeneratorSettings_for_MRC_06-06-2024.jpg
GeneratorSettings_for_MRC_06-06-2024.jpg
Attachment 4: MRC_Parameters_06-06-2024_18-30.JPG
MRC_Parameters_06-06-2024_18-30.JPG
  43   Tue Jun 11 21:38:35 2024 Julian, Imke, RodolfoLaserWavemeter HeNe long time stability
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...
Attachment 1: HeNe_LangeMessung_11-06-2024.JPG
HeNe_LangeMessung_11-06-2024.JPG
  51   Wed Jun 12 17:12:13 2024 Julian, Danyal, RodolfoLaserTiming für 229Th89+
We did the timing Ion-Beam Laser-beam time overlap.

The ion revolution frequency (and therefore the bunching frequency) is: 1.5429 MHz.
Attachment 1: Timing_229Th89_12-06-2024.JPG
Timing_229Th89_12-06-2024.JPG
  69   Thu Jun 13 18:23:46 2024 JulianLaserRestarting 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.
  70   Thu Jun 13 18:38:24 2024 Rodolfo Sanchez, Julian Palmes, Sebastian KlammesLaserLaser Dye change - new MRC settings - scraper checks of laser beam
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).
Attachment 1: MRC-settings-13-06-2024-after-dye-change-at-3pm.JPG
MRC-settings-13-06-2024-after-dye-change-at-3pm.JPG
  1   Tue Apr 16 14:42:37 2024 JanGeneralG-PAC Proposal
Attachment 1: G-22-00052.pdf
G-22-00052.pdf G-22-00052.pdf G-22-00052.pdf G-22-00052.pdf G-22-00052.pdf G-22-00052.pdf G-22-00052.pdf G-22-00052.pdf
  2   Tue Apr 16 16:28:21 2024 DanyalGeneralGreat
Thanks Jan!
  6   Wed May 29 10:54:21 2024 Shahab, JanGeneralGas Target Events with new timing system
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
Attachment 1: 2024-05-29_11-07-40-259.png
2024-05-29_11-07-40-259.png
Attachment 2: IMG_0465.JPG
IMG_0465.JPG
Attachment 3: IMG_0466.JPG
IMG_0466.JPG
Attachment 4: IMG_0467.JPG
IMG_0467.JPG
  Draft   Thu Jun 6 07:54:15 2024 DanyalGeneralpressure 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.
  32   Fri Jun 7 17:10:45 2024 SebastianGeneralXUV LED
Maximum XUV LED Voltage: 6.5V
  35   Sat Jun 8 13:11:52 2024 CarstenGeneralPut 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.
  42   Tue Jun 11 21:23:11 2024 Julian, ImkeGeneralHow to read out voltage
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.
Attachment 1: medusa1.JPG
medusa1.JPG
Attachment 2: medusa3.png
medusa3.png
Attachment 3: medusa4.png
medusa4.png
ELOG V3.1.5-fc6679b