 Sat Apr 9 03:46:31 2022, Carsten, Accelerator, Slits in TE line
|
Changed GTEDSAH Rechts to 10mm |
Sat Apr 9 03:27:47 2022, Patrick, DAQ, Laser scanning 
|
DAQ1: lxg1927:/data.local2/BeamTimeTh22/
DAQ2: lxg0155:/data.local2/E142/
LMD file name DAQ1:229Thor
LMD file name DAQ2:229Th
Shottky marker pos: 243.973MHz
|
Time | SIS-intensity | cooler-HV | LMD-DAQ1 | LMD-DAQ2 | scan range(nm) | step width(nm) | dwell time(s) | comments
| |
xx:xx | x.xe9 | 209xxx | 00xx | 78xx | 32x.x - 32x.x | 0.01 | x | sketch for filling the table
| |
04:13 | 1.4e9 | 209614 | 0093 | 7831 | 323.2 - 321.2 | 0.01 | 4 | First laser scan this night shift
| |
04:46 | 1.3e9 | 209616 | 0094 | 7832 | 323.2 - 321.2 | 0.01 | 4 |
| |
05:17 | 1.0e9 | 209617 | 0095 | 7833 | 323.2 - 321.2 | 0.01 | 4 | The laser left the screen between the two loops
| |
05:54 | 1.5e9 | 209619 | 0097 | 7835 | 323.2 - 321.2 | 0.01 | 4 | go4 on DAQ2 does not show any events. mbs does not write to file although it is OPEN and the acq is RUNNING
|
|
|
Sat Apr 9 02:55:38 2022, Carsten, Accelerator, Kühlerausfall und Gründe dazu
|
Wir hatten heute Abend eine Kühlerausfall, der uns mehrere Stunden beschäftigt hat, weil gem. Anzeige in Device Control kein Netzteil mit „rot“ angezeigt/ausgefallen war (siehe unten).
Nach Rufbereitschaft Serge, dann Regina sowie Controls konnte zunächst gefunden werden, dass das Netzteil einer Clearingelektrode (GECEKD2D) keinen korrekten Wert hat. Problem mittels Operateur (Christoph ?) und Rufbereitschaft Contrls gelöst.
Kühler ist trotzdem jedes Mal ausgefallen, wenn man versucht hat, auch nur den geringsten Strom zu ziehen (mit Hilfe Telefonunterstüzung Regina).
Rufbereitschaft Jon.
Mit ihm haben wir dann herausgefunden, dass im Device-Control, bei Auswahl „Kühler“ UND wenn das Fenster nicht vollständig maximiert ist, die letzten drei Netzteile (ECEBG8T, ECEBG3D, ECEBG4D) nicht angezeigt werden und man auch den Scrollbalken nicht dorthin bewegen kann (ergo: nicht vorhanden sind…). Ist das Fenster von DC maximiert, tauche die Geräte wieder auf und ACH WUNDER ECEBG8T (Kollektor) ist rot, lässt sich einfach wieder zuschalten und auch der Rest wieder anschalten. Ein Fehler, den ich leicht hätte selber beheben können, wenn er denn nur angezeigt worden wäre.
Soll heißen: Man weiß zwar, das irgendwo ein Fehler ist, kriegt aber in diesem Modus das Gerät gar nicht angezeigt… |
|
Fri Apr 8 23:56:07 2022, Patrick, DAQ, DAQ improvement
|
As requested in ID:146 and ID:147, the laserscan tab was improved:
- The laserscan tab shows each observable plotted against the predefined wavelength setpoints now.
- The Kobra set wavelength shows the actual setpoints now and not measured wavelengths.
Note: The bins of the laserscan histograms are defined in TLdaAnlProc.cxx, lines 140-142.
At the moment, the histograms are set up for scans in the range 320 - 325 nm and step sizes of 0.01 nm.
If the step size changes or scans that exceed this range are required, these parameters should be adjusted.
Remember to add or subtract half of the step size to your min. and max. wavelength to prevent binning artifacts.
Then of course, also only scan wavelengths which are multiples of your step size. |
|
Fri Apr 8 22:26:44 2022, Patrick, DAQ, Spike in all detectors
|
In the previous shift, there was a spike in all detectors in the same scan step. Apparently, this was NOT a resonance since in the next step it appeared again but at a different wavelength.
The current hypothesis is, that this is a disruption signal from one of the machines. |
|
Fri Apr 8 17:57:45 2022, Konstantin, DAQ, Laser scanning
|
|
Time | SIS-intensity | cooler-HV | LMD-DAQ1 (R4L-68) | LMD-DAQ2 (R4L-41) | scan range (nm) | step width(nm) | dwell time(s) | comments
| |
17:28 | 1.1e9 | - | 0083 | 7822 | 322.3-321.3 | 0.01 | 4 | Wrong scan range
| |
17:48 | 1.4e9 | 209618 | 0084 | 7823 | 322.3-321.3 | 0.01 | 4 | Wrong scan range
| |
18:10 | 1.6e9 | - | 0085 | 7824 | 323.2-321.2 | 0.01 | 4 | acquisition on r4l-68 crashed
| |
18:13 | 2e9 | - | 0086 | - | 323.2-321.2 | 0.01 | 4 | acquisition on r4l-41 crashed
| |
18:29 | 1.9e9 | 209618 | 0087 | 7826 | 323.2-321.2 | 0.01 | 4 | An artifact is observed at about 644nm <-> 322nm fundamental wavelength
| |
20:17 | 2e9 | 209609 | 0089 | 7827 | 323.2-321.2 | 0.01 | 4 | Cu-mirror and XUV detector are not driven at the moment. It is unclear for how long this was the case. Optimization of the accelerator settings were done before.
| |
21:12 | 1.6e9 | - | 0089 | 7828 | 323.2-321.2 | 0.01 | 4 | Laser got wrong pulse widths during this scan and also during the last one.
|
At about 20:00 the slits were adjusted to the h=1 settings:
NI: 5mm
NA: -3mm
SA: -10mm (also the voltage for the Scitnilator in this pocket was increased to 1500V)
SA_Scraper: +14mm |
|
Fri Apr 8 17:44:25 2022, Konstantin, Calibration, Final Timing
|
We measured the timing for the laser bunch synchronization. A summary is given below.
|
detector | time till common stop [bins] | time till common stop [ns]
| |
PD North | 28 | 93.33 | |
PD South | 63 | 210 | |
Particle Detector South | 14 | 46.67 | |
Particle Detector North | 94 | 313.33 | |
PMT middle | 119 | 396.67
|
Using all numbers, the difference between the center of the photodiodes and PMT middle is
given by 245ns, which corresponds to the half revolution period of 256 ns. Difference between the
center of both photodiodes and particle detector south is given by 105 ns.
The delay for the laser trigger is now set correctly. |
|
Fri Apr 8 15:45:24 2022, YL, , Spectrum manipulation 5
|
See attached |
|
Fri Apr 8 15:42:20 2022, Yuri, Accelerator, Slits in the TE line
|
At around 15:00, The slits in the TE line were changed to :
TE4DS5HL -12 mm -> -20 mm
TE5DSAH 0 mm -> +15 mm |
|
Fri Apr 8 15:39:36 2022, all, Runs, first 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. |
|
Fri Apr 8 14:46:02 2022, Danyal & Sebastian & Volker & Ken, Detectors, high dark countrate Cu PMT solved
|
The problem - "discovered" by Volker and Ken - of the high dark countrate of the Cu PMT has been solved.
(when the Cu mirror was moved in, the dark countrate was very high ... also without ion beam)
I asked Graziano Savino to check the vacuum gauges along the target side of the ESR (west side).
The gauges at the laser window sections (which we do not use here!) - NW and SW - were still on.
Volker remembered that, in the past, for the lowest dark countrate at the Cu PMT --> ALL GAUGES MUST BE SWITCHED OFF.
Graziano turned them off and Sebastian and I checked the Cu PMT rate in DAQ1.
Attached you can clearly see the difference: from 7500 cps to 400 cps.
When the Cu mirror is retracted the dark countrate is 200 cps.
Danyal
PS The slow increase in one plot is due to the fact that Graziano switched on the light in the ESR. |
|
Fri Apr 8 14:43:50 2022, Wilfried, DAQ, laser timing - Q-switch start
|
below are my notes concerning laser timing / Q-switch start |
|
Fri Apr 8 14:14:28 2022, Kristian, DAQ, Delay of bunch RF
|
The bunch HF is now fed through a delay to shift the stop trigger relative to the PMT signal. The delay generator is placed directly after the CFG and before splitting the signal for the two DAQs. The relative timing of both DAQs was not changed. |
|
Fri Apr 8 14:12:57 2022, morning shift, DAQ, timing for h=1
|
The timing for h=1 has been set up
The time window is now twice as large as before!
This means that we see the same ion bunch twice.
(150 bins = 1 turn in the ESR)
The PMT signal is exactly in between two cycles + the extra flight time (3 bins = 10 ns) from target to PMT north. |
|
Fri Apr 8 12:04:13 2022, Ragan, Runs, NTCAP 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 |
|
Fri Apr 8 11:16:57 2022, Kristian, Laser, Wavemeter
|
We changed the fiber to the wavemeter. The third fiber worked best and we could operate the WM at low exposure times, i.e., below the laser repetition rate. We used the neutral density filter to adapt the laser power that only one laser pulse is measured by the WM each time (Exposure time =34ms)
This way, there are no frequency jumps. The jitter is slighly different at each wavelength which was ~5GHz peak to peak.
We optimized the fiber coupler and slightly optimized the jitter to <4GHz. |
|
Fri Apr 8 11:02:04 2022, DW, YL, RSS, SL, , Change h=2 to h=1
|
After changing to h=1
The frequency manipulation #5: f=242.021487MHz (124th harmonic) [no bunching]
Manipulation #7: f=242.021812 MHz [with bunching] |
|
Fri Apr 8 10:44:55 2022, Ragan, Yuri, Danyal, Sergey, Runs, NTCAP 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 |
|
Fri Apr 8 09:39:04 2022, Ragan, Runs, NTCAP 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 |
|
Fri Apr 8 09:33:52 2022, Dayshift 1 8.4.2022, , Reference Measurements
|
DAQ1: lxg1297:/data.local2/BeamTimeTh22/
DAQ2: lxg0155:/data.local2/E142/
LMD file name DAQ1:229Thor
LMD file name DAQ2:229Th
center freq. 242.2M, 10MIQs, -30dBm
Shottky marker pos: 243.973MHz
|
Time | SIS-intensity | cooler-HV | LMD-DAQ1 | LMD-DAQ2 | scan range(nm) | step width(nm) | dwell time(s) | comments
| |
09:30 | ?? | 209614 | 0079 | 7817 | 323.2-321.2 | 0.01 | 4 | 2 loops
| |
10:15 | 2.3e9 | 209611 | 0081 | 7820 | 321.0-320.0 | 0.01 | 8 | just 1 loop, aborted 2nd loop and started from 320.5-320.4 in 0.005 steps and 10s dwell time (300), started again from 320.5-320.4 in 0.005 steps and 10s dwell time (300)
|
We crosschecked the last measurements from the nightshift for reference measurements.
Now the ESR group start switching to 1 bunch. |