 Tue Apr 8 09:28:49 2025, Team PLEIADES, General, Controlled access to ESR to connect cables for DAQ
|
We will need to enter the ESR to connect the cables again for our DAQ and then drive in the outside detector for 20min to get some data.
9:35 entered
9:41 exit
9:44 ESR available again |
|
Tue Apr 8 09:53:04 2025, Team PLEIADES, Detectors, Moving outside particle detector in for 20min
|
9:53 Data taking with outside detector (GE01DD2AG) moved in to -110mm |
|
Tue Apr 8 10:13:51 2025, Team PLEIADES, Detectors, Moved outside particle detector back into parking position
|
10:16 Moved outside particle detector back into parking position (-126mm) |
Tue Apr 8 11:37:13 2025, Team PLEIADES, Detectors, PLEIADES 
|
11:37 Outside particle detector (GE01DD2AG) moved in to -100mm to take data |
|
Tue Apr 8 11:57:56 2025, Team PLEIADES, Detectors, Outside detector moved out
|
12:00 Outside particle detector moved out to parking position again (-125 mm) |
|
Sun Apr 6 19:42:23 2025, Taka, Moriguchi, General, Lessie screenshots
|
|
|
Sun Apr 6 20:13:03 2025, Taka, Moriguchi, Accelerator, Beam sharing
|
Now we have every injection. |
|
Sun Apr 6 21:12:07 2025, Taka, Moriguchi, General, Lassie screenshots
|
|
|
Sun Apr 6 21:29:37 2025, Taka, Moriguchi, Accelerator, Beam sharing
|
again, ESR : FRS = 1 : 1 |
|
Sun Apr 6 22:22:46 2025, Taka, Moriguchi, General, Lassie screenshots
|
|
|
Mon Apr 7 07:04:06 2025, Siddharth, Dima, Jelena, Guy, General, Lassie screenshots
|
|
|
Mon Apr 7 03:25:41 2025, Siddharth, Dima , Collaboration, mesycontrol does not start GUI
|
mesycontrol process starts but shows no GUI at all.
Around 02:51 we wanted to record leakage currents for PLEIADES.
The windows of the mesycontrol were not present on the screens.
We followed the instructions for restart:
-ssh -X into x86l-128 (-X is important, otherwise qt will not be initialized)
-mesycontrol
as a result we see nothing but the terminal is busy, and the process exists.
We noticed that ssh connection establishes very slow, the terminal after the connection responds to typing with a delay of several seconds(one press 'm', after 1-2 sec that letter appears on
the screen).
htop hanged the terminal entirely without showing a thing. Several minutes before we started htop and 12th thread(processor?) has been fully busy, 100%.
our assumption is that GUI has been closed because computer had not enough resources for sustaining it. We would not expect such a slow response even in terminal.
Could anybody have a look on x86l-128 and figure out why is it so slow?
UPD: started mesycontrol around 03:40, until 04:02 nothing happened except first two commands.
Tried to start it from x86l-124 and everything works fine except that the connection to /dev/tty/USB0 can't be established (because it is occupied by x86l-128?)
So we are not able to read leakage currents.
|
|
Sun Apr 6 23:51:33 2025, Siddharth, Dima, Simulations, LISE file for the 192Pb setting
|
|
|
Sun Apr 6 23:59:09 2025, Siddharth, Dima, General, Lassie screenshots
|
|
|
Mon Apr 7 01:05:11 2025, Siddharth, Dima, General, Lassie screenshots
|
|
|
Mon Apr 7 02:02:47 2025, Siddharth, Dima, General, Lassie screenshots
|
|
|
Mon Apr 7 02:56:47 2025, Siddharth, Dima, General, Lassie screenshots
|
|
|
Mon Apr 7 03:58:58 2025, Siddharth, Dima, General, Lassie screenshots
|
|
|
Mon Apr 7 05:04:59 2025, Siddharth, Dima, General, Lassie screenshots
|
|
|
Mon Apr 7 06:09:30 2025, Siddharth, Dima, General, Lassie screenshots
|
FRS started taking beam from 6:00 Am |
|