- Google doc with description of the DUTs and the run numbers as well as the pixel definition: https://docs.google.com/spreadsheets/d/1TnWUcQzUWrj8VAUR8ibuB0fImi6PLNq-u8Q3nU0tzjY/edit?gid=778326781#gid=778326781
* In the tab named “Test_structures_FBK_TILGADs”, the nam,e of the ddevices under test is mentioned as well as the batch they were included in. The brown AC LGAD was included on Batch 4.
* The tab “pixels_definition” describes which channels of the 16-channel CAEN digitizer was connected to which channel of each DUT.
* The tab “Plane_Dfinition” had the names of the sensors on each plane. You will notice that the AC LGAD was connected as DUT2 in plane number 3. Plane number 1 within the cold box is always the time reference.
* Tabs “batch_number” and “Calculator_alignment” arte not useful .
*Tab “runs” has a description of the runs and what voltage, conditions where used in each of them. The run numbers is useful to locate the data
- Data are available on the DRD3 common space at /eos/experiment/drd3/TB-data/SPSApril2025 but a local copy is also preserved at the beam area on the telescope itself. We wrote all the relevant information in the CodiMD here: https://codimd.web.cern.ch/gPvzzfnmSwOemAu2yAu_xQ?view#
Information on how to connect to the PC in the control room if you want to access the local copy of the data:
- Control Room PC
- Ubuntu 20.04
- Name: pcaidarc
- username: telescope
- password: telescope+
- Interfaces:
- External to Internet:
- Name: enx58ef68b4e3d2
- IP address: 128.141.149.69
- Gateway: 128.141.149.1
- DNS: 127.0.0.53
- Login ssh: ssh -X telescope@128.141.149.69
- The specific name depends on the USB-Ethernet connector: If the device changes, the name changes.
- To the Internal Network:
- Name: eno1
- IP address: 192.168.5.251
- Gateway: 192.168.5.251
- SubNet: 255.255.255.0
- DNS: 137.138.17.5 , 137.138.16.5