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:
[LIST]
[*] The laserscan tab shows each observable plotted against the predefined wavelength setpoints now.
|
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
|
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 14:15:44 2022, Kristian, Max, Konstantin, DAQ, Change in LV code
|
We changed the LV code so that the Cobra Set Wavelength is permanently sent. Before it was only sent once at the beginning of each laser step. This, however,
lead to too much data for the LV->MBS server.
This was fixed by inserting a 250 ms wait in LV (in Krypton data VI). Basically, all LV values are now updated every 250 ms, which works fine with MBS |
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):
|
Sun Apr 10 04:07:53 2022, Patrick, DAQ, go4 shows wrong frequencies and wavelengths  
|
[B]Update (ID:194):[/B] In labview "Stop All", close labview, stop python script (ID:197), close wavemeter. Then restart wavemeter, python script, labview
an mbs.
|
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.
|
Sun Apr 10 06:34:49 2022, Kristian, Max, DAQ, Wavemeter Readout
|
Problem solved. Ignore this entry
|
Sun Apr 10 13:17:53 2022, Kristian, Max, DAQ, Wavemeter readout
|
We changed the Labview code in order to reduce the amount of data that was overfilling the WM data queue. We removed the temperature and intensity values
and added an additional 250ms wait.
|
Sun Apr 10 15:08:42 2022, Carsten, DAQ, Backup of Data from 1rst Scanrange to extrenal RAID1 HDDs
|
I just performed a backup of all data (+log-Files) that were collected until now to the two RAID HDDs.
For DAQ1: /media/sdc2 - last file 229Thor7889.lmd. Please note, that the naming sceme on DAQ1 is inconsistent - please look for the filenumnbering
|
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 Mar 17 17:56:33 2022, Kristian, Calibration, HV dividers
|
PTB HV dividers arrived. Divider ratios are:
PT120: 12003,341
|
Thu Mar 31 22:41:35 2022, Kristian, Calibration, HV divider
|
We noticed a difference in the electron cooler high voltage:
The set voltage is ~205 kV, the Ohmlabs divider measures 207 kV and the PTB200 shows a value of ~212 kV. The latter is doing some crazy jumps of up to |
Fri Apr 1 18:19:58 2022, Kristian, Calibration, HV divider
|
We checked the strange behavior of the HV dividers again. The Ohmlabs and the PTB divider are in good agreement at 120 kV and 150 kV. There, both dividers
deviated by 0.35% from the value on the HKR multimeter. Ohmlabs divider yields higher voltage.
|
Sun Apr 3 18:52:30 2022, Konstantin, Calibration, Laser ion beam overlap
|
We measured vertical and horizontal ion beam positions. Unfortunately, the horizontal scraper positions can not be manipulated
by the "Device Control" software. Robert Boywitt has supported us a lot to get the drives moving by using the expert software on
a local control PC, which can only be remotely accessed from beapc032 with the usual experiment account "atplaser". In the first
|
Thu Apr 7 16:50:22 2022, Konstantin, Calibration, Spacial laser-ion overlap
|
Laser-ion-beam overlap was achieved after measuring the ion beam positions (compare [URL=https://elog.gsi.de/esr/E142/83]Entry 83[/URL]).
Screenshots are comprised in the following table.
|
Thu Apr 7 19:13:26 2022, Konstantin, Patrick, Calibration, How to find the correct laser position
|
In order to achieve the correct laser ion beam superposition one needs to do the following steps:
[LIST=1]
|
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.
[TABLE border="1"]
|
Fri Nov 19 15:50:44 2021, Rodolfo, Accelerator, Laser windows at E-Cooler side 
|
New laser viewports have been installed at the E-Cooler side of the ESR.
[IMG]elog:10/1[/IMG]
|