 Thu Apr 7 05:23:50 2022, Patrick, DAQ, How To Start MBS for DAQ2 (Carstens DAQ)
|
(MBS server should be running at the LXG0155 machine. If not you will get an error message. Then start the server - last command in console)
Just enter the following commands in the console of any PC
ssh stoe_exp@r4l-68
*** Password on a sheet of paper ***
resl
cd /esr/usr/stoe_exp/E142Brandau/SCA... (auto complete with tab)
mbs
@startup
connect rfio lxg0155 -disk
open file lxg0155:/data.local2/E142/229Th -auto -rfio
sta ac
To stop MBS enter the following commands
sto ac
close file
disconnect rfio
@shutdown
exit
resl |
|
Fri Apr 8 00:06:37 2022, Patrick, Laser, Connection to the laser pc
|
To login to the laser pc use the command
xfreerdp -g 1920x1080 -u atplaser atppc023.campus.gsi.de |
Fri Apr 8 01:48:57 2022, Patrick, DAQ, Bugged Trending plots? 
|
The wavelengths/frequencies shown in the graph in the labview window do not match the wavelengths/frequencies in go4.
Compare the picture which shows an incomplete laser scan although the scans in the labview window are completed (The measurement was started at an 'elapsed MBS time' of 2700s and took 1700s/28min).
However, the displayed time is correct. Only the data seems to be "stretched".
The same is true for the 'XUV anode' detector. The counter in the electronic module is ahead of the displayed count rate in go4.
Additional Note: The 'Cobra set wavelength' plot shows wavelengths which seem to be measured. However, we would expect deterministic setpoints from the software, see picture. |
|
Fri Apr 8 03:54:39 2022, Patrick, Laser, Q-switch window
|
The solution of increasing the Q-switch window from 2us to 5us described in ID:148 fulfills its purpose, but the window is unstable.
We saw the laser jumping across the screen which was because the Laser had a lot of hickups.
The hickups come from the signal which determines the duration of the window.
This window "flickers". It gets very small, leaving no time for coincident events which fire the laser.
This is probably an issue with the NIM module.
Compare the picture below: The oscilloscope freezes and only the first of the yellow pulses is visible which should repeat and span 5us at the moment.
After looking at the different signals to trigger the laser on the oscilloscope, the laser does not fire anymore when used in the external trigger mode.
However, all signals are looking good and everything should be in the same state as before.
The internal Q-switch works as good as before. |
|
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 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. |
|
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 04:40:01 2022, Patrick, DAQ, Bugged Trending plots?
|
| The problem from yesterday (ID:147) still persists. All the plots (not only the labview stuff) comes in too late in go4. However, the time axis is correct, see picture. |
|
Sat Apr 9 05:26:25 2022, Patrick, Laser, Wavemeter
|
| The wavemeter still shows large spikes from time to time. The exposure time is still at 34ms. |
|
Sun Apr 10 02:20:17 2022, Patrick, DAQ, New mbs startup guide
|
Connecting to the rfio server and opening a file is included in '@startup' now. Since mbs crashes reliably every 3 or 4 runs, it may be preferable to use the following procedure (which did not crash yet):
|
| DAQ1 | DAQ2
| |
1 | ssh atplaser@r4l-41 | ssh stoe_exp@r4l-68
| |
2 | ThE142_2022 | see ID:179
| |
3 | cd mbsrun/th22 | cd mbsrun/th22cd /esr/usr/stoe_exp/E142Brandau/SCA... (auto complete with tab)
| |
// loop start | |
| |
4 | resl | resl
| |
5 | mbs | mbs
| |
6 | @startup | @startup
| |
7 | // connect go4 | // connect go4
| |
8 | sta ac | sta ac
| |
9 | // measure | // measure
| |
10 | sto ac | sto ac
| |
11 | clo fi | clo fi
| |
12 | exit | exit
| |
13 | // disconnect go4 | // disconnect go4
| |
14 | // go to step 4 | // go to step 4
|
Note: At least in DAQ1, step 13 is necessary to be able to reconnect mbs to the rfio server. |
|
Sun Apr 10 04:07:53 2022, Patrick, DAQ, go4 shows wrong frequencies and wavelengths
|
Update (ID:194): In labview "Stop All", close labview, stop python script (ID:197), close wavemeter. Then restart wavemeter, python script, labview an mbs.
Both labview and the wavemeter software are displaying the scanned wavelength correctly (Fig. 1 & 2), but go4 shows something which looks just like a freely drifting wavelength (Fig. 3).
The Cobra set voltages are displayed correctly. |
|
Sun Apr 10 04:37:29 2022, Patrick, DAQ, Next wavelength range
|
Measurements with the next wavelength scan range should be started roughly around 12:00 noon. The plan is to go to lower wavelengths / higher energies.
So the next wavelength scan range would be 322.81 - 322.4 nm, again with a step size of 0.002 nm and 5s dwell time.
In the picture below you find some calculations/estimates for the current scan range. |
|
Mon Apr 11 04:26:53 2022, Patrick, DAQ, Next wavelength range
|
Measurements with the next wavelength scan range should be started roughly around 10:00 am.
The next wavelength scan range is planned to be 322.41 - 322.00 nm, again with a step size of 0.002 nm, 5s dwell time and 2 loops.
This range includes roughly a third of the first scan range. |
|
Thu Apr 7 22:18:06 2022, Night shift 7.4-8.4, , Next scans
|
DAQ1: lxg1927:/data.local2/BeamTimeTh22/
DAQ2: lxg0155:/data.local2/E142/
LMD file name DAQ1:229Thor
LMD file name DAQ2:229Th
Shottky and NTCAP started at 23:53, 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
| |
00:20 | 1.4e9 | 209617 | 0065-0067 | 7810 | 323.2-321.2 | 0.01 | 4 | buggy DAQ? see Elog, file 0068 empty
| |
01:27 | 1.6e9 | 209606 | 0069-0070 | 7811 | 323.2-321.2 | 0.01 | 4 | buggy DAQ? see Elog, file 0071 empty
| |
02:15 | 1.6e9 | 209611 | 0072-0073 | 7812 | 323.2-321.2 | 0.01 | 4 | buggy DAQ? see Elog, file 0074-0075, 7813-7814 empty
| |
03:00 | 1.1e9 | ? | 0076-0077 | 7815 | 323.2-321.2 | 0.01 | 4 | buggy DAQ? see Elog and below, file 0078, 7816 empty
|
We were searching for a difference of a factor of twoin both DAQs. It turns out that the default value for the MBSstream server task is scale=2. In the main task this value is explicately set to scale=1. we will now (starting with filenumber: 0078) restart the 2nd DAQ with set stream_serv scale=1.
Also TDC is disabled.
From file number 0076 in DAQ2 : ADC thresholds:
unsigned short caen_V785AH_threshold_mod0 [32] =
{0x0100 , 0x0005 , 0x0004 , 0x0003 , 0x0004 , 0x0003 , 0x0005 , 0x0003 ,
0x0005 , 0x0004 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 ,
0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 ,
0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 , 0x0100 };
Before the next scan, we realized, that the laser destabilized. For the rest of the shift we tried to get laser back online (see ID:149). |
|
Wed Apr 6 13:32:57 2022, Max, Sebastian, DAQ, LabView Cobra Channel List
|
channel 0: linux time (epoch time)
channel 1: ms timer
channel 2: E-Cooler Voltage(Ohmlabs)
channel 3: Cobra Set Wavelength
channel 4: WS7 wavelength
channel 5: WS7 frequency
channel 6: WS7 status
channel 7: Status keysight (?)
channel 8: WS7 pressure (?)
channel 9: CobraMotorPosUpperPart
channel 10: CobraMotorPosLowerPart
channel 11: CobraNumberOfLoop
channel 12: StatusCobra
channel 13: WS7 temperature (?)
channel 14: CobraFromWavelength (higher wavelength)
channel 15: CobraToWavelength (lower wavelength)
channel 16: CobraIncrement
channel 17: CobraStepNr
channel 18: status?
channel 19: PTB divider (not connected to cooler)
channel 20: ?
|
|
Thu Apr 7 11:11:31 2022, Max, Sebastian, Laser, dye changed, pulse energy measurements
|
We changed the dye at 10am.
We increased the pump power for the dye Laser to 480mJ (before 450mJ). New calibration factor is 29 for Quanta Ray monitor signal.
We get now 17mJ UV pulse energy after SHG. Pulse energy before was 14mJ. |
|
Thu Apr 14 06:29:18 2022, Max, Sebastian, Accelerator, lesser ESR injection intensity
|
We now have less ESR injection intensity (see screenshot attached).
This can also be seen in the count rate after "UNILAC/SIS failures".
Before failure: ~7k-8k
Now: 3k
The stored particles in the SIS are only in the range between 1.4 and 1.7e9 |
|
Sat Apr 9 06:25:22 2022, Max, Kristian, Runs, morning shift runs
|
DAQ1: lxg1927:/data.local2/BeamTimeTh22/
DAQ2: lxg0155:/data.local2/E142/
LMD file name DAQ1:229Thor
LMD file name DAQ2:229Th
Shottky marker pos: 243.973MHz
|
Time | SIS-intensity | cooler-HV | LMD-DAQ1 start-end | LMD-DAQ2 start-end | scan range(nm) | step width(nm) | dwell time(s) | comments
| |
xx:xx | x.xe9 | 209xxx | 00xx | 78xx | 32x.x - 32x.x | 0.01 | x | sketch for filling the table
| |
06:40 | 1.7e9 | 209619 | 0098-0099 | 7836 | 323.2 - 321.2 | 0.002 | 4s | laser pulse energy is @ ~12mJ after SHG
| |
09:35 | 1.4e9 | 209624 | 0101-0101 | 7838-7838 | 323.2 - 322.8 | 0.002 | 3s | only 0.5nm range, WM power + coupling tuned to scan range, Konstantin updated LV code to hold Cobra Set WL value, aborted LV readout problem
| |
11:25 | 1.0e9 | 209622 | 0102 - 102 | 7839-7839 | 323.2 - 322.8 | 0.002 | 3s | LV readout problem solved. WM readout is wrong (Cobra set is good)
| |
12:15 | old beam | 209622 | 0103 - 103 | 7840-7840 | 323.2 - 322.8 | 0.002 | 3s | WM readout is wrong
| |
12:50 | 2.3e9 | 209617 | 0104 - 104 | 7841-7841 | 323.2 - 322.8 | 0.002 | 3s | couldnt open go4 stream view, stopped after one good scan
| |
13:20 | 2.0e9 | 209617 | 0104 - 105 | 7842-7842 | 323.2 - 322.8 | 0.002 | 3s | first scan with LV correct
|
|
|
Sat Apr 9 13:45:42 2022, Max, Kristian, Runs, first scans with LV problem solved!
|
This is the first time with LV buffer problem solved (see Elog ID: 184). Before the PMT signals were out of sync with the wavelength data!
We concluded to scan with step sizes of 0.002nm, scan range of 0.5nm (f
nm), dwelltime = 150(5s), loops = 2 (approx.: 30min measurements).
DAQ1: lxg1927:/data.local2/BeamTimeTh22/
DAQ2: lxg0155:/data.local2/E142/
LMD file name DAQ1:229Thor
LMD file name DAQ2:229Th
Shottky marker pos: 243.973MHz
|
Time | SIS-intensity | cooler-HV | LMD-DAQ1 start-end | LMD-DAQ2 start-end | scan range(nm) | step width(nm) | dwell time(s) | comments
| |
11:25 | 1.0e9 | 209622 | 0102 - 102 | 7839-7839 | 323.2 - 322.8 | 0.002 | 3s | LV readout problem solved. WM readout is wrong (Cobra set is good)
| |
12:15 | old beam | 209622 | 0103 - 103 | 7840-7840 | 323.2 - 322.8 | 0.002 | 3s | WM readout is wrong
| |
12:50 | 2.3e9 | 209617 | 0104 - 104 | 7841-7841 | 323.2 - 322.8 | 0.002 | 3s | couldnt open go4 stream view, stopped after one good scan, WM readout is wrong .
| |
13:20 | 2.0e9 | 209617 | 0104 - 105 | 7842-7842 | 323.2 - 322.8 | 0.002 | 3s | first scan with LV correct
| |
13:40 | 1.2e9 | 209618 | 0106 - 106 | 7843-7843 | 323.2 - 322.8 | 0.002 | 3s | 3 loops
| |
14:20 | 1.5e9 | 209612 | 0107 - 107 | 7844-7844 | 323.2 - 322.8 | 0.002 | 3s | 1 loop
|
Runs after this have the right cobra set value but propably the wrong WM data until 10.04.22 12:44 (see also ID:198) |
|
Fri Apr 15 12:42:18 2022, Max, Danyal, Carsten, Konstantin, Patrick, Simon, General, laser wavelength range changed: 320.12 - 319.60 nm
|
Runs of the morning/afternoon/night shift. The wavelength range is now 320.12 - 319.60 nm.
|
Time | SIS-intensity | cooler-HV | LMD-DAQ2 file nr | LMD-DAQ1 file nr | scan range(nm) | step width(nm) | dwell time(s) | particles counted | comments
| |
12:51 | 1.2e9 | 209617 | 0321 | 8034 | 320.12 - 319.60 | 0.002 | 5s | 5530 | ERS Trafo 1.25e7 --> 1.2e9
| |
13:43 | 1.2e9 | 209617 | 0322 | 8035 | 320.12 - 319.60 | 0.002 | 5s | 6408 | at 13:49 there was a short broadening of the ion beam in the Schottky spectrum
| |
14:35 | 1.16e9 | 209618 | 0323 | 8036 | 320.12 - 319.60 | 0.002 | 5s | 6585 |
| |
15:30 | 1.08e9 | 209617 | 0324 | 8037 | 320.12 - 319.60 | 0.002 | 5s | 5701 |
| |
16:20 | 1.10e9 | 209617 | 0325 | 8038 | 320.12 - 319.60 | 0.002 | 5s | 5470 |
| |
17:11 | 1.11e9 | 209617 | 0326 | 8039 | 320.12 - 319.60 | 0.002 | 5s | 5519 |
| |
18:00 | 1.08e9 | 209616 | 0327 | 8040 | 320.12 - 319.60 | 0.002 | 5s | 5402 | Ecooler voltage suddenly jumped to 109619 around 18:30. Laser spot seems to drift slowly to an inner position (left on the screen). This might be due to an interplay between a decreasing laser power and the position sensitive detectors of the beam stabilization.
| |
18:52 | 1.16e9 | 209620 | 0328 | 8041 | 320.12 - 319.60 | 0.002 | 5s | 6948 |
| |
20:39 | 1.13e9 | 209619 | 0329 | 8042 | 320.12 - 319.60 | 0.002 | 5s | 6xxx | Dye was changed before this run was started
| |
20:32 | 1.20e9 | 209620 | 0330 | 8043 | 320.12 - 319.60 | 0.002 | 5s | 6948 |
| |
22:25 | 1.21e9 | 209619 | 0331 | 8044 | 320.12 - 319.60 | 0.002 | 5s | 7120 | Night shift took over (Patrick, Simon)
| |
23:15 | 1.26e9 | 209619 | 0332 | 8045 | 320.12 - 319.60 | 0.002 | 5s | 7080 |
| |
00:06 | 1.25e9 | 209616 | 0333 | 8046 | 320.12 - 319.60 | 0.002 | 5s | 6500 |
| |
00:59 | 1.23e9 | 209616 | 0334 | 8047 | 320.12 - 319.60 | 0.002 | 5s | 5380 |
| |
01:50 | 1.30e9 | 209616 | 0335 | 8048 | 320.12 - 319.60 | 0.002 | 5s | 6750 |
| |
02:41 | 1.38e9 | 209616 | 0336 | 8049 | 320.12 - 319.60 | 0.002 | 5s | 6970 |
| |
03:32 | 1.37e9 | 209616 | 0337 | 8050 | 320.12 - 319.60 | 0.002 | 5s | 7010 |
|
|
|