Tue May 21 11:09:15 2024, Yuri, General, Logbook for beam tuning.
|
The version with better resolution is on our wiki page.
https://wiki.gsi.de/pub/ESR_EXP/E0018Experiment/20240521_logbook3.pdf |
Tue May 21 08:50:06 2024, Yuri, Accelerator, EoB
|
End of beamtime!
Request is out.
Scrapers are removed, slits in the TE line removed, ESR is ramped down. |
Tue May 21 03:27:21 2024, K.Takiura Y.Kikuchi, Runs, Beam back
|
03:26 Beam is back. |
Tue May 21 03:07:58 2024, K.Takiura Y.Kikuchi, Runs, No beam
|
03:07 Beam is down. |
Mon May 20 14:02:03 2024, Jelena, Oliver, Shahab, DAQ, Retune 245 MHz
|
Mew numbers for 245 MHz plunger is 190 (both) |
Mon May 20 13:31:09 2024, Jelena, Oliver, Shahab, General, New setting focussing on 96-Sr
|
plunger 150 for 250
plunger 48 for 410
From file starting from 13:21 is a new setting for 96Sr. |
Mon May 20 13:26:55 2024, Jelena, Oliver, Shahab, General, Plunger values
|
plunger 150 for 250
plunger 48 for 410 |
Mon May 20 09:01:51 2024, Oliver, Jelena, General, Shift news
|
Data collection runs smooth so far.
Yuri Litvinov will start modifying SP magnets now. The resolution will change. |
Mon May 20 09:01:14 2024, Yuri, Accelerator, Modify SP magnets
|
In attempt to remove double-peak structure, we will modify the SP magnets
START: 9:02
SP unchanged. Other values lead to a worse peak shapes.
Scrapers:
EEXDS2HA: -75 mm -> -5 mm (hopefully the left half is scraped)
E02DS3HG: -60 mm - unchanged
STOP: 9:40 |
Mon May 20 05:32:17 2024, Gregor, Cagla, Accelerator, Short beam interruption
|
We lost the beam for ~2min at (from ~5:28 till ~5:30). Everything seems to be back at the same state. |
Sun May 19 17:48:15 2024, xing xu, hongfu, shahab, Runs, Beam back
|
beam is back, first file 17:47 |
Sun May 19 15:13:48 2024, xing xu, hongfu, Runs, No beam
|
beam is down 14:45. Problem with UNILAC. may take an hour. |
Sun May 19 14:17:57 2024, Shahab, Kanika,hongfu li,xing xu, DAQ, center frequency change for 96Sr
|
aiming for 96-Sr:
410 MHz:
The plunger position for 410 is 45, which should correspond to the 408.998 MHz which is expected position for 96Sr. The first file is at 14:38.
245 MHz:
The center frequency is changed to 244.235723 MHz for 96Sr, the new plunger position is 300.The first file is at 14:5 |
Sun May 19 14:11:29 2024, Yuri, Sergey, Accelerator, Sextupoles
|
at 13:00
scrapers in the ESR are moved to block the most outside orbits
E02DS3HG out -> -60 mm
EEXDS2HA out -> -75 mm
at 13:50
E02KS3 changed from +0.01 to -0.1
E01KS4 is unchanged at -0.26
peaks look somewhat narrower (see telegram) |
Sun May 19 12:04:55 2024, Kanika, Accelerator, Beam back
|
The beam is back. |
Sun May 19 11:02:49 2024, Xu Zhou, Yuhu Zhang, Kanika, Accelerator, the beam is paused
|
The beam is paused and HHT team needs to enter the ring. |
Sat May 18 16:45:15 2024, Helmut, Yury, Accelerator, setting for 96Sr (98Y)
|
To have a few more lines the setting actually is not on 96Sr directly, but on 98Y39+.
98Y is also the one set to be isochronous.
But in addition the SIS-energy is shifted by -0.9 MeV/u to get at least better transmission for 96Sr. |
Sat May 18 16:29:15 2024, Filip, Taka, Shahab, Runs, Good operation screen shot
|
|
Sat May 18 16:21:30 2024, Taka, Filip, Shahab, DAQ, DAQ start
|
16:21 DAQ restart for 96Sr
Acq. time 300 ms, 50 MS/s, span 25 MHz |
Sat May 18 15:26:46 2024, Taka, Filip, DAQ, DAQ stop
|
15:20 RSA DAQ stop -> Sr setting |
Sat May 18 14:43:59 2024, Yuri, Accelerator, Reduce intensity, 98Mo42+
|
reduce intensity
eexds2ha 7mm --> 9 mm
e02ds3hg -69 mm -- stays
measure for about 30 min
9 mm was too much, change to +8 mm |
Sat May 18 13:13:45 2024, Yuri, Taka, Xinliang, Sophia, Yuanming, Ragan, Shahab , Calibration, Shorter shots with 98 Mo
|
now making shorter shots with 98-Mo
3 seconds each
50 MSPS
98Mo
13:57 RSA01-2024.05.18.13.57.32.674.tiq, RSA02-2024.05.18.13.57.32.472.tiq
13:58 RSA01-2024.05.18.13.58.32.760.tiq, RSA02-2024.05.18.13.58.32.552.tiq
14:00 RSA01-2024.05.18.14.00.23.759.tiq, ../RSA02/RSA02-2024.05.18.14.00.23.551.tiq
14:01 RSA01-2024.05.18.14.01.09.543.tiq, ../RSA02/RSA02-2024.05.18.14.01.16.038.tiq
14:01 RSA01-2024.05.18.14.01.54.049.tiq, ../RSA02/RSA02-2024.05.18.14.02.05.544.tiq
last long shot :
14:05 RSA01-2024.05.18.14.05.14.375.tiq, ../RSA02/RSA02-2024.05.18.14.08.54.672.tiq
1 second each
RSA01-2024.05.18.14.08.54.879.tiq |
Sat May 18 13:07:23 2024, Yuri, Taka, Xinliang, Sophia, Yuanming, Ragan, Shahab , DAQ, Long measurements 100-Mo
|
Primary beam two shots, each 10 seconds
13:06 --> RSA01-2024.05.18.13.05.41.969.tiq, ../RSA02/RSA02-2024.05.18.13.05.42.662.tiq
13:08 --> RSA01-2024.05.18.13.08.41.929.tiq, ../RSA02/RSA02-2024.05.18.13.08.42.621.tiq
for checking Markus hypothesis about the longevity of the bunched beam due to the ISO mode. This is important to understand lifetime measurements in ISO mode, otherwise the information might be affected. |
Sat May 18 12:31:45 2024, Yuri, Taka, Xinliang, Sophia, Yuanming, Ragan, Shahab, Detectors, Cooler Curve measurements
|
Cooler curve measurement, Primary Beam 100 Mo
center Freqs:
243.26875 MHz
408.03925 MHz
Running 13 harmonics
25 MHz
50 MSPS
1 sec
First injection:
-650, RSA01-2024.05.18.12.32.51.008.tiq, RSA02-2024.05.18.12.32.50.799.tiq
-700, RSA01-2024.05.18.12.34.53.819.tiq, RSA02-2024.05.18.12.34.53.611.tiq
-800, RSA01-2024.05.18.12.36.50.332.tiq, RSA02-2024.05.18.12.36.50.123.tiq
-1000, RSA01-2024.05.18.12.37.56.219.tiq, RSA02-2024.05.18.12.37.56.011.tiq
-1100, RSA01-2024.05.18.12.39.29.003.tiq, RSA02-2024.05.18.12.39.28.795.tiq
-1200, RSA01-2024.05.18.12.41.22.539.tiq, RSA02-2024.05.18.12.41.22.331.tiq
-1300, RSA01-2024.05.18.12.42.28.763.tiq, RSA02-2024.05.18.12.42.28.554.tiq
-1400, RSA01-2024.05.18.12.43.33.203.tiq, RSA02-2024.05.18.12.43.32.995.tiq
-1500, RSA01-2024.05.18.12.45.11.816.tiq, RSA02-2024.05.18.12.45.11.608.tiq
New injection:
uncoooled beam: RSA01-2024.05.18.12.49.09.850.tiq, RSA02-2024.05.18.12.49.09.642.tiq
-650, RSA01-2024.05.18.12.50.20.059.tiq, RSA02-2024.05.18.12.50.19.851.tiq
-650 (longer wait), RSA01-2024.05.18.12.52.37.936.tiq, RSA02-2024.05.18.12.52.37.728.tiq
-600, RSA01-2024.05.18.12.53.55.915.tiq, RSA02-2024.05.18.12.53.55.706.tiq
-500, RSA01-2024.05.18.12.55.31.146.tiq, RSA02-2024.05.18.12.55.30.938.tiq
-400, RSA01-2024.05.18.12.56.48.690.tiq, RSA02-2024.05.18.12.56.48.482.tiq
-300, RSA01-2024.05.18.12.58.16.906.tiq, RSA02-2024.05.18.12.58.16.698.tiq
-200, RSA01-2024.05.18.12.59.44.098.tiq, RSA02-2024.05.18.12.59.43.890.tiq
-100, RSA01-2024.05.18.13.00.38.088.tiq, RSA02-2024.05.18.13.00.37.880.tiq
0, RSA01-2024.05.18.13.01.28.466.tiq, RSA02-2024.05.18.13.01.28.258.tiq |
Sat May 18 02:22:30 2024, Helmut Weick, Accelerator, paper log book pages 17.05.2024
|
until we lost the beam in the night. |
Sat May 18 02:04:38 2024, Yoshi, Ohnishi, DAQ, RSA01 run
|
RSA01 was stopped from 19:25, it restart now. |
Sat May 18 01:57:44 2024, Weick, Accelerator, 96Sr isoc setting
|
We fist verified the ESR after a crash with the 98Zr setting, was fine good resolution,
then we scaled to 96Sr directly at gamma_t not with shift as before.
E_SIS = 449.21 MeV/u for 100Mo 38+
after target = 373.36 MeV/u for 96Sr 38+
in ESR = 373.60 MeV/u for 96Sr 38+
in the LISE calculation this leads to gamma = 1.40082 as before in the other settings.
yield is very low now, but some lines. |
Sat May 18 00:37:52 2024, Helmut, Wolfram, Shahab, David, Xinliang, Runs, SIS beam gone
|
|
Sat May 18 00:37:21 2024, Helmut, Wolfram, Shahab, David, Xinliang, Runs, Trying to get back to Zr setting
|
|
Sat May 18 00:15:44 2024, Yoshi, Ohnishi, General, Beam back
|
Beam is back, but it stopped again at 0:17...... |
Sat May 18 00:06:56 2024, Shahab, Runs, HHT people out again
|
we try to re run the ESR. ESR behaves very strangely. Something not so right. |
Fri May 17 23:30:16 2024, Shahab, General, HHT people inside
|
no beam since about one hour, also HHT people inside since about 10 min. |
Fri May 17 23:14:51 2024, Yoshi, Ohnishi, General, shift started
|
Just test |
Fri May 17 22:48:14 2024, Jelena B, Accelerator, Back to old setting
|
We go back to the Zr-settings to make a deffinite state of ESR and we move again to previous setting (Sr) |
Fri May 17 22:43:11 2024, Jelena B, Zsolt P., Accelerator, ESR_e.cooler are back
|
We have back ESR and we have a fixed issue with a cooler.
Beam issues! |
Fri May 17 22:38:30 2024, Jelena B, Zsolt P., , ESR + e.cooler are back
|
We have back ESR and fixed issue with a cooler. |
Fri May 17 22:06:05 2024, Jelena B, Zsolt P., Accelerator, ESR
|
ESR is down |
Fri May 17 21:56:58 2024, Jelena B, Zsolt P., Accelerator, Optimizing setting
|
We are optimizing setting for 96Sr
start time: 21:52 |
Fri May 17 21:44:39 2024, Jelena B, Zsolt P., General, Beam issues
|
We do not have beam, and we have some instability during last 1-1.5 hour. |
Fri May 17 20:33:43 2024, Jelena B, Zsolt P., General, Beam returned to FRS
|
We have again beam at FRS..
But we are taking still cycles on a same way as before...and discussing to go back to the old zirconium setting
In one hour HHT will enter the cave. |
Fri May 17 19:43:03 2024, Jelena B, Zsolt P., Shahab, David, Analysis, + Beam issues
|
Important - analysis
-> we are trying to get PID with a new setting to see if 98Zr decays with 30s half-life
--> we are taking 1 min cycles
---> strongest line does not corespondents to 96Sr38+ as it decays very fast (few seconds) and we observe long-lived one - still we have to confirm this
----> analysis is still ongoing
We lost the beam at 19:35
|
Fri May 17 17:50:49 2024, Jelena B, Zsolt P., Shahab, DAQ, new trigger events
|
From 17:49 we have super short trigger. - see attached setting! |
Fri May 17 17:09:26 2024, Helmut, Yury, Accelerator, approx. 96Sr setting (98Zr39+)
|
Only 96Sr would yield very few line with only ions from time to time.
So we went a bit lower in Brho 7.69 Tm -> 7.65 Tm.
The setting is calculated as a 98Mo39+.
E-SIS = 455.3 MeV/ for 100Mo,
after target 98Mo now with 39+ gives 7.6500 Tm.
In ESR also 39+.
In LISE we get the same average gamma as before for 98Zr (gamma = 1.40082).
The 98Zr was also entered as a 98Mo40+- |
Fri May 17 17:08:24 2024, Jelena B, Zsolt P., Runs, New setting from 5p.m.
|
NEW SETTING
All runs from 17:00 are with new setting, due to changing the directory - transfer from old to new one around 200 runs. |
Fri May 17 17:03:39 2024, Helmut, Yury, Accelerator, approx. 96Sr setting
|
Only 96Sr would yield very few line with only ions from tiem to time.
So we went a bit lower in Brho 7.69 Tm -> 7.65 Tm.
The setting is calculated as a 98Mo39+.
E-SIS = 455.3 MeV/ for 100Mo.
after target 98Mo now with 39+ gives 7.6500 Tm.
In ESR also 39+.
In LISE we get the same average gamma as before for 98Zr (gamma = 1.40082). |
Fri May 17 16:42:00 2024, Jelena B, Zsolt P., General, Beam back
|
Beam is back at 16:38.
We are changing the setting. |
Fri May 17 16:34:43 2024, Jelena B, Zsolt P., General, Beam issues
|
We lost beam at 16:29.
Cooler has to be investigated. |
Fri May 17 05:48:33 2024, Ahmed, Zidarova, Kalaidjieva, Runs, Beam stopped
|
HHT have more problems and need to enter the cave, beam is stopped for some time
Beam stop: 05:46
Beam back 6:31 |
Fri May 17 00:15:24 2024, Ahmed, Zidarova, Kalaidjieva, Runs, Beam gone
|
HHT called and said they have problems and need to enter the cave, so they stop the beam for some time
Beam Stop 00:10
Beam back 01:01 |
Thu May 16 23:08:34 2024, Ahmed, Zidarova, Runs, Beam dropped
|
Beam dropped between 23:00 and 23:05 |
Thu May 16 21:51:22 2024, Ide, Hubbard, Runs, Intensity back to previous values
|
since 21:48 particle intensities increased to again to 1.5E9 |
Thu May 16 21:40:20 2024, Ide, Hubbard, Runs, Intensity drop
|
Intensity in particles dropped from 21:33 |
Thu May 16 21:26:50 2024, Ide, Hubbard, Runs, Intensity back to previous values
|
since 21:20 the intensity is back to 1.5E9 |
Thu May 16 21:13:18 2024, Ide, Hubbard, Runs, Intensity drop
|
The intensity dropped at 21:10 from ~ 1.6E9 down to ~ 8E8 |
Thu May 16 19:10:27 2024, Ide, Hubbard, Xinliang, David, Shahab, Runs, New Run setting for Zr Isomer hunt
|
19:10 runs from now on run with an optimized setting:
we did a lot of optimization for the hunt of Zr isomer:
1- increased the time as much as possible, but stay within the 1:1 cycle with FRS
2- increased the sampling rate from 6.25 MSPS to 50 MSPS (!) going down to very short recording times --> 300ms only
We are now taking data with this settings for about half an hour. |
Thu May 16 18:55:38 2024, Ide, Hubbard, General, new timing cycle
|
new timing cycle of 6.7s |
Thu May 16 18:33:30 2024, Ide, Hubbard, Runs, Beam returned to ESR
|
Beam is back at 18:32
now in the particle plot the peaks seem to be more isolated than before (see attachment 1)
since 18:36 it looks like before (see attachment 2) |
Thu May 16 18:28:31 2024, Ide, Hubbard, Runs, No beam to ESR
|
beam issues between 18:23-18:26
and beam completely lost from 18:27 till 18:32
in the SIS an issue with a dipole occured |
Thu May 16 16:45:33 2024, Ide, Hubbard, Runs, Beam returned to ESR
|
beam is back
16:45 |
Thu May 16 16:43:29 2024, Yuri, Accelerator, HHT
|
HHT sees radiation from us. We stop for 10 min for them to see the speed with which the radiation level decreases. |
Thu May 16 16:38:11 2024, Ide, Hubbard, Runs, No beam to ESR
|
because of problems in HHT
no beam from 16:36 |
Thu May 16 16:10:03 2024, Ide, Hubbard, Runs, Lassie Screenshot
|
Lassie Screenshot taken at 16:09 |
Thu May 16 15:24:30 2024, Ide, Hubbard, Accelerator, new Plunger setting
|
plunger motors were set
to +/-390 mm for 245 MHz resonator
and +/-55 mm for 410 MHz resonator |
Thu May 16 14:52:45 2024, Shahab, DAQ, Zr recording
|
Recording Zr starting from 14:45 again back to short cycle. |
Thu May 16 13:04:02 2024, Mayr, Hannes, Runs, DAQ stopped, change setting to 98Zr
|
Beam tuning for 98Zr starting at 12:53, following data should be excluded from analysis. DAQ was stopped around 13:13. |
Thu May 16 12:48:58 2024, Sergey, Accelerator, Tune to 98Zr
|
- stop longer measurements
- change quadrupole and sextupole magnets
- rescale SIS-TE-ESR |
Thu May 16 11:20:10 2024, Sergey, Accelerator, Screenshot of ESR pattern with 140 repetitions (each is 100 ms)
|
Injection Beam Process: 100ms
Bunching Beam Process: 16ms
Intermediate Beam Process: 100 ms, which is repeated 140 times
Intermediate Beam Process: 16 ms |
Thu May 16 11:13:05 2024, Mayr, Hannes, Runs, Rates
|
With the new timing, the rates now look like can be seen in the screenshot. |
Thu May 16 11:08:27 2024, Mayr, Hannes, Runs, DAQ running again
|
"Real" measurement with good data starting from 11:07 until approximately 13:00.
Measurement time was changed to 10s with injections every 32s. |
Thu May 16 10:18:14 2024, Mayr, Hannes, Runs, Beam back, DAQ off
|
Beam is back since 10:10, but DAQ is turned off to change the setting there.
Measurements starting at 10:18 are only test runs and should not be used for analysis. |
Thu May 16 09:41:56 2024, Mayr, Hannes, Runs, No beam
|
No beam from 09:39 to 10:10 due to a setting change. The change aims to increase the measurement time to 10s. |
Thu May 16 08:58:39 2024, Mayr, Hannes, Runs, Fluctuations in particle rate
|
Particle rates are fluctuating and increasing from a constant 5e8 to something around 1e9. |
Thu May 16 07:50:39 2024, Mayr, Hannes, Runs, Peaks with very high particle rate
|
Peaks in the particle diagram going to unusual high 1.4e9 particles. |
Thu May 16 07:25:33 2024, Mayr, Hannes, Runs, Lassie Screenshot 07:23
|
Start of regular screenshots of the Lassie monitor every 1-2 hours. |
Thu May 16 04:37:27 2024, Boguslaw, Camille, Runs, No beam to ESR
|
We had no beam in ESR for about 3 minutes |
Thu May 16 00:37:41 2024, Boguslaw, Camille, Runs, Injection pattern changed
|
The injection pattern changed on Lassie monitor (0:27 AM). (picture 1)
It when back to the previous rate at 1:48 AM. (picture 2)
The same pattern change appeared from 3:01 AM to 3:07 AM. (picture 3) and from 3:24 AM to 3:39 AM. |
Wed May 15 23:04:32 2024, Xinliang, Analysis, Electron cooler data
|
The cooler curve measured during May 14 afternoon. |
Wed May 15 20:40:51 2024, Jeroen, Johan, Runs, Beam returned to ESR
|
20:39:42 Runs restarted. |
Wed May 15 20:17:20 2024, Jeroen, Accelerator, Fewer spills from SIS18 then lost beam
|
Apparently fewer spills coming from SIS18, see attached.
Beam was lost at 20:17:52. |
Wed May 15 19:45:44 2024, Helmut Weick, Accelerator, Cooler curves after beam shift
|
After the Beam position tuning but before the scraper tuning two more cooler curves were taken.
The first with all scrapers open shows a similar shape to before with the same quadrupole setting.
Afterwards the ESR ebergy was shifted by -0.8 MeV/u to get the beam more on an outer orbit.
The curve then is shifted and has a bit less acceptance. |
Wed May 15 19:20:32 2024, Helmut Weick, Accelerator, scraper setting
|
After the orbit correction on the target straight section the scrapers work better.
One pair of scrapers works best:
GEEXDS2HA (outside straight section = low Brho side) = -4.0 mm
GE02DS3HG (outside arc = high Brho side) = -71.4 mm
All other scrapers are open (finished playing with scrapers ~18:20)
When one side is opened more one can cut more on the other.
We can attack the beam from both sides.
With scrapers good resolution, David already posts lifetimes of the isomer.
Details in paper log book. |
Wed May 15 18:37:36 2024, Jeroen, Johan, Shahab, Runs, Beam returned to ESR
|
Beam returned at 18:30:55. Taking data with new triggers. |
Wed May 15 17:47:34 2024, Jeroen, Johan, Shahab, General, New Trigger Setup
|
We changed the trigger setup, see attachment |
Wed May 15 17:45:09 2024, Jeroen, Johan, General, No beam to ESR
|
Beam lost from SIS18 at 17:41:41. |
Wed May 15 17:22:43 2024, Jeroen, Shahab, Johan, Runs, 98Mo run
|
Beam tuned at 4:50, data acquisition aligned for 98Mo at 4:56. |
Wed May 15 16:55:10 2024, Jeroen, Johan, General, Tuning ESR scraper. Isomer resolved.
|
4:50 Scraper tuned to produce Gaussian beam profile for 98Mo. Isomer now clearly resolved.
Plan to take data for 98Mo fragment for 12 hours. Measurements from 4:59 are now aligned so that the Molybdenum fragment is centered in the RSA acquisition. |
Wed May 15 13:39:10 2024, Beatriz, Min, General, ESR setting
|
From 13:37 ESR will be changed again. Now back to the primary beam, it will be attempted to measure the orbit of the beam. |
Wed May 15 12:58:12 2024, Beatriz, Min, Shahab, Runs, optimizing the mass resolution
|
Yuri and Sergey still optimizing the mass resolution.
From 13:10 to ~ 13:35 SIS energy was increased to 457.4 (~3 MeV/u) to test whether this moves the best isochronicity to 98Mo (we were off before), -> Brho(98Mo)=7.12736 Tm
From ~13:35 back to setting up with the primary beam at 441.95 MeV (with target, same Brho as the 98Mo fragments). It will be attempted to measure the orbit of the beam |
Wed May 15 11:59:32 2024, Beatriz, Min, DAQ, File transfer to lustre looks to be stopped
|
File transfer to lustre looks to be stopped at around 11:35AM |
Wed May 15 11:45:22 2024, David, Analysis, Lustre Trouble
|
Since around 11:30, Lustre is down, therefore in https://sparc-daq-02.gsi.de/, the spectrograms are not being updated. Expected time to recovery > 2 hours.
The data will still be stored on the local hardisk. Whenever Lustre is online, we start file transfer and analysis.
Attached can be found an information email sent:
-------------------
Dear Lustre-users,
the main metadata server of the Lustre file system shows repeated errors that break I/O on at least
some clients.
We will have to restart the server, which will cause a downtime of min. 2 hours.
----------------------------------------------------------------------- |
Wed May 15 10:58:32 2024, Beatriz, Min, General, Beam returned to ESR
|
Beam recovery at around 10:52:30. Sergey and Yuri still tuning the mass resolution. |
Wed May 15 09:35:08 2024, Beatriz, Min, General, No beam
|
At 9:32 we lost the beam. They have to work in the Unilac and there will be no beam for 45 minutes. |
Wed May 15 06:15:02 2024, Chris, Asahi, DAQ, Data transfer to lustre looks to be stopped
|
File transfer to lustre looks to be stopped at 6:03
File copy program had stopped for some reason.
After figuring out what the problem was, we have restarted the file copy and everything seems to be catching up. |
Wed May 15 02:12:59 2024, Chris G, Asahi Y, General, Beam returned to ESR
|
Injection to ESR restarted around 02:12:15 |
Wed May 15 02:07:02 2024, Chris G, Asahi Y, General, No beam to ESR
|
Injection to ESR stopped around 02:04:45.
Will continue to write data in hope that beam returns shortly. |
Wed May 15 01:27:13 2024, David, Asahi, Shahab, Chris, DAQ, Restarted data taking
|
Data taking restarted at 01:27 following re-alignment of the RSAs.
Also reduced number of processing threads to 10. |
Wed May 15 01:11:45 2024, David, Asahi, Shahab, Chris, Ruijiu, General, Time optimisation
|
DAQ stopped at 01:11 to optimise data taking cycle of RSAs.
Changed data writing time from 2s -> 1.8s. |
Wed May 15 00:26:53 2024, David, Asahi, Shahab, Chris, Ruijiu, Runs, First data file - 00:26
|
Centered resonant frequency on 98Mo+42 at the 126 harmonic (243.925 MHz) and 211 harmonic (408.483 MHz).
Recording for 2 seconds (injection start at 10%), injection every 6 seconds. |
Wed May 15 00:17:24 2024, David, Asahi, Shahab, Chris, Ruijiu, DAQ, Optimizing the 245 resonance curve
|
|
Wed May 15 00:06:10 2024, David, Asahi, Shahab, Chris, Ruijiu, DAQ, Optimizing the 410 resonance curve
|
|
Tue May 14 23:46:04 2024, David, Asahi, Shahab, DAQ, Trigger setup
|
GENESYS setup trigger
screen shot
https://clipboard.acc.gsi.de/screenshot-app/screenshots/tcl1064/2024-05-14_23-46-56-017.png |
Tue May 14 23:40:03 2024, Helmut, Sergey, Yury, Accelerator, paper log book
|
two pages of log book on paper for teh first setup,
injection into ESR and tuning primary beam 100Mo and fragment 98Mo. |
Tue May 14 23:22:55 2024, Helmut Weick, Accelerator, isochronicity curves
|
Sergey started with a setting with quadrupoles already changed like in 2021.
Ths was used for the first isochronicity curves.
It also gave soem, however, not good peak shapes with scrapers closed.
But after a failure only a new setting of quads could revover the peaks.
Then more cooler curves were measured and found to have quite a slope.
Changing ESR energy does not change the curves much, but changing the quads does.
With the stronger variation of quads (+1.65% on two quadrupole families) the curve tilts to opposite side.
All curves in EXCEL.
Cooler voltage converted to Brho with gamma ~ 1.4 and curves in relative frequency spread shifted on top of each other.
In new injections the quads are set new, which causes a frequency jump. Pasted parts of curves to remove jump. |
Tue May 14 22:13:38 2024, David, Ruijiu, David, Asahi, DAQ, doing some test runs without accelerator trigger
|
empty shots for test. |
Tue May 14 21:41:11 2024, Shahab, Runs, Test Screenshot
|
|
Tue May 14 19:07:27 2024, Shahab, Runs, Broadband measurement / High Sampling rate
|
Stable beam after a long time:
from below ones, only the last 4 ones are probably best.
RSA01-2024.05.14.17.36.49.211.tiq
RSA01-2024.05.14.17.38.25.867.tiq
RSA01-2024.05.14.17.38.39.827.tiq
RSA01-2024.05.14.17.38.54.555.tiq
RSA01-2024.05.14.17.39.08.523.tiq
and
RSA02-2024.05.14.17.32.58.640.tiq
RSA02-2024.05.14.17.36.48.947.tiq
RSA02-2024.05.14.17.37.02.258.tiq
RSA02-2024.05.14.17.38.25.603.tiq
RSA02-2024.05.14.17.38.39.587.tiq
RSA02-2024.05.14.17.38.54.315.tiq
RSA02-2024.05.14.17.39.08.283.tiq |
Tue May 14 15:07:23 2024, Ruijiu, David, Shahab, Xinliang, Zhangmin, Runs, Cooler curve measurement 7x
|
Cooler curve measurement
# First run:
# V, RSA01-File, RSA02-File
-2300, RSA01-2024.05.14.15.21.21.576.tiq, RSA02-2024.05.14.15.21.21.334.tiq
-2200, RSA01-2024.05.14.15.22.56.743.tiq, RSA02-2024.05.14.15.22.56.501.tiq
-2100, RSA01-2024.05.14.15.24.17.833.tiq, RSA02-2024.05.14.15.24.17.591.tiq
-2000, RSA01-2024.05.14.15.25.34.248.tiq, RSA02-2024.05.14.15.25.34.006.tiq
-1900, RSA01-2024.05.14.15.26.39.602.tiq, RSA02-2024.05.14.15.26.39.359.tiq
-1800, RSA01-2024.05.14.15.27.41.204.tiq, RSA02-2024.05.14.15.27.40.962.tiq
-1700, RSA01-2024.05.14.15.28.45.781.tiq, RSA02-2024.05.14.15.28.45.539.tiq
-1600, RSA01-2024.05.14.15.29.49.831.tiq, RSA02-2024.05.14.15.29.49.589.tiq
-1500, RSA01-2024.05.14.15.31.02.912.tiq, RSA02-2024.05.14.15.31.02.670.tiq
-1400, RSA01-2024.05.14.15.32.53.806.tiq, RSA02-2024.05.14.15.32.53.564.tiq
-1300, RSA01-2024.05.14.15.34.02.599.tiq, RSA02-2024.05.14.15.34.02.357.tiq
-1200, RSA01-2024.05.14.15.35.32.079.tiq, RSA02-2024.05.14.15.35.31.836.tiq
-1100, RSA01-2024.05.14.15.36.35.601.tiq, RSA02-2024.05.14.15.36.35.359.tiq
-1000, RSA01-2024.05.14.15.37.52.778.tiq, RSA02-2024.05.14.15.37.52.536.tiq
-900, RSA01-2024.05.14.15.39.20.656.tiq, RSA02-2024.05.14.15.39.20.414.tiq
-800, RSA01-2024.05.14.15.40.24.019.tiq, RSA02-2024.05.14.15.40.23.777.tiq
-700, RSA01-2024.05.14.15.41.41.963.tiq, RSA02-2024.05.14.15.41.41.721.tiq
-600, RSA01-2024.05.14.15.42.53.140.tiq, RSA02-2024.05.14.15.42.52.899.tiq
-500, RSA01-2024.05.14.15.43.55.830.tiq, RSA02-2024.05.14.15.43.55.588.tiq
# Second run:
-1400, RSA01-2024.05.14.16.01.38.472.tiq, RSA02-2024.05.14.16.01.38.231.tiq
-1410, RSA01-2024.05.14.16.02.42.778.tiq, RSA02-2024.05.14.16.02.42.536.tiq
-1420, RSA01-2024.05.14.16.03.50.044.tiq, RSA02-2024.05.14.16.03.49.802.tiq
-1430, RSA01-2024.05.14.16.05.04.612.tiq, RSA02-2024.05.14.16.05.04.371.tiq
-1440, RSA01-2024.05.14.16.06.16.606.tiq, RSA02-2024.05.14.16.06.16.364.tiq
-1450, RSA01-2024.05.14.16.07.31.414.tiq, RSA02-2024.05.14.16.07.31.172.tiq
-1460, RSA01-2024.05.14.16.08.43.864.tiq, RSA02-2024.05.14.16.08.43.622.tiq
-1470, RSA01-2024.05.14.16.09.59.912.tiq, RSA02-2024.05.14.16.09.59.670.tiq
-1480, RSA01-2024.05.14.16.11.08.625.tiq, RSA02-2024.05.14.16.11.08.384.tiq
-1490, RSA01-2024.05.14.16.12.12.699.tiq, RSA02-2024.05.14.16.12.12.458.tiq
-1500, RSA01-2024.05.14.16.13.20.061.tiq, RSA02-2024.05.14.16.13.19.820.tiq
-1510, RSA01-2024.05.14.16.14.31.982.tiq, RSA02-2024.05.14.16.14.31.741.tiq
-1520, RSA01-2024.05.14.16.15.30.129.tiq, RSA02-2024.05.14.16.15.29.887.tiq
-1530, RSA01-2024.05.14.16.16.41.026.tiq, RSA02-2024.05.14.16.16.40.784.tiq
-1540, RSA01-2024.05.14.16.17.51.499.tiq, RSA02-2024.05.14.16.17.51.257.tiq
-1550, RSA01-2024.05.14.16.18.49.853.tiq, RSA02-2024.05.14.16.18.49.612.tiq
-1560, RSA01-2024.05.14.16.19.58.297.tiq, RSA02-2024.05.14.16.19.58.054.tiq
-1570, RSA01-2024.05.14.16.21.14.503.tiq, RSA02-2024.05.14.16.21.14.262.tiq
-1580, RSA01-2024.05.14.16.22.29.616.tiq, RSA02-2024.05.14.16.22.29.375.tiq
-1590, RSA01-2024.05.14.16.24.26.365.tiq, RSA02-2024.05.14.16.24.26.124.tiq
-1600, RSA01-2024.05.14.16.25.34.823.tiq, RSA02-2024.05.14.16.25.34.582.tiq
-1610, RSA01-2024.05.14.16.26.43.576.tiq, RSA02-2024.05.14.16.26.43.335.tiq
-1620, RSA01-2024.05.14.16.27.57.633.tiq, RSA02-2024.05.14.16.27.57.391.tiq
-1630, RSA01-2024.05.14.16.28.59.107.tiq, RSA02-2024.05.14.16.28.58.865.tiq
-1640, RSA01-2024.05.14.16.30.03.861.tiq, RSA02-2024.05.14.16.30.03.619.tiq
-1650, RSA01-2024.05.14.16.31.06.942.tiq, RSA02-2024.05.14.16.31.06.701.tiq
-1660, RSA01-2024.05.14.16.32.25.911.tiq, RSA02-2024.05.14.16.32.25.670.tiq
-1670, RSA01-2024.05.14.16.33.46.951.tiq, RSA02-2024.05.14.16.33.46.710.tiq
-1680, RSA01-2024.05.14.16.34.56.720.tiq, RSA02-2024.05.14.16.34.56.479.tiq
-1690, RSA01-2024.05.14.16.36.54.877.tiq, RSA02-2024.05.14.16.36.54.636.tiq
-1700, RSA01-2024.05.14.16.38.06.854.tiq, RSA02-2024.05.14.16.38.06.613.tiq
# Third run:
-1590, RSA01-2024.05.14.16.40.04.235.tiq, RSA02-2024.05.14.16.40.03.994.tiq
here computer crashed.
1. Preliminary result. |
Sun May 12 18:34:54 2024, Ruijiu, Analysis, How to use queqiao to transfer tiq data
|
If the ssh to lxir131 was disconnected, you can connect to lxir131 and restart queqiao program to transfer tiq data from NAS to luster.
1. Open a terminal on any GSI linux computer, like the one in the Measurement Room:
2. start "Online data analysis system":
(base) litv-exp@lxg1478:~$ start_OnlineDataAnalysisSystem
3. click the 3rd button "Copy data from RSA hard disk to luster" to start "queqiao" program.
4. click "start" button on "queqiao" user interface to transfer tiq data on RSA spectrum analyzer.
|
Thu May 9 15:59:30 2024, Ruijiu Chen, DAQ, Carsten checked the NTCAP system.
|
Exactly this was the question. If several devices fail at the same time and you look for the course you might get suspicious.
Anyhow,
the NAS is working again. I assume this was only a temporary alert. I cannot trace the alert back to something special. One could do a S.M.A.R.T oft he HDDs to read out their status.
The bad new ist that the NI PXIe-1075 (crate) power supply seems to have a failure (95% sure). It is in a shuttle unit and can in priciple be replaced as a whole.
The shuttle itself is not easy to open itself, so to really measure the voltages is diffcult/takes some time. I tried to measure the voltages at an external connector (DB9 at backside of the crate) but as
you might know it doesn’t have a „hard switch“ but some push button that starts some logic. Depending on the number of modules in the crate or if I switch on the fans on full intensity (as a load) the
power of the crate immediately switches off or stays on a little bot longer. If you take out one or more modules (no particular one) the crate stays on a little bit longer. Some of the modules show an
error then. I assume is because of wrong/missing power.
Again, I had no chance for a careful measurement of this behaviour, so I am not fully sure whether I am right.
Unfortunately, the crate itself cannot be bougth anymore (discontinued), similar ones are incredibly expensive and also usually not on stock
I suggest a twofold strategy : We can bring the „power supply shuttle“ (that i shte name) to a specialist here at GSI, may be Shahab knows someone (or Jan/Uwe). May be there is a quick way to fix it.
In former times weh ad someone here at GSI.
Or try to get a new power supply shuttle (but it might be discontinued as well).
The full replament part (someone would need to contact NI and/or search the net, if a company/ebay still has it) is called:
„PXIe-1075 PowerSupplyShuttle“
I found two part numbers for it:
198136B-01L (original part number ont he back of the deivce)
780292-01 (official replacement part number) . However, NI doesn’t know about it on the web page.
http://download.ni.com/support/manuals/372539a.pdf
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019N2CSAU&l=de-DE
Evtl. hier anfragen:
https://www.rosenkranz-elektronik.com/de/messgeraete/273795/national-instruments-ni-pxie-1075
or datatec, they also have a lot NI Pxie stuff.
https://www.datatec.eu/pxi-chassis
ebay?
However, again I am not 100% sure about the PS, but there are strong hints.
A few notes at the end:
Although none of the below is likely the reason for the failure, yet,
If a label on crate a states „please leave some headroom for ventilation“ then please do it. There might be a reason.
Please consider the maximum power that can be drawn from a single mains connection. Two crates (NIM/NI) + a server computer are quite something, in particular on a multi-outlet power strip….
Bending of cables, in particular of optical fibres… Don’t bend them two tight. The NI optical cable can also not be ordered anymore. Stiff long cables on tiny connector (found on several places on the NI
crate).
I cannot take further care about the issue since I am pretty busy here with the Etarget beamtime but may be it helps soemhow.
Best,
Carsten |
Thu May 9 10:01:59 2024, Ruijiu Chen, DAQ, NI crate of NTCAP system can not be started.
|
After moving the NTCAP system from HKR to ESR Messhutte, we tested the system with a signal generator on 16th February and confirmed that it was functioning correctly.
On 7th May, I and David tried to start the NTCAP system again. However, the main computer of the NTCAP system took a significantly longer time to boot up on 7th May. We
managed to collect some data and subsequently shut down the LabVIEW interface on 7th May. The NTCAP system was running well during the test. In the afternoon of 7th May, to
replace the new monitor, I turned off the NTCAP system except the hard disk of NTCAP.
On the morning of 8th May, I noticed an alert warning on the hard disk of the NTCAP system. Moreover, I found the NTCAP computer unexpectedly turned on. When I
tried to start the system today at the office, it failed to boot. The SP Device indicator was flashing, and then the system powered down by itself.
I am concerned that not shutting down the hard disk might have contributed to these issues, although I am not entirely sure.
1. Comparison of tdms files between 16th February and 7th May.
iq:
IQ_2024-02-16_11-00-53 0000000.iq.tdms 4196035 kB
IQ_2024-02-16_11-00-53 0000001.iq.tdms 4196035 kB
IQ_2024-02-16_11-00-53 0000002.iq.tdms 4196035 kB
IQ_2024-05-07_10-24-21 0000000.iq.tdms 4196035 kB
IQ_2024-05-07_10-24-21 0000001.iq.tdms 4196035 kB
IQ_2024-05-07_10-24-21 0000002.iq.tdms 4196035 kB
sc:
SC 2024-02-16[11-01-31 0000000.sc.tdms 386 kB
SC 2024-05-07 10-23-49 0000000.sc.tdms 136 kB
The iq and sc files recorded on 7th May are the same as the files which were recorded on 16 February. However, it took a long time to start the NTCAP system on 7th
May. It seems that the status of NTCAP was wrong on 7 May.
2. The hard disk of the NTCAP system was the old one on 06 February. The hard disk was replaced on 6th February and 7th May. |
Thu May 9 09:12:59 2024, Dounia, Shahab, DAQ, RSA file sync
|
RSA file sync with server was up with LXIR131 through to the Lustre. |
Mon May 6 12:16:09 2024, Ruijiu Chen, DAQ, ntcap scaler
|
|
Tue Apr 16 15:35:07 2024, Jan, Collaboration, G-PAC Proposal
|
|
|