Difference between revisions of "DVCS3 DAQ"

From Hall A Wiki
Jump to: navigation, search
(Stress test)
 
(72 intermediate revisions by 4 users not shown)
Line 15: Line 15:
  
 
|}
 
|}
 +
 +
See also [[DVCS3 crate and channel maps]] for information about the channel layouts.
 +
 +
=== Accessing the networked scope in the LHRS ===
 +
Log into ahut@halla-lpt1, open firefox, and navigate to hascope1.jlab.org.
 +
 +
===  Some ways to check the Calorimeter/spectrometer timing ===
 +
*  The easiest check will be to look at the distribution of waves in the ARS, this lets all channels be checked simultaneously
 +
*  If the timing is very far off, we can compare the timing of one block with the calorimeter ADC gate.  The calorimeter ADC gate is in CAEN TDC channel 9 (counting from 0), and Calorimeter block 001 with a 50mV threshold is in CAEN TDC channel 14.
 +
**  The ROOT command, <code>T->Draw("tdc_val[14]-tdc_val[9]","tdc_val[14]>0 && tdc_val[9]>0","")</code>, shows the distribution of the time differences.  From a DVCS cosmic run (10159), we can see that a well-timed trigger will result in an average difference value of about 400.<br /> [[Image:Pking_run10159_CB001_to_gate_timediff.png‎|200px]]
 +
**  This command, <code>T->Draw("adcval[1]:tdc_val[14]-tdc_val[9]","tdc_val[14]>0 && tdc_val[9]>0","*")</code>, will show the correlation of the block 001 ADC value against the timing difference.  Again from run 10159, we can see the strong ADC events are associated with time differences of about 400.<br /> [[Image:Pking_run10159_CB001adc_vs_CB001_to_gate_timediff.png‎|200px]]
 +
**  If the time difference is peaked later than 400, we can increase the DVCS ADC gate width setting to try to pick up sensitivity before making an access to adjust cable delays.  If the time difference is peaked substantially before 400, we will need to consider how to shift the triggering (and thus the ADC gate) earlier.
  
 
=== Stress test ===
 
=== Stress test ===
Line 21: Line 33:
 
* to check the disk occupency: as adaq@adaq1, "df -k /adaq1/data1/*"
 
* to check the disk occupency: as adaq@adaq1, "df -k /adaq1/data1/*"
 
* Analyze deadtime on any aonl machines: "godvcs", "cd marco/deadtime/", "analyzer", ".L deadtime.C", "deadtime(run_number)".
 
* Analyze deadtime on any aonl machines: "godvcs", "cd marco/deadtime/", "analyzer", ".L deadtime.C", "deadtime(run_number)".
 +
 +
*Please note: The tests were done on 06 November 2014. Times with no dates should be interpreted as done or observed on 06 November, otherwise the date is included in brackets.
 +
  
 
&nbsp;<p>
 
&nbsp;<p>
Line 26: Line 41:
 
<table border="1" style="width:100%">
 
<table border="1" style="width:100%">
 
<tr>
 
<tr>
<td>run number</td>
+
<td>Run number</td>
 +
<td>Buffer</td>
 
<td>DAQ start/stop time</td>
 
<td>DAQ start/stop time</td>
<td>DAQ rate (Hz) </td>
+
<td>DAQ rate TS11 (Hz) </td>
 +
<td>DAQ rate ROC27 (Hz) </td>
 
<td>Analysis ran on wich aonl?</td>
 
<td>Analysis ran on wich aonl?</td>
 
<td>Analysis start/stop time</td>
 
<td>Analysis start/stop time</td>
Line 34: Line 51:
 
<td>Time at end of copy of mss</td>
 
<td>Time at end of copy of mss</td>
 
<td>Occupency of the data disk at end of data taking</td>
 
<td>Occupency of the data disk at end of data taking</td>
<td>Marco's awesome plot</td>
+
<td>Live time</td>
 
<td>Prescale </td>
 
<td>Prescale </td>
 
</tr>
 
</tr>
Line 40: Line 57:
 
<tr>
 
<tr>
 
<td>2666</td>
 
<td>2666</td>
<td>12:43</td>
+
<td>None</td>
 +
<td>12:43/13:48</td>
 
<td>836.7</td>
 
<td>836.7</td>
 +
<td>N/A</td>
 
<td>4</td>
 
<td>4</td>
<td>13:42</td>
+
<td>15:27(rest.)/18:14</td>
<td></td>
+
<td>342.0</td>
<td></td>
+
<td>21:21</td>
<td></td>
+
<td>0.29</td>
<td></td>
+
<td>[[Image:run2666_deadtime_cptS2mANDCer.png|200px]]</td>
 
<td>4</td>
 
<td>4</td>
 
</tr>
 
</tr>
  
 
<tr>
 
<tr>
<td></td>
+
<td>2667</td>
<td></td>
+
<td>None</td>
<td></td>
+
<td>13:51/14:20</td>
<td></td>
+
<td>850.0</td>
<td></td>
+
<td>N/A</td>
<td></td>
+
<td>3</td>
<td></td>
+
<td>14:39(rest.)/15:15</td>
<td></td>
+
<td>684.0</td>
<td></td>
+
<td>22:45</td>
<td></td>
+
<td>0.3</td>
 +
<td>[[Image:run2667_deadtime_cptS2mANDCer.png|200px]]</td>
 +
<td>4</td>
 +
</tr>
 +
 
 +
<tr>
 +
<td>2669</td>
 +
<td>None</td>
 +
<td>14:25/14:55</td>
 +
<td>720.0</td>
 +
<td>700.0</td>
 +
<td>2</td>
 +
<td>14:39/17:01</td>
 +
<td>158.3</td>
 +
<td>00:15 (Nov. 7)</td>
 +
<td>0.31</td>
 +
<td>[[Image:run2669_deadtime_cptS2mANDCer.png|200px]]</td>
 +
<td>1</td>
 +
</tr>
 +
 
 +
 
 +
<tr>
 +
<td>2670</td>
 +
<td>None</td>
 +
<td>14:56/15:26</td>
 +
<td>752.0</td>
 +
<td>716.0</td>
 +
<td>1</td>
 +
<td>15:26(rest.)/18:06</td>
 +
<td>152.0</td>
 +
<td>01:41 (Nov. 7)</td>
 +
<td>0.33</td>
 +
<td>[[Image:run2670_deadtime_cptS2mANDCer.png|200px]]</td>
 +
<td>1</td>
 +
</tr>
 +
 
 +
<tr>
 +
<td>2673</td>
 +
<td>None</td>
 +
<td>15:43/16:14</td>
 +
<td>711.0</td>
 +
<td>690.0</td>
 +
<td>3(rest.2 on 1)</td>
 +
<td>21:04(rest.2)/23:34</td>
 +
<td>259.7</td>
 +
<td>03:46 (Nov. 7)</td>
 +
<td>0.35</td>
 +
<td>[[Image:run2673_deadtime_cptS2mANDCer.png|200px]]</td>
 +
<td>1</td>
 +
</tr>
 +
 
 +
<tr>
 +
<td>2674</td>
 +
<td>None</td>
 +
<td>16:25/16:56</td>
 +
<td>722.0</td>
 +
<td>718.0</td>
 +
<td>2</td>
 +
<td>16:43/18:23</td>
 +
<td>152.0</td>
 +
<td>04:45 (Nov. 7)</td>
 +
<td>0.35</td>
 +
<td>[[Image:run2674_deadtime_cptS2mANDCer.png|200px]]</td>
 +
<td>1</td>
 +
</tr>
 +
 
 +
<tr>
 +
<td>2675</td>
 +
<td>None</td>
 +
<td>16:52/17:22</td>
 +
<td>755.0</td>
 +
<td>730.0</td>
 +
<td>4</td>
 +
<td>17:06/19:32</td>
 +
<td>158.3</td>
 +
<td>06:15 (Nov. 7)</td>
 +
<td>0.36</td>
 +
<td>[[Image:run2675_deadtime_cptS2mANDCer.png|200px]]</td>
 +
<td>1</td>
 +
</tr>
 +
 
 +
<tr>
 +
<td>2676</td>
 +
<td>None</td>
 +
<td>17:25/crashed(17:45)</td>
 +
<td>870.0</td>
 +
<td>840.0</td>
 +
<td>1</td>
 +
<td>17:38/19:10</td>
 +
<td>152.0</td>
 +
<td>07:16 (Nov. 7)</td>
 +
<td>0.38</td>
 +
<td>[[Image:run2676_deadtime_cptS2mANDCer.png|200px]]</td>
 +
<td>1</td>
 +
</tr>
 +
 
 +
<tr>
 +
<td>2678</td>
 +
<td>ON</td>
 +
<td>17:52/18:25</td>
 +
<td>666.0</td>
 +
<td>648.0</td>
 +
<td>2</td>
 +
<td>21:06(rest.)/23:30</td>
 +
<td>158.3</td>
 +
<td>09:12 (Nov. 7)</td>
 +
<td>0.39</td>
 +
<td>[[Image:run2678_deadtime_cptS2mANDCer.png|200px]]</td>
 +
<td>1</td>
 +
</tr>
 +
 
 +
<tr>
 +
<td>2679</td>
 +
<td>ON</td>
 +
<td>18:28/18:54</td>
 +
<td>660.0</td>
 +
<td>640.0</td>
 +
<td>2</td>
 +
<td>18:38/20:18</td>
 +
<td>145.7</td>
 +
<td>13:15 (Nov. 7)</td>
 +
<td>0.39</td>
 +
<td>[[Image:run2679_deadtime_cptS2mANDCer.png|200px]]</td>
 +
<td>1</td>
 
</tr>
 
</tr>
  
 
</table>
 
</table>

Latest revision as of 14:52, 6 December 2014

ROC info

Please see https://logbooks.jlab.org/entry/3292168 for information.

Model Mac1 location Hostname IP Adress ROC Hardware ID CODA ROC
VME 002038046D12 LHRS DVCS crate 1 intelhadvcs1 (ROC27) 129.57.192.80 4 27
VME 002038046DC1 LHRS DVCS crate 2 intelhadvcs2 (ROC28) 129.57.192.86 6 28
VME 0020CEF603EA LHRS DVCS crate 3 intelhadvcs3 (ROC29) 129.57.192.91 5 29
VME 002038046D0C LHRS DVCS crate 4 intelhadvcs4 (ROC30) 129.57.192.92 0 30
VME Upper level crate intelha3 7

See also DVCS3 crate and channel maps for information about the channel layouts.

Accessing the networked scope in the LHRS

Log into ahut@halla-lpt1, open firefox, and navigate to hascope1.jlab.org.

Some ways to check the Calorimeter/spectrometer timing

  • The easiest check will be to look at the distribution of waves in the ARS, this lets all channels be checked simultaneously
  • If the timing is very far off, we can compare the timing of one block with the calorimeter ADC gate. The calorimeter ADC gate is in CAEN TDC channel 9 (counting from 0), and Calorimeter block 001 with a 50mV threshold is in CAEN TDC channel 14.
    • The ROOT command, T->Draw("tdc_val[14]-tdc_val[9]","tdc_val[14]>0 && tdc_val[9]>0",""), shows the distribution of the time differences. From a DVCS cosmic run (10159), we can see that a well-timed trigger will result in an average difference value of about 400.
      Pking run10159 CB001 to gate timediff.png
    • This command, T->Draw("adcval[1]:tdc_val[14]-tdc_val[9]","tdc_val[14]>0 && tdc_val[9]>0","*"), will show the correlation of the block 001 ADC value against the timing difference. Again from run 10159, we can see the strong ADC events are associated with time differences of about 400.
      Pking run10159 CB001adc vs CB001 to gate timediff.png
    • If the time difference is peaked later than 400, we can increase the DVCS ADC gate width setting to try to pick up sensitivity before making an access to adjust cable delays. If the time difference is peaked substantially before 400, we will need to consider how to shift the triggering (and thus the ADC gate) earlier.

Stress test

  • To run the analysis, on alternating aonl machines: "godvcs", "analyzer", ".L replay_DVCS.C", " replay_DVCS(run_number)".
  • MSS storage: /mss/halla/dvcs/raw/dvcs14*
  • to check the disk occupency: as adaq@adaq1, "df -k /adaq1/data1/*"
  • Analyze deadtime on any aonl machines: "godvcs", "cd marco/deadtime/", "analyzer", ".L deadtime.C", "deadtime(run_number)".
  • Please note: The tests were done on 06 November 2014. Times with no dates should be interpreted as done or observed on 06 November, otherwise the date is included in brackets.


 

Run number Buffer DAQ start/stop time DAQ rate TS11 (Hz) DAQ rate ROC27 (Hz) Analysis ran on wich aonl? Analysis start/stop time Analysis rate (Hz) Time at end of copy of mss Occupency of the data disk at end of data taking Live time Prescale
2666 None 12:43/13:48 836.7 N/A 4 15:27(rest.)/18:14 342.0 21:21 0.29 Run2666 deadtime cptS2mANDCer.png 4
2667 None 13:51/14:20 850.0 N/A 3 14:39(rest.)/15:15 684.0 22:45 0.3 Run2667 deadtime cptS2mANDCer.png 4
2669 None 14:25/14:55 720.0 700.0 2 14:39/17:01 158.3 00:15 (Nov. 7) 0.31 Run2669 deadtime cptS2mANDCer.png 1
2670 None 14:56/15:26 752.0 716.0 1 15:26(rest.)/18:06 152.0 01:41 (Nov. 7) 0.33 Run2670 deadtime cptS2mANDCer.png 1
2673 None 15:43/16:14 711.0 690.0 3(rest.2 on 1) 21:04(rest.2)/23:34 259.7 03:46 (Nov. 7) 0.35 Run2673 deadtime cptS2mANDCer.png 1
2674 None 16:25/16:56 722.0 718.0 2 16:43/18:23 152.0 04:45 (Nov. 7) 0.35 Run2674 deadtime cptS2mANDCer.png 1
2675 None 16:52/17:22 755.0 730.0 4 17:06/19:32 158.3 06:15 (Nov. 7) 0.36 Run2675 deadtime cptS2mANDCer.png 1
2676 None 17:25/crashed(17:45) 870.0 840.0 1 17:38/19:10 152.0 07:16 (Nov. 7) 0.38 Run2676 deadtime cptS2mANDCer.png 1
2678 ON 17:52/18:25 666.0 648.0 2 21:06(rest.)/23:30 158.3 09:12 (Nov. 7) 0.39 Run2678 deadtime cptS2mANDCer.png 1
2679 ON 18:28/18:54 660.0 640.0 2 18:38/20:18 145.7 13:15 (Nov. 7) 0.39 Run2679 deadtime cptS2mANDCer.png 1