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