Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Run NumberStart timeEnd timeNumber of EventsWindow coordinates (DUT)Comments
9002/06/18 11pm02/06/18 11:25 pm8655x=100~300 
91

02/06/18 11:27 pm

    
9202/06/18 11:27 pm03/06/18 00:27 am19007 We hadn't saved the histogram at the end of run 91, so the run histogram just has twice as much data. But the beam conditions were stable between these two runs.
9303/06/18 00:30 am03/06/18 01:03 am9021  
9403/06/18 01:05 am03/06/18 01:36 am9284  
9503/06/18 01:39 am03/06/18 02:07 am9013  
96    moving the RD53: up 1cm (Motor 3: Y fine  : > 1cm)
9703/06/18 02:24 am03/06/18 02:54 am9113  
9803/06/18 02:57 am

03/06/18
3:14 am

6845 

Changed shift to Ke and Jannicke

Stopped early because we were looking at Sensor 0 for measuring the number of events, will be using number of events from Sensor 2 from now on - it does not have hot pixels!

99

03/06/18

3:14 am

03/06/18
3:40am
9210  
100

03/06/18

3:40am

03/06/18

4:06am

9406  
101

03/06/18

4:06am

03/06/18

4:34am

9425  
102

03/06/18

4:34am

03/06/18

5:04

9173  
103

03/06/18

5:04am

03/06/18

5:31am
9150X: (0,~100)Moved RD53 (Motor 3 Y:fine < 2 cm) RBV from step at 10.00mm now. Aiming for coverage of 0-100 in X
104

03/06/18

5:31am

03/06/18
5:59am

9245 Moved RD53 (Motor 3 Y:fine > 2 mm) RBV from step at 12.00mm now, adjustment was made to get slightly better coverage in the 50-100 range. Looks good now!
105

03/06/18
6:00 am

03/06/18

6:12am

  

Run stopped early - noticed histograms stopped filling

ERROR IN DUT DATA PRODUCER

vent: tag(0) l1id(14 bcid(11398) hits (0)
Event: tag(0) l1id(15 bcid(11399) hits (0)
####################
### Stopping Run ###
####################
Got 1791events!
Caught interrupt, stopping data taking!
Abort will leave buffers full of data!
Caught interrupt, stopping data taking!
Abort will leave buffers full of data!
Waiting for run thread ...
-> Processor done, waiting for histogrammer ...
virtual void Fei4Histogrammer::process(): processorDone!
-> Processor done, waiting for analysis ...
virtual void Fei4Analysis::process(): histogrammerDone!
void Fei4Analysis::end()
-> All rogue threads joined!
-> Cleanup
Plotting : EnMask-0
Warning: empty cb range [1:1], adjusting to [0.99:1.01]
Plotting : OccupancyMap-0
Plotting : L1Dist-0
Empty data containers.
 -> send EORE
Command Thread exiting due to exception:
Error sending data:
  From /local/pixel/YarrEudaqProducer/EUDAQ/src/EUDAQ/main/lib/src/TransportTCP.cc:229
  In void eudaq::{anonymous}::do_send_data(SOCKET, const unsigned char*, size_t)

ERROR IN TLU PRODUCER:

Error sending data:
  From /local/pixel/eudaq/eudaq-1.7/main/lib/src/TransportTCP.cc:229
  In void eudaq::{anonymous}::do_send_data(SOCKET, const unsigned char*, size_t)

While copying this error message pressed control C in TLU Producer ------------------------------------

restarted ./STARTRUN

reran  ./TLUProducer.exe -r 172.27.100.8:44000

reconfigured EUDAQ in EUDAQ RD using ni_coins_YARR because it seems like it was the most recently updated

starting run 933

Histograms not popping up; killing all jobs and restarting ------------------------------------------------

went through steps 1-3


Called Su Dong: suggested we look at size of files

df -k

Filesystem           1K-blocks     Used Available Use% Mounted on

/dev/sda1             20030100 18989568     16392 100% /

 

moved data files to

 /home/tfuser/data_20180603/

 Now down to 81% full

Filesystem           1K-blocks     Used Available Use% Mounted on

/dev/sda1             20030100 15243540   3762420  81% /

Okay, so source of the problem was the disk full. --------------------------------------


Step 3 shows errors in finding libraries

[tfuser@ar-eudaq eudaq-1.7]$ ./OnlineMon.exe: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by ./OnlineMon.exe)

./OnlineMon.exe: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./OnlineMon.exe)

NEEDED TO SOURCE SETUP_EUDAQ.SH. Edited twiki to reflect this. ----------------------------

 

./TLUProducer.exe -r 172.27.100.8:44000

bin/YarrProducer -h configs/controller/specCfgExtTrigger.json -c configs/connectivity/example_rd53a_setup.json -s configs/scans/rd53a/std_exttrigger.json -r 172.27.100.8

Step 4 Cannot connect to pixel@172.27.104.52

ssh_exchange_identification: Connection closed by remote host

 We can ping 172.27.104.52 but cannot log into it? Why? ------------------------------------------

From our end we are able to ssh into other places, so the issue appears to be with the 172.27.104.52 computer. We also tried just sshing with no username and this just hangs. Looked through ssh keys, no username associated with IP address although a key exists.

We think we might need to reset the computer, but the beam is on.

 

 

 

03/06/18
8:00am

   Timon and Alexandra have arrived, Timon made an access and they are now resetting the computer. We stopped the HGTD run before the access request was made.
106

03/06/18
8:38

03/06/18

9:05

9334  Beam is back, restarted a new run. Also restarted a new run for HGTD
10703/06/18
9:08

03/06/18

9:40

9384 Transferred to Alexandra
108

03/06/18

09:41

03/06/18empty     
      

The beam was turned off at 9:51.

108-119 are runs without beam used for testing the YarrProducer setup. No root files saved.

RD53a config file changed.

120

03/06/18

10:50

03/06/18

10:53

few events To test the config files.
121

03/06/18

10:54

03/06/18

  

 

   First run for analyzing with a new config. Restarted a new run for HGTD.