Injection to ESR stopped around 02:04:45.

Will continue to write data in hope that beam returns shortly.

Beam lost from SIS18 at 17:41:41.

We had no beam in ESR for about 3 minutes

because of problems in HHT
no beam from 16:36

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

At 9:32 we lost the beam. They have to work in the Unilac and there will be no beam for 45 minutes. 

No beam from 09:39 to 10:10 due to a setting change. The change aims to increase the measurement time to 10s.

beam is down 14:45. Problem with UNILAC. may take an hour.

03:07 Beam is down.

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.

plunger 150 for 250
plunger 48 for 410 

From file starting from 13:21 is a new setting for 96Sr.

We changed the trigger setup, see attachment

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.

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. 

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

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.
-----------------------------------------------------------------------

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.

Start of regular screenshots of the Lassie monitor every 1-2 hours.

Lassie Screenshot taken at 16:09