...
Latest Run 17 LCLS/ESTB (2018 Fall schedule)
- Dec/13-18/2018: T578 HGTD
- Dec/10-12/2018: T539 sharing T-577 period. [Event log]
- Nov/2-7/2018: T539 + T545 ITk Pixel. [Event Log log]
- Oct/3-7/2018: T578 HGTD
- May/30-Jun/5/2018 T545 + T539: Joint ITk pixel session with first RD53A module (+T578 parasitic). [Event log]
- Apr/5-9/2018 T578: UCSC HGTD run with first ESTB beam after kicker magnet upgrade. [Event log] [Report]
- Sep/26-Oct/4/2016 T-545 + T-539: Joint ITk pixel session for new ITk devices and some additional irradiated IBL FE-I4 module runs. Event log
- Jul/7-19/2016 T-539 + T-545: Combined ITk pixel session and continued irradiated FE-I4 module tests. Event log
- May/05-10/2016 T-539: Data with irradiated IBL FE-I4 modules for simulation model. Event log
- Jan/12-25/2016 T-534: Recommissioning of CALADIUM telescope and ATLAS DUT readout.
- Oct/2015 Caladium installation: 151030_caladium_at_slac_report.pdf, 151030_caladium_pictures.pdf
- May/01-15/2014 T-516: Various ATLAS ITk pixel upgrade samples.
...
--> check in eudaq Run Control, that Produce TLU is connected
5. Start DUT data producer(s) if not running telescope by itself.
- For standard RCE based DUT readout, thisstarting shouldfrom bean justar-eudaq startingconsole rceOfflineProducerterminal on esadutdaq1.
- For YARRssh based-Y readoutesadutdaq1 (for-l beam rigger runs), login to pixel@172.27.104.52 as in the TLUProducer case, then [pw=TestBeamUser] cd ~/daq/rce source ./scripts/setup-env.sh
cd YarrEudaqProducer
bin/YarrProducerrceOfflineProducer -r 0 -h configs/controller/specCfgExtTrigger.json -c configs/connectivity/example_rd53a_setup.json -s configs/scans/rd53a/std_exttrigger.json -r 172.20.100.8i 192.168.1.1 -d ar-eudaq
- For YARR based readout (for beam rigger runs),
ssh -XY pixel@esadutlbnl1 (pw=Testbeam)
cd YarrEudaqProducer
./start_1.sh
6. Configure EUDAQ in eudaq Run Control
- select init file (should just use the
6. Configure EUDAQ in eudaq Run Control
- select init file (should just use the default example) and init; then select Config file
(Caladium only exercise config: no-beam: ni_autotrig;
beam: ni_coins, June test beam 2018, ni_coins_YARR)
- Press Config
- wait till all Connections are green (OK)
7. Start Run
- Press Start (wait till all green)
--> check, that Trigger and Event Built numbers are increasing
--> check OnlineMonitor, and reset (upper left x-button)
8. Stop
- Re-configure (5.) and Re-Run (6.)
OR
- Terminate and press "Reset" in MI26.exe at NI crate to stop sensors --> check 2.0 Amps
...
- For HSIO2-module communication: Ground wire between HSIO2 LV supply Molex pigtail and pixel module LV PSU ground
- For HSIO2-TLU communication: Lemo cable between TLU trig0 TTL and any of the HSIO2 main board LEMO bank socket
If you are not running the system from the ESA console next to the EUDET, but from some public nodes at SLAC, you need to first hop onto an ESA public machine on the 172.27.100 subnet and login as yourself e.g.
...
ssh -Y esadutdaq1 -l beam [pw=TestBeamUser]
cd ~/daq/rce
source ./scripts/setup-env.sh...
ssh -XY pixel@esadutlbnl1 (ask Timon or Ben for the password or don't close the terminal(pw=Testbeam)
cd yarr-eudet/eudaqYarrEudaqProducer
bin/yarr-fe65p2-producer -n YARR -r 172.27.100.8./start_1.sh
In addition to starting the producer, In addition to starting the producer, one needs to modify the DUTMask in the .conf. Add +4 to include YARR. There is no need to add anything else because the configuration is currently hard-coded into the producer (and the Latency = 43 and Trig Count = 3 seem good so there should not be a need to touch this).
To fully kill this producer if it gets stuck or when terminating the run control, do a ctrl+Z to move it to the background and then kill in the usual way with ps ux | grep yarr. Then, kill -9 <pid> where <pid> is the id of the producer from the ps uxaux.
After stopping a run, there will be some offline plots in ~/yarr-eudet/eudaq/data. There is also a simple script for offline analysis:
...
../src/bin/read_rawData data<file>.raw #<file> is <Dutname>_<runnumber>
On occasion, you the trigger counter will increase, but no events will be built. This could be because the chip is in a funny state. We can reconfigure the chip and power cycle:
to run a digital scan
cd
cd Yarr/src
./test_digi_1.sh
qpdfview data/last_scan/*.p*
check that they look okay (note that syncrhonous is off). To power cycle
minicom -D /dev/ttyUSB1
ctrl-a z
ctrl-a e
++addr 3
to check what you are talking to:
*IDN?should be Agilent Technologies ... To turn it off:
OUTPUT OFF OUTPUT ON ctrl-a z x
Infrastructure Utilities
...