HOME ESR EXPERIMENTS LABS etc
E121 E127 E132 E125 E143 laser_cooling_2021 E142 Ê128 E146 E0052 E0018
  Nuclear hyperfine mixing in 229Th89+, Page 1 of 12  Not logged in ELOG logo
ID Date Author Categorydown Subject
  62   Sat Apr 2 01:27:25 2022 Jan GloriusRunstest runs 02.04.2022
Beam settings:
primary beam 
copper stripper
I_el=300mA
U_el=205.490kV (Ohm_labs)
3.5e7 ions at injection


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

Files/Runs [DAQ2]:

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

no corresponding file in DAQ1

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

file in DAQ1:
...7768.lmd

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

file in DAQ1:
...7770.lmd

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

VUPROM -> delay stop trigger ch12 

file in DAQ1:
no file

no laser scan

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

VUPROM -> delay stop trigger ch12 

file in DAQ1:
...7772.lmd
Attachment 1: setting_e142.1648855568
1648855568
Sat Apr  2 01:26:08 CEST 2022
e127pi:mrcc:mscf2:getGainCommon 15
e127pi:mrcc:mscf2:getShapingTimeCommon 0
e127pi:mrcc:mscf2:getThresholdCommon 200
e127pi:mrcc:mscf2:getPzCommon  255
e127pi:mrcc:mscf2:getGain1     15
e127pi:mrcc:mscf2:getGain2     10
e127pi:mrcc:mscf2:getGain3     15
e127pi:mrcc:mscf2:getGain4     15
e127pi:mrcc:mscf2:getShapingTime1 0
e127pi:mrcc:mscf2:getShapingTime2 0
e127pi:mrcc:mscf2:getShapingTime3 0
e127pi:mrcc:mscf2:getShapingTime4 1
e127pi:mrcc:mscf2:getThreshold1 255
e127pi:mrcc:mscf2:getThreshold2 2
e127pi:mrcc:mscf2:getThreshold3 200
e127pi:mrcc:mscf2:getThreshold4 200
e127pi:mrcc:mscf2:getThreshold5 222
e127pi:mrcc:mscf2:getThreshold6 2
e127pi:mrcc:mscf2:getThreshold7 200
e127pi:mrcc:mscf2:getThreshold8 200
e127pi:mrcc:mscf2:getThreshold9 222
e127pi:mrcc:mscf2:getThreshold10 255
e127pi:mrcc:mscf2:getThreshold11 255
e127pi:mrcc:mscf2:getThreshold12 255
e127pi:mrcc:mscf2:getThreshold13 100
e127pi:mrcc:mscf2:getThreshold14 255
e127pi:mrcc:mscf2:getThreshold15 255
e127pi:mrcc:mscf2:getThreshold16 255
e127pi:mrcc:mscf2:getPz1       100
e127pi:mrcc:mscf2:getPz2       100
e127pi:mrcc:mscf2:getPz3       100
e127pi:mrcc:mscf2:getPz4       100
e127pi:mrcc:mscf2:getPz5       100
e127pi:mrcc:mscf2:getPz6       100
e127pi:mrcc:mscf2:getPz7       100
e127pi:mrcc:mscf2:getPz8       100
e127pi:mrcc:mscf2:getPz9       100
e127pi:mrcc:mscf2:getPz10      100
e127pi:mrcc:mscf2:getPz11      100
e127pi:mrcc:mscf2:getPz12      100
e127pi:mrcc:mscf2:getPz13      100
e127pi:mrcc:mscf2:getPz14      100
e127pi:mrcc:mscf2:getPz15      100
e127pi:mrcc:mscf2:getPz16      100
e127pi:mrcc:mscf2:getSingleChMode 1
e127pi:mrcc:mscf2:getRcMode    1
e127pi:mrcc:mscf2:getAutoPZ    18
e127pi:mrcc:mscf2:getMultiplicityHi 8
e127pi:mrcc:mscf2:getMultiplicityLo 0
e127pi:mrcc:mscf2:getSumTrgThresh 18
e127pi:mrcc:mscf2:getBlrOn     1
e127pi:mrcc:mscf2:getCoincTime 121
e127pi:mrcc:mscf2:getThreshOffset 70
e127pi:mrcc:mscf2:getShaperOffset 35
e127pi:mrcc:mscf2:getBlrThresh 25
e127pi:mrcc:mscf2:getECLDelay  18
  78   Sun Apr 3 12:31:10 2022 Rui-Jiu Chen, Yuri, Carsten, RaganRunsMeasurement of beam with different circles
Parameters of NTCAP:

1. IQ rate 20 MSamples/s
2. Carrier frequency: 245 MHz
3. RF attenuation(dB): 40
4. IF attenuation(dB): 19.9288

Data files:
Samples/record: 2^18=262144
Records/File:2^12=4096

Masterpath:
p:/E142/iq
p:/E142/sc


1. Manipulation 1:

(ESR EXP22 02 238U92 Brandau 30March22.C1.3 WAIT FOR MANIP BY. OF O)
Data A: IQ_2022-04-03_11-37-01, SC_2022-04-03_11-37-01
Data B: IQ_2022-04-03_11-46-54, SC_2022-04-03_11-47-04


2. Manipulation 2:

(ESR EXXP22 02.23U92 Brandau SOMarch22.CIS WAIT FOR MANI BY OP O )
Data A: IQ_2022-04-03_11-56-17, SC_2022-04-03_11-56-17 (Reference level 0dBm)
Data B: IQ_2022-04-03_12-03-27, SC_2022-04-03_12-03-27 (Reference level 0dBm)
Data C: IQ_2022-04-03_12-58-00, SC_2022-04-03_12-58-00 (Reference level -25dBm, record data
for long time.)\


3. Manipulation 3:

(ESR EXP22 02 23AUS2 Branda3OMarch22C1.7 WAIT FOR MANIP BY OP)
Data A: IQ_2022-04-03_12-11-11, SC_2022-04-03_12-11-11 (Reference level 0dBm)
Data B: IQ_2022-04-03_12-18-49, SC_2022-04-03_12-18-49 (Reference level 0dBm)


4. Manipulation 1+2+3. Measuring two injections.

Data A: IQ_2022-04-03_12-26-47, SC_2022-04-03_12-26-47(REFERENCEL LEVEL 0dBm)
Data B: IQ_2022-04-03_12-26-55, SC_2022-04-03_12-26-55(Reference level -25dBm)

Preliminary result: comparison between manipulation (MP) 1,2,3 and full manipulation




Attachment 1: 202204031422502.jpg
202204031422502.jpg
Attachment 2: 202204031422501.jpg
202204031422501.jpg
Attachment 3: 20220403142250.jpg
20220403142250.jpg
Attachment 6: Comparison_between_manipulations.pdf
Comparison_between_manipulations.pdf Comparison_between_manipulations.pdf
  86   Mon Apr 4 09:10:44 2022 Ragan, Yuri, Rui-JiuRunsMeasurement
NTCAP is taking data with the beam with a stop at manipulation 5 (taking all the fragments).

1)

Start time: 09:07
Stop time:  11:31

Reference level: -25 dBm

SC_2022-04-04_09-07-57
IQ_2022-04-04_09-07-57

2)

Start time: 11:35
Stop time:  14:00

Reference level: -25 dBm

SC_2022-04-04_11-35-25
IQ_2022-04-04_11-35-25
  104   Tue Apr 5 23:55:11 2022 CarstenRunsLong time measurment with NTCAP
Settings:
Center: 2242.5MHz
RefLevel: -25dB
Rate 15 MIQs

File Numbers: 2022_04_05 23-46-22

Please note that the file started one minute earlier had wrong settings.

File contains also injection, paused in machine #5: ramped to central orbit / not yet bunched.
The measurement does not represent the later settings since here hte 229Th89+ is still on a too inner orbit (cf. previous post).

The beam settings can also be found in the previous post.
  110   Wed Apr 6 14:52:29 2022 RodolfoRunsScraping the ion beam
We are T-scraping the ion beam.
  121   Thu Apr 7 02:32:29 2022 all on shiftRunsFirst Scans 322-320nm
Laser scanning from 322-320 steps 0.01nm/s
DAQ1: lxg1927:/data.local2/BeamTimeTh22/
DAQ2: lxg0155:/data.local2/E142/
LMD file name DAQ1:229Thor
LMD file name DAQ2:229Th

TimeSIS-intensitycooler-HVLMD-DAQ1LMD-DAQ2
02.30??Th227781-Th2277840027-0028
03.031.75e92096487785-77870029-0030
03:281.7e920964877880031 (stopped during scan)
Break - fixing cables, Elog ID: 125
04:00 - problems with UNILAC, stopping for now.
Apparently not so bad problems. we can continue.
Mesytek PS of xuv-detector crashed, can only be restarted from inside the ESR by turning the crate on and off.
05.201.23e92096467791-77940035-0038
05.521.5e92096487795-77970039-0042
06.241.5e92096427798-78000043-0046 1 sec waiting at each laser frequency (dwell time 30)
07.36 xx e9209 xx 7803-78040047-0050 problems with DAQ 1 and DAQ2
07.52 xx e9209646 7805-78090051-0055 DAQs started again 5 sec waiting at each laser frequency (dwell time 150)
08.30 e9209 xx 7810-780056-00 DAQs started again 5 sec waiting at each laser frequency (dwell time 150)
  151   Fri Apr 8 06:53:29 2022 RaganRunsNTCAP data taking
NTCAP is taking data since 07.04.2022 23:53:47

Carrier Frequency: 242.2 M
IQ Rate (S/s): 10 M
Reference level (dBm): -30

SC_2022-04-07_23-53-47
\IQ_2022-04-07_23-53-47
Attachment 1: IMG_0936.jpg
IMG_0936.jpg
  155   Fri Apr 8 09:32:32 2022 RaganRunsNTCAP stopped
Since there is no beam, NTCAP is stopped.

Carrier Frequency: 242.2 M
IQ Rate (S/s): 10 M
Reference level (dBm): -30

SC_2022-04-07_23-53-47
\IQ_2022-04-07_23-53-47
  157   Fri Apr 8 09:39:04 2022 RaganRunsNTCAP started
Carrier Frequency: 242.2 M
IQ Rate (S/s): 10 M
Reference level (dBm): -30

SC_2022-04-08_09-39-33
\IQ_2022-04-08_09-39-33
  158   Fri Apr 8 10:44:55 2022 Ragan, Yuri, Danyal, SergeyRunsNTCAP stopped
NTCAP is stopped. Sergey will now set an ion bunch instead of two in the ESR.

SC_2022-04-08_09-39-33
\IQ_2022-04-08_09-39-33
  161   Fri Apr 8 12:04:13 2022 RaganRunsNTCAP started
NTCAP is started for the data taking.

Carrier Frequency: 242.02 M
IQ Rate (S/s): 10 M
Reference level (dBm): -30

SC_2022-04-08_12-04-28
\IQ_2022-04-08_12-03-50
Attachment 1: IMG_0947.jpg
IMG_0947.jpg
  166   Fri Apr 8 15:39:36 2022 allRunsfirst data after timing set up
started taking data again

started at 15:40  
h=1  

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

stopped at 16:25 


The laser was not really properly scanned. 
This was mainly a test run to see if everything was working. 
  181   Sat Apr 9 06:25:22 2022 Max, KristianRunsmorning shift runs
DAQ1: lxg1927:/data.local2/BeamTimeTh22/
DAQ2: lxg0155:/data.local2/E142/
LMD file name DAQ1:229Thor
LMD file name DAQ2:229Th

Shottky marker pos: 243.973MHz

TimeSIS-intensitycooler-HVLMD-DAQ1 start-endLMD-DAQ2 start-endscan range(nm)step width(nm)dwell time(s)comments
xx:xxx.xe9209xxx00xx78xx32x.x - 32x.x0.01xsketch for filling the table
06:401.7e92096190098-00997836323.2 - 321.20.0024slaser pulse energy is @ ~12mJ after SHG
09:351.4e92096240101-01017838-7838323.2 - 322.80.0023sonly 0.5nm range, WM power + coupling tuned to scan range, Konstantin updated LV code to hold Cobra Set WL value, aborted LV readout problem
11:251.0e92096220102 - 1027839-7839323.2 - 322.80.0023sLV readout problem solved. WM readout is wrong (Cobra set is good)
12:15old beam2096220103 - 1037840-7840323.2 - 322.80.0023s WM readout is wrong
12:502.3e92096170104 - 1047841-7841323.2 - 322.80.0023s couldnt open go4 stream view, stopped after one good scan
13:202.0e92096170104 - 1057842-7842323.2 - 322.80.0023s first scan with LV correct
  183   Sat Apr 9 13:45:42 2022 Max, KristianRunsfirst scans with LV problem solved!
This is the first time with LV buffer problem solved (see Elog ID: 184). Before the PMT signals were out of sync with the wavelength data!
We concluded to scan with step sizes of 0.002nm, scan range of 0.5nm (f
nm), dwelltime = 150(5s), loops = 2 (approx.: 30min measurements).

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

Shottky marker pos: 243.973MHz

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


Runs after this have the right cobra set value but propably the wrong WM data until 10.04.22 12:44 (see also ID:198)
  185   Sat Apr 9 15:47:21 2022 Carsten, Rodolfo, Sarper, PatrickRunsAfternoon 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


TimeSIS-intensitycooler-HVLMD-DAQ1 start-endLMD-DAQ2 start-endscan range(nm)step width(nm)dwell time(s)comments
xx:xxx.xe9209xxx0xxx78xx32x.x - 32x.x0.002xsketch for filling the table
15:141.5e92096240111-01117847-7847323.2 - 322.80.0025s DAQ 2 no VUPROM TDC Pat south
xx:xx1.5e92096240111-01117847-7847323.2 - 322.80.0025s DAQ 2 changed TDC part south from ch 8 to ch 10
17:052.2e92096240113-01137848-7848323.2 - 322.80.0025s successful scan
19:041.8e92096160116-0116 7850-7850 323.2 - 322.80.0025s 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:491.8e92096140117-0117 7851-7851 323.2 - 322.80.0025s successful scan
20:282.0e92096220118-0118 7852-7852 323.2 - 322.80.0025s successful scan
21:072.2e92096230119-119 7853-7853 323.2 - 322.80.0025s successful scan
22:011.8e92096210122-0122 7856-7856 323.2 - 322.80.0025s successful scan
22:41?20962001237857323.2 - 322.80.0025s First scan started by night shift
23:211.1e920962001247858323.2 - 322.80.0025s mbs crashed at 'sta ac'
23:321.3e920961801257859323.2 - 322.80.0025s e-cooler turned off
23:501.5e9209xxx01267860323.2 - 322.80.0025s the stop point was not set
23:531.5e920961101277861323.2 - 322.80.0025s DAQ2 must have crashed between 23:30 - 23:50
00:071.9e9209xxx01287862323.2 - 322.80.0025s mbs crashed at 'sta ac'
00:231.7e920962301317864323.2 - 322.80.0025s successful scan. we 'resl' after every measurement from now on. 'open file' is included in '@startup' now (ID:190).
01:081.6e920962301327865323.2 - 322.80.0025s successful scan
01:471.6e920962301337866323.2 - 322.80.0025s successful scan
02:351.3e920962301347868323.2 - 322.80.0025s successful scan
03:192.0e920962201357869323.2 - 322.80.0025s successful scan
04:041.3e920962201367870323.2 - 322.80.0025s successful scan
04:441.0e920962201377871323.2 - 322.80.0025s e-cooler turned off
05:251.9e920962201407875323.2 - 322.80.0025s 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)
  195   Sun Apr 10 06:39:16 2022 Kristian, Marek, MaxRunsruns morning shift 10.04.
These are the measurement runs of the morning shift (10.04.).


TimeSIS-intensitycooler-HVLMD-DAQ1 start-endLMD-DAQ2 start-endscan range(nm)step width(nm)dwell time(s)comments
06:xx3e82096xx0141-01417876-7876323.2 - 322.80.0025sjust one loop
06:392e92096210142-01427877-7877323.2 - 322.80.0025s
07:182.1e92096160143-01437878-7878323.2 - 322.80.0025s 8000 particles on counter
07:572.2e92096210144-01447879-7879323.2 - 322.80.0025s
08:371.9e92096200145-01457880-7880323.2 - 322.80.0025s 7200 particles on counter
09:242.1e92096210146-01467881-7881323.2 - 322.80.0025s laser pulse energy @ start of run: 488mJ green monitor, 11.6mJ UV, 7700 particles on counte
10:072.1e92096200147-01477882-7882323.2 - 322.80.0025s optimized WM coupling, the WM data is stretched in this run (buffer problem?), also possible for previous runs
11:042.1e92096200148-01487884-7884323.2 - 322.80.0025s restarted WM, still wrong WM data, stopped after 1 run
11:272.1e92096160149-01497885-7885323.2 - 322.80.0025s restarted WM + LV
12:112.0e92096160150-01507886-7886323.2 - 322.80.0025s wrong WM data
12:551.9e92096160151-01517887-7887323.2 - 322.80.0025s changed LV code (ID: 198), WM data works now!
13:371.8e92096200152-01527888-7888323.2 - 322.80.0025s
14:162.1e92096210153-01537889-7889323.2 - 322.80.0025s1 loop
  200   Sun Apr 10 15:16:19 2022 Carsten, Rodolfo, SarperRunsRuns 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.


TimeSIS-intensitycooler-HVLMD-DAQ1 start-endLMD-DAQ2 start-endscan range(nm)step width(nm)dwell time(s)comments
16:261.95e92096200155-01557891-7891322.81 - 322.400.0025slaser scan did not work, labview (Thorium_main.vi) communication issue
16:511.8e92096200156-01567892-7892322.81 - 322.400.0025s
17:331.6e92096180157-01577893-7893322.81 - 322.400.0025s 7894 particles on the counter
18:171.6e92096180158-01587894-7894322.81 - 322.400.0025s 8200 particles on the counter
19:061.8e92096180159-01597895-7895322.81 - 322.400.0025s 8650 particles on the counter
19:441.9e92096180160-01607896-7896322.81 - 322.400.0025s 8600 particles on the counter
20:241.7e92096200161-01617897-7897322.81 - 322.400.0025s 4200 particles on the counter
21:041.7e92096190162-01627898-7898322.81 - 322.400.0025s 8380 particles on the counter
21:451.8e92096190163-01637899-7899322.81 - 322.400.0025s 8550 particles on the counter
22:241.8e92096190164-01647900-7900322.81 - 322.400.0025s 8016 particles on the counter
  203   Sun Apr 10 22:47:05 2022 Patrick, Volker, Prannay, Danyal, Alexandre, Sebastian, KristianRunsRuns 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.


TimeSIS-intensitycooler-HVLMD-DAQ1 start-endLMD-DAQ2 start-endscan range(nm)step width(nm)dwell time(s)particles countedcomments
23:05 1.75e92096200165 - 01657901-7901322.81 - 322.400.0025s8500
23:57 1.?e92096200166 - 01667902-7902322.81 - 322.400.0025s8500The HV of PMT south was changed from 2.5kV to 3kV
00:35 1.4e92096200167 - 01677903-7903322.81 - 322.400.0025s4100
01:18 1.75e92096200168 - 01687904-7904322.81 - 322.400.0025s4400
01:58 1.4e92096200169 - 01697905-7905322.81 - 322.400.0025s7700 The ESR went red after this run. The on-call service was called because of some power supply failure, ETA: 45min.
04:12 1.75e92096200171 - 01717906-7906322.81 - 322.400.0025s7600 With the start of this run, the wavemeter, labview and the python script were restarted. The python script was slightly adjusted.
04:50 1.6e92096200172 - 01727907-7907322.81 - 322.400.0025s8300
05:31 1.6e92096190173 - 01737908-7908322.81 - 322.400.0025s8100
06:09 1.6e92096150174 - 01747909-7909322.81 - 322.400.0025s 8000
06:52 1.8e92096150175 - 01757910-7910322.81 - 322.400.0025s8800 at 07:08 the cooler voltage jumped from 209615 V to 209619 V
07:30 1.9e92096190176 - 01767911-7911322.81 - 322.400.0025s forgotten at 07:50 the cooler voltage jumped from 209619 to 209610 V and back again at to 209619 V
08:18 1.8e92096190177 - 01777912-7912322.81 - 322.400.0025s 9100 08:47 the cooler voltage jumped from 209618 to 209614 V and back again at to 209618 V
08:55 1.75e92096190178 - 01787913-7913322.81 - 322.400.0025s 8300
09:36 1.6e92096190179 - 01797914-7914322.81 - 322.400.0025s 8194


The SIS intensity is taken directly before injection to ESR. Not the SIS peak intensity as in yesterday's table.
  210   Mon Apr 11 14:45:11 2022 Paul, Konstantin, Sarper, DavidRunsAfternoon shift runs 11.04
We continue scan the new wavelength scan range is 322.41 - 322.00 nm



TimeSIS-intensitycooler-HVLMD-DAQ1 file nr LMD-DAQ2 file nr scan range(nm)step width(nm)dwell time(s)particles countedcomments
14:45 1.9e9 209618 0189 7924 322.41 - 322.00 0.002 5s 9100
18:54 1.83e9 209616 0191 7926 322.41 - 322.00 0.002 5s 7300
19:34 1.7e9 209615 0192 7927 322.41 - 322.00 0.002 5s 7110
20:13 1.8e9 20961X 0193 7928 322.41 - 322.00 0.002 5s 6730
20:53 1.8e9 209614 0194 7929 322.41 - 322.00 0.002 5s 7550 During the scan the ecooler voltage changed to approximately 209613
21:43 1.7e9 209614 0195 7931 322.41 - 322.00 0.002 5s 7000
22:30 1.6e9 209612 0197 7932 322.41 - 322.00 0.002 5s 7300
23:10 1.4e9 209614 0198 7933 322.41 - 322.00 0.002 5s 6100 For this measurement, ESR_Ring went red, we realized only after completing the measurement. The sections went red are Dipole Correction Points (GE01KP17-18-19-20, 4 in total) @~23:45 and fixed @01:35...
01:52 1.6e9 209614 0199 7934 322.41 - 322.00 0.002 5s 7151
02:32 1.7e9 209616 0200 7935 322.41 - 322.00 0.002 5s 8368
03:22 1.8e9 209617 0201 7936 322.41 - 322.00 0.002 5s 7005
04:01 1.9e9 209616 0202 7937 322.41 - 322.00 0.002 5s Ecooler voltage increased 4 volts during the run
  215   Tue Apr 12 04:43:29 2022 Alexandre, Kristian, SebastianRuns322.01 - 321.60 nm
We scan the wavelength scan range is 322.01 - 321.60 nm

before the first scan of the new wavelength range we changed the high voltage divider ratio in Labview from 248514 to 248517, which is the correct value for this voltage. This leads to slightly higher cooler voltages in the log.

TimeSIS-intensitycooler-HVLMD-DAQ2 file nr LMD-DAQ1 file nr scan range(nm)step width(nm)dwell time(s)particles countedcomments
04:40 1.9e9 209625 0203 7938 322.01 - 321.60 0.002 5s 8830
05:20 1.7e9 209626 0204 7939 322.01 - 321.60 0.002 5s 7800
06:00 1.6e9 209626 0205 7940 322.01 - 321.60 0.002 5s 8500
06:45 1.7e9 209620 0206 7941 322.01 - 321.60 0.002 5s 9400 cooler HV decreased slowly by a few V, jumped back at ~7:03
07:25 1.8e9 209620 0207 7942 322.01 - 321.60 0.002 5s 9300
08:05 1.75e9 209620 0208 7943 322.01 - 321.60 0.002 5s 9100
08:45 1.7e9 209618 0209 7944 322.01 - 321.60 0.002 5s 9000 cooler HV decreased 5V to 209614 and jumped back to initial value after ~5s
09:25 1.7e9 209618 0210 7945 322.01 - 321.60 0.002 5s 8500
10:05 1.9e9 209618 0211 7946 322.01 - 321.60 0.002 5s 9200 cooler HV decreased steadily to 209611 V during the run
10:45 1.9e9 209611 0212 7947 322.01 - 321.60 0.002 5s 7500 After injecting into the ESR, we saw after cooling some tails left and right of the Shottky peak of Th. Was not there in the runs before. After some minutes it disappeared in the spectrum
11:35 2e9 209611 0213 7948 322.01 - 321.60 0.002 5s it seems to be that much lesser ions are stored in the ESR - counter shows low rate - ABORTED laser didn't start scanning
11:58 1.75e9 209615 0214 7949 322.01 - 321.60 0.002 5s 7700 cooler HV jumped to 209610 at 12:12 and stayed there
12:53 1.85e9 209611 0215 7950 322.01 - 321.60 0.002 5s 7155 cooler HV increased slowly from initial value to ~209618
13:32 1.9e9 209612 0216 7951 322.01 - 321.60 0.002 5s 6638
14:39 1.8e9 209610 0217 7952 322.01 - 321.60 0.002 5s 6815 Voltage was jumping around from 209610 up to 209624 and back
15:20 1.75e9 209612 0218 7953 322.01 - 321.60 0.002 5s 8400 In contrast to the previous measurement, the cooler voltage was drifting by about 3V around 209612
16:00 1.7e9 209612 0219 7954 322.01 - 321.60 0.002 5s 7920
16:58 1.5e9 209612 0220 7955 322.01 - 321.60 0.002 5s 4577 PMT North voltage and threshold modified Entry 221, Ecooler voltage dcreased to 209609 V, weak injection
18:09 1.62e9 209609 0221 7957 322.01 - 321.60 0.002 5s During the last injection the beam suddenly got lost during the scraping, File 7956 was discarded since go4 was still during the startup of mbs
18:49 1.69e9 209609 0222 7958 322.01 - 321.60 0.002 5s 6133
19:49 1.6e9 209610 0223 7959 322.01 - 321.60 0.002 5s 7035
20:29 1.78e9 209611 0224 7960 322.01 - 321.60 0.002 5s 4490
21:12 1.86e9 209622 0225 7961 322.01 - 321.60 0.002 5s 10296 Note that the cooler voltage is increased. Particle number might be overestimated since it was read when the beam was already dumped.
Attachment 1: DriftingVoltage14-40.PNG
DriftingVoltage14-40.PNG
ELOG V3.1.5-fc6679b