...

The SLAC End Station A Test Beam (ESTB) was re-establishing in 2014 to take small fraction of SLAC LCLS beams into End Station test beam line. The operation is largely parasitic to the LCLS operations with electron beams in the 5-13 GeV range depending on the LCLS operation energy. From the FACET/ESTB portal, you can navigate to info on proposals, new user registrations etc. ESTB beam schedule mostly just follow the LCLS Run schedule (which may be not always up to date). The CALADIUM EUDET telescope owned by Carleton University has been installed at the end of ESTB as a precision tracking telescope with 6 planes of CMOS/MIMOSA sensors (1152x576 18.4x18.4um pixels) with ~3 micron spatial resolution. User Device Under Test (DUT) can be mounted on a movable stage in the middle of the telescope. For ATLAS pixel test beam users, a HSIO2/RCE based DUT readout will be provided as a standard readout utility.     

...

The list of sessions below may be incomplete (welcome to add missing sessions). Links behind each session dates below navigates to activities on individual sessions. In case of confluence wiki access issue in either viewing or editing the Event log page yourself, if only needs a trivial registration to gain access.  

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/12-67/2018: T539 + T545 ITk Pixel.  [Event 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 YARR based readoutssh (for-Y beamesadutdaq1 rigger runs), login to pixel@172.27.104.52 as in the TLUProducer case, then 

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

 
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

EUDAQ Online Framework

The EUDAQ software operation involves 3 types of main entities: 

-l beam   [pw=TestBeamUser]
       cd ~/daq/rce 
       source ./scripts/setup-env.sh

       rceOfflineProducer -r 0 -i 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 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

EUDAQ Online Framework

The EUDAQ software operation involves 3 types of main entities: 

TLUProducer, rceOfflineProducer

...

While the DUT readout can be of variety of ways, the RCE readout setup is provided for at least ATLAS pixel users as a standard utility. As of July/2018, the DUT RCE readout is upgrading to HSIO-II setup with EUDAQ-1.7, with the dedicated ESADUTDAQ1 server also upgraded to a fanless Kindel Kingdel PC residing the beam tunnel in the EUDET rack next to the NI crate as the DUT RCE readout host. HSIO-II has the DTM mezzanine with the Gen-3 ZYNQ based RCE operating Centos-7 on the ARMS CPU that communicates with external world via its native 1Gb/s Ethernet. More general information on HSIO-II/RCE can be found on the RCE Development Lab Twiki. If the RCE readout setup with HSIO-II is dissembled and reinstalled, it is important to remember two important grounding connections to ensure LVDS communications have proper DC reference levels:

• 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 (pw=Testbeam)

    (ask Timon or Ben for the password or don't close the terminal)cd YarrEudaqProducer
    cd yarr-eudet/eudaq    bin/yarr-fe65p2-producer -n YARR -r 172.27.100.8./start_1.sh

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

After stopping a run, there will be some offline plots in ~/yarr-eudet/eudaq/data.  There is also a simple script for offline analysis:

    cd ~/yarr-eudet/eudet

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

After stopping a run, there will be some offline plots in ~/yarr-eudet/eudaq/data.  There is also a simple script for offline analysis:

    cd ~/yarr-eudet/eudet

    ../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    ../src/bin/read_rawData data<file>.raw #<file> is <Dutname>_<runnumber>

Infrastructure Utilities

...