Difference between revisions of "Data Acquisition System and Triggers"

From Tritium Experiments Group
Jump to navigation Jump to search
 
(44 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
[https://wiki.jlab.org/tegwiki/index.php/Installation_and_Commissioning <b>Back to Installation and Commissioning</b>]
+
[https://wiki.jlab.org/tegwiki/index.php/Additional_Installation_and_Commissioning <b>Back to Installation and Commissioning</b>]
 
=== Overview===
 
=== Overview===
−
[http://hallaweb.jlab.org/12GeV/experiment/E12-07-108/DAQ/HallA_hrs_daq.pdf <B>Vince's detailed Writeup about HRS (some information is outdated for tritium)</B>]
+
(see [https://wiki.jlab.org/tegwiki/index.php/Tritium_DAQ_page Tritium DAQ page])
  
−
=== Trigger Checkout Plan (Experts Only) ===
+
=== Key Runs ===
 +
<table border="1"  style="width:80%">
 +
  <tr>
 +
    <td>Run-No</td>
 +
    <td>E'</td>
 +
    <td>Theta (Degree)</td>
 +
    <td>Targets</td>
 +
    <td>Current</td>
 +
    <td>Prescale</td>
 +
    <td>Total Events</td>
 +
    <td>Comments</td>
 +
  </tr>
 +
 +
  <tr>
 +
    <td> 0000 </td>
 +
    <td>3.10</td>
 +
    <td>17.58</td>
 +
    <td>H3</td>  
 +
    <td>22.5</td>
 +
    <td>1/1/1</td>
 +
    <td>25000?</td>
 +
    <td> </td>
 +
  </tr>
 +
</table>
 +
 
 +
 
 +
=== 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==
+
 
 
<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) and T1/T4, T2/T5 and T3/T6
−
<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> 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 compared to the scopes.
 +
<li> The reference logs for the LHRS are https://logbooks.jlab.org/entry/3512251 and https://logbooks.jlab.org/entry/3512265
 +
<li> The reference logs for the RHRS are 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>
 
* In parallel: Check S0, S2 and GC timings with Tong's and Jason's scripts.
 
* In parallel: Check S0, S2 and GC timings with Tong's and Jason's scripts.
−
 
−
== Step 2 ==
 
−
<ol>
 
−
<li> Go to the hall and plug in the trigger signals and S2 on the 4-channel scopes.
 
−
<li> 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.
 
−
<li> If necessary go to the hall and modify the cables.
 
−
</ol>
 
 
* In parallel: Check trigger time distributions with Shujie's script.  
 
* In parallel: Check trigger time distributions with Shujie's script.  
  
 +
== [https://wiki.jlab.org/tegwiki/index.php/Howto_access_remote_scopes Remote Scope Access] ==
  
−
== LHRS scopes ==
 
  
−
* A 4-chan scope and a 2-chan scope is installed. Both scopes are from Tektronix.
+
== FADC Check ==
−
* The IP address of the 4-chan scope is 129.57.192.253.
+
<ol>
−
* The IP address of the 2-chan scope is 129.57.164.37 or hascope1.
+
<li>Modify FADC readout list to switch to raw sample mode:
−
* Both scopes are accessible in observer mode if you type in the IP address in the browser.
+
  <ul>
−
*To access them in control mode, one has to open /escope/index.html in the adaq home folder with a browser.
+
    <li>LHRS:    on adaq@adaq1: 
−
* The following inputs are currently plugged into the 4-chan scope for trigger checkout step 1 (12/01/17):
+
    </ul>
−
{| border="1"
+
    <ol>
−
!Channel!!Signal
+
      <li>"ssh -Y adaq@halladaq8"
−
|-
+
      <li>"cd fadc_mike/BlkRead"
−
||1||S0
+
      <li>open "roc31_tritium_list.c"
−
|-
+
      <li>change "FADC_MODE" to "10"; save and exit;
−
||2||S2
+
      <li>"make"
−
|-
+
    </ol>
−
||3||GC
 
−
|-
 
−
||4||S0&S2
 
−
|-
 
−
|}
 
−
* The following inputs are currently plugged into the 2-chan scope for trigger checkout step 1 (12/01/17):
 
−
{| border="1"
 
−
!Channel!!Signal
 
−
|-
 
−
||1||GC
 
−
|-
 
−
||2||(S0 OR S2)
 
−
|-
 
−
||ext||S0&S2&GC
 
−
|-
 
−
|}
 
−
* For the power remote control the 4-chan scope is plugged in hareboot2 channel 6 and the 2-chan scope is plugged in hareboot2 channel 8.
 
  
−
== RHRS scopes ==
+
  <ul>
 +
  <li>RHRS:    on adaq@adaq2: 
 +
    </ul>
 +
    <ol>
 +
      <li>"ssh -Y adaq@intelha3"
 +
      <li>"cd tritium_fadc/BlkRead/"
 +
      <li>open "roc20_tritium_list.c"
 +
      <li>change "FADC_MODE" to "10"; save and exit;
 +
      <li>"make"
 +
    </ol>
  
−
* A 4-chan scope with remote connection is installed. It is a MSO-X-3024A from Agilent.
+
<li>"Reset"  and "Download" coda;
−
* The IP address of the 4-chan scope is 129.57.164.227.
+
    <li>Check the ROC31/ROC20 coda window to make sure it's in mode 10;
−
* To access the scope type in the IP address in a browser (<b>It doesn't currently work from the adaq2 computer!</b>). Click on "Browser Web Control" in the web page and choose "Table Remote Front Panel" afterwards.
+
<li>Take runs with trigger T1=T2=T3=1 for LHRS, and T4=T5=T6=1 for RHRS;
−
Alternatively, you can use vncviewer via the command "vncviewer 129.57.164.227:0".
+
<li>Decode a run with FADC decoder:  on a-onl@aonl1
−
* The following inputs are currently plugged into the 4-chan scope for trigger checkout step 1 (12/01/17):
+
  <ol>
−
{| border="1"
+
  <li>gotritium; 
−
!Channel!!Signal
+
  <li>cd scripts/FADC_decode;
−
|-
+
  <li>./FADCcom
−
||1||S0
+
  </ol>
−
|-
+
<li>check /chafs1/work1/tritium/FADC_rootfiles/fadc_*.root one channel by one channel.  
−
||2||S2
+
Any under/overflow? Is the window including entire signal? Is the start point of signal 17 samples away to the window beginning?
−
|-
+
<li>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);
−
||3||GC
+
<li>If any of the requirement above doesn't satisfied, call Mike or Hanjie to adjust it.
−
|-
+
<li>Very important ! ! ! Remember to switch back to mode 9 after taking mode 10 runs ! ! !
−
||4||S0&S2
 
−
|-
 
−
|}
 
−
* For the power remote control the 4-chan scope is plugged in hareboot32 channel 4
 

Latest revision as of 23:50, 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.

  1. Use remote scopes with inputs S0 (from FIFO), S2 (from FIFO), GC (from FIFO), S0&S2 (from Logic Unit) and T1/T4, T2/T5 and T3/T6
  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. 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 compared to the scopes.
  5. The reference logs for the LHRS are https://logbooks.jlab.org/entry/3512251 and https://logbooks.jlab.org/entry/3512265
  6. The reference logs for the RHRS are 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.
  7. 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.
  • 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=2983"