Difference between revisions of "Data Acquisition System and Triggers"

From Tritium Experiments Group
Jump to navigation Jump to search
m
Line 29: Line 29:
  
  
−
=== Trigger Checkout Plan (Experts Only) ===
+
=== Trigger Checkout Plan Fall 2018 (Experts Only) ===
 
In general, we need one hall access if everything works fine.
 
In general, we need one hall access if everything works fine.
 
==Step 1==
 
==Step 1==
 
<ol>
 
<ol>
−
<li> Use remote scopes with inputs S0 (from FIFO), S2 (from FIFO), GC (from FIFO), S0&S2 (from Logic Unit) and S0||S2 (from Logic Unit)
+
<li> Use remote scopes with inputs S0 (from FIFO), S2 (from FIFO), GC (from FIFO), S0&S2 (from Logic Unit)  
−
<li> Verify that the S0 and S2 signals are as they should be (see picture (<b>needs to be added!!!</b>))
+
<li> Verify that the S0 and S2 signals are as they should be  
−
<li> Verify that the S0&&S2 signal is within the GC signal with the desired time distance (see picture (<b>needs to be added!!!</b>))
+
<li> Verify that the S0&&S2 signal is within the GC signal with the desired time distance  
−
<li> Verify that the S0||S2 signal is within the GC signal with the desired time distance. Take also into account the extra cable delay from the S0|S2 logic unit to the (S0||S2)&&GC logic unit (see picture (<b>needs to be added!!!</b>))
+
<li> The reference logs are for the LHRS https://logbooks.jlab.org/entry/3512251 and https://logbooks.jlab.org/entry/3512265
 +
<li> The reference logs are for the RHRS https://logbooks.jlab.org/entry/3512332 and https://logbooks.jlab.org/entry/3519580 **
 +
( For the RHRS only the Tektronix Scope shows the trigger settings which are shown on the Agilent scope in the reference halog entries)
 +
 
 +
*NOTE: The S0&&S2 and S0||S2 times could be also estimated from the S0 and S2 signals with the known delays from the trigger schematics if there is no second remote scope available.
  
−
*NOTE: The S0&&S2 and S0||S2 times could be also estimated from the S0 and S2 signals with the known delays from the trigger schematics if there is no remote scope available for the RHRS.
 
 
<li> If necessary go to the hall and change individual trigger delays!
 
<li> If necessary go to the hall and change individual trigger delays!
 
</ol>
 
</ol>

Revision as of 23:47, 25 September 2018

Back to Installation and Commissioning

Overview

(see Tritium DAQ page)

Key Runs

Run-No E' Theta (Degree) Targets Current Prescale Total Events Comments
0000 3.10 17.58 H3 22.5 1/1/1 25000?


Trigger Checkout Plan Fall 2018 (Experts Only)

In general, we need one hall access if everything works fine.

Step 1

  1. Use remote scopes with inputs S0 (from FIFO), S2 (from FIFO), GC (from FIFO), S0&S2 (from Logic Unit)
  2. Verify that the S0 and S2 signals are as they should be
  3. Verify that the S0&&S2 signal is within the GC signal with the desired time distance
  4. The reference logs are for the LHRS https://logbooks.jlab.org/entry/3512251 and https://logbooks.jlab.org/entry/3512265
  5. The reference logs are for the RHRS https://logbooks.jlab.org/entry/3512332 and https://logbooks.jlab.org/entry/3519580 ** ( For the RHRS only the Tektronix Scope shows the trigger settings which are shown on the Agilent scope in the reference halog entries)
    • NOTE: The S0&&S2 and S0||S2 times could be also estimated from the S0 and S2 signals with the known delays from the trigger schematics if there is no second remote scope available.
  6. If necessary go to the hall and change individual trigger delays!
  • In parallel: Check S0, S2 and GC timings with Tong's and Jason's scripts.

Step 2

  1. Go to the hall and plug in the trigger signals and S2 on the 4-channel scopes.
  2. Check the individual trigger delays with respect to each and other and S2 (leads the time for S0&S2 and S0&S2&GC). Keep in mind to take also into account different cable length of the triggers from the logic unit to the TS input.
  3. If necessary go to the hall and modify the cables.
  • In parallel: Check trigger time distributions with Shujie's script.

Remote Scope Access

FADC Check

  1. Modify FADC readout list to switch to raw sample mode:
    • LHRS: on adaq@adaq1:
    1. "ssh -Y adaq@halladaq8"
    2. "cd fadc_mike/BlkRead"
    3. open "roc31_tritium_list.c"
    4. change "FADC_MODE" to "10"; save and exit;
    5. "make"
    • RHRS: on adaq@adaq2:
    1. "ssh -Y adaq@intelha3"
    2. "cd tritium_fadc/BlkRead/"
    3. open "roc20_tritium_list.c"
    4. change "FADC_MODE" to "10"; save and exit;
    5. "make"
  2. "Reset" and "Download" coda;
  3. Check the ROC31/ROC20 coda window to make sure it's in mode 10;
  4. Take runs with trigger T1=T2=T3=1 for LHRS, and T4=T5=T6=1 for RHRS;
  5. Decode a run with FADC decoder: on a-onl@aonl1
    1. gotritium;
    2. cd scripts/FADC_decode;
    3. ./FADCcom
  6. check /chafs1/work1/tritium/FADC_rootfiles/fadc_*.root one channel by one channel. Any under/overflow? Is the window including entire signal? Is the start point of signal 17 samples away to the window beginning?
  7. Also there is a txt in scripts/FADC_decode/results. Make sure all the overflow/underflow/bad pedestal are 0 percent for LHRS slot 6, 7, 8 (chan 0 -12), and RHRS slot 13, 14, 15(chan 0 -12);
  8. If any of the requirement above doesn't satisfied, call Mike or Hanjie to adjust it.
  9. Very important ! ! ! Remember to switch back to mode 9 after taking mode 10 runs ! ! !
Retrieved from "https://wiki.jlab.org/tegwiki/index.php?title=Data_Acquisition_System_and_Triggers&oldid=2982"