<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<style type="text/css">
<!--
html{color:#555555;}body{line-height:1.5;font-family:'Trebuchet MS','Helvetica Neue',Arial,Helvetica,sans-serif;font-size:87.5%;}h1{font-size:1.6em;}h2.field-label{display:inline-block;font-size:1em;padding-right:5px;min-width:10em;margin:0.3em;}.problem_report{line-height:1.5;max-width:60em;}fieldset.problem_report.resolved
legend{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAACXBIWXMAAA7EAAAOxAGVKw4bAAAAy0lEQVQ4jWP8//8/AyWAiZACd3f3/xYWFrht+f//P1a84t3e/0obff4rbfT5D1GGXR0LuoEr3+/7X3W4n2gvwA0gVSOKAcqbfPGGpImJCU45JgYGBoa7fpsZ22wLSbadgYGBgRE9GrF55Vf2BYbHjx8zYjWB0ljAcAGGExkZ/0MtwuoCggmJEBh4AzBS4pMnT/7fuXOH4dKlSwwnT56EiwcGBv43MDBgMDExYdDX12eQkZGBhAlyiC5YsOA/AwMDUXjLli3/iYoFQgAA+pSxZrXofD0AAAAASUVORK5CYII=);background-repeat:no-repeat;padding-left:18px;}fieldset.problem_report.needs_attention
legend{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABmJLR0QA/wD/AP+gvaeTAAAA9ElEQVR42sWTvUoDQRSFv9wMKWxSBVmzdhZJIwTWv9pyLWxTpbE1kBeJPoLxBazzBgGFKNqlHXAhsITUw1y7sMpmjER0YJrDPWcO556BPzhjYPJjlhfT82LUpxcK6Lo5U0JMgcu56tXy7BQajeBDpkAcAEdz1W6uyrLdYieK2DMmKCArcqczpH/ddc0msy+OkyQJC4h3N0ynx+Q5ALtUNs5q5U+8e+R+VPFi4kjk3NZqd++qUK+TZVnYwSfAOyvejeLXt/2qVG/dYoG1dqseBNco27bs/wXKWhIDB8AhcFLAH4Bn4Al4AUqT7RVC++6mv/JVPwDi3VGzomYvyAAAAABJRU5ErkJggg==);background-repeat:no-repeat;padding-left:18px;}.problem_report div.field-items{display:inline-block;}div.date-vitals p{font-size:87.5%;}a{text-decoration:none;}.Readme a:link,.Readme a:visited,.Readme
a:active{color:red;}
-->
</style>
</head>
<body id="mimemail-body" class="elog-logentry-notify">
<div id="center">
<div id="main">
<style>
<!--/*--><![CDATA[/* ><!--*/
div.field-vitals{
margin: 0.5em 0;
}
div.field-vitals .field-type-taxonomy-term-reference {
margin: 0.1em 0;
}
article.comment {
padding-left: 10px;
}
article.comment.odd {
background-color: #EEEEEE;
}
article.comment.even {
background-color: #DDDDDD;
}
div.node-content.logentry table{
width: auto;
border-collapse: collapse;
border-spacing: 0;
border-width: 1px;
}
div.node-content.logentry th{
border: inherit;
}
div.node-content.logentry blockquote{
background-color: #FFFFFF;
}
div.node-content.logentry caption{
font-size: 1em;
font-weight: normal;
}
table.field-vitals{
margin-top: 1em;
margin-bottom: 1em;
font-size: 87.5%;
}
table.field-vitals th{
vertical-align: middle;
text-align: left;
width: 15%;
padding: 0.1em;
}
table.field-vitals td{
vertical-align: middle;
text-align: left;
width: auto;
padding: 0.1em;
}
table.field-vitals td li {
margin-left: 0;
list-style-type: none;
list-style-image: none;
}
table.downtime {
width: 30em;
margin-bottom: 1em;
border: 1px black dotted;
}
table.downtime th {
text-align: center;
}
table.downtime td {
text-align: center;
}
tr.caption th {
border-bottom: none;
}
table.downtime tfoot{
background-color:#EEEEEE;
}
div.field-name-body{
margin: 1em 0;
font-size: 110%;
}
div.date-vitals p{
margin: .1em 0;
}
article div.ctools-collapsible-container{
margin-left: -5px;
clear: both;
}
#comment-form{
margin-left: 5px;
border: graytext outset medium;
-moz-border-radius: 15px;
border-radius: 15px;
padding: 1em;
}
div.comments-form-box {
margin-top: 2em;
margin-bottom: 5em;
}
h3.comment-title {
/* display: none; */
}
p.author-datetime{
font-weight: bold;
}
/*--><!]]>*/
</style><article id="node-361992" class="node node-logentry article ia-n clearfix" role="article"><header class="node-header"><h1 class="node-title" rel="nofollow">
<a href="https://logbooks.jlab.org/entry/3289248" rel="bookmark">DAQ Testing</a>
</h1>
</header><div class="date-vitals">
<p class="author-datetime">
Lognumber <a href="https://logbooks.jlab.org/entry/3289248" class="lognumber" data-lognumber="3289248">3289248</a>. Submitted by <a href="https://logbooks.jlab.org/user/davidl">davidl</a> on <time datetime="2014-07-08T11:35:50-0400" pubdate="pubdate">Tue, 07/08/2014 - 11:35</time>. </p>
<table class="field-vitals"><tr><th>Logbooks: </th><td><a href="https://logbooks.jlab.org/book/hdlog">HDLOG</a></td></tr><tr><th>Tags: </th><td><a href="https://logbooks.jlab.org/tag/daq">DAQ</a></td></tr><tr><th>Entry Makers: </th><td>timmer, gurjyan, furletov, abbottd</td></tr></table></div>
<div class="logentry node-content">
<p>We met to continue the program of large scale DAQ testing. </p>
<p>Participants: Sergey F., Vardan G., Carl T., Dave A., David L.</p>
<p>- Setup to run from hdops account by installing from hdsys account</p>
<p> - Installed new DAQ using hdsys into /gluex/daq/daq_dev_vers.<br />
To use this, one must do the following after logging into the hdops<br />
account:</p>
<p> source /gluex/daq/daq_dev_vers/work/online_setup.cshrc</p>
<p> - Changed permissions on “log” and “ddb” directories in cool so<br />
that hdops can write to them<br />
- Changed gluon50-daq to just gluon50 in ~/.rcm.ini so that ethernet<br />
interface would be used instead of IB. This was done because the<br />
IB interface is currently down<br />
- Removed the setup.xml file installed by default in $COOL_HOME/gluex<br />
since it was causing the platform to try and use “furletov” and “gluon50”<br />
instead of defaulting to the local machine (gluon02)<br />
- Built the mcROL.so in $DAQ_HOME/vme/src/rol_soft. Also modified<br />
the online_setup.cshrc script to set CODA_ROL to this directory</p>
<p>- 2 crate configuration: SoftROC</p>
<p> - Started up rcm.sh and selected:<br />
RUN: TEST<br />
SETUP: SoftROC<br />
TRIGGER: PULSER</p>
<p> - All components started OK (platform, PEB, ER, ROCSTPSC1, ROCSTPSC2, rcgui)<br />
- Configure failed. RTVs not set. Message is buried in exception from platform.<br />
- Tried resting and configuring again. RC again reports error “Control Supervisor is no registered”<br />
- Stop all components via rcm and restart<br />
- Noticed message from platform: “tee: log.platform: Permission Denied”. Both log<br />
and lock files appear to be in place however in the $COOL_HOME/gluex/log directory<br />
with correct timestamps and owned by hdops<br />
- setup.xml needs to be writable by hdops<br />
- rcm config. is in both .rcm.ini and a file in work. The /work file saves last settings<br />
and is used for storing last settings used. These may need to be consolidated.</p>
<p>At this point we switched over to testing the 50 crate system from Sergey's account.</p>
<p>- Testing 50 crate system fast startup and shutdown</p>
<p> - Attempt 1<br />
- All crates except roctrig1 started. roctrig1 was not responding to ping. Crate<br />
was power cycled remotely via:</p>
<p> rocs.sh trig:1 </p>
<p> (syntax is: basename:num1,num2,num3,..NumN or basename:num1:numN</p>
<p> - roctrig1 came up OK and restarted all components. started is much faster (few seconds)<br />
- tested fast shutdown of components. It worked within a few seconds as well</p>
<p> - Attempt 2<br />
- Configure failed due to some components connecting to the wrong gluon<br />
due to the direct connection being set to a different node than we’re on.<br />
(we’re using gluon50 and configuration used gluon53). Switching to using<br />
gluon53</p>
<p> - Attempt 3 (using gluon53)<br />
- Configure succeeded<br />
- Download succeeded<br />
- Prestart succeeded<br />
- Go succeeded (forgot to start softROCcontroller)</p>
<p> - Attempt 4<br />
- Reset and try again. (don’t kill any components)<br />
- Configure succeeded<br />
- Download succeeded<br />
- Started softROCcontroller<br />
- Prestart succeeded<br />
- Go succeeded<br />
- Data flowed for 1million events<br />
- Started hd_ana connecting to ER’s ET system. Very odd behavior:<br />
Event rate went up by a significant amount (to 1.5kHz to 2kHz from<br />
around 200Hz) when hd_ana was reading events from ET<br />
This propagated all of the way back to the ROCs.<br />
Stopping hd_ana caused rate to drop back down.<br />
Current theory is that there are too few events in the ET system created<br />
by the ER. The SEB is trying to grab 10 at a time, but the whole system<br />
has only 20. The addition of hd_ana which reads events 1 at a time<br />
smoothes out the flow resulting in fewer failed requests and therefore<br />
fewer sleeps waiting for events to appear.</p>
<p> - Attempt 5<br />
- Changing number of events CODA starts ET system with by editing<br />
COOL “Options/ERsoftROC.xml” file<br />
- Configure, Download, Prestart, and Go succeeded<br />
- Event rate behavior is the same.</p>
<p>This event speed-up phenomenon exposed an issue that will be addressed by the CODA group that<br />
should help smooth out and possibly speed up the data rate.</p>
<p>- Testing fast starts and stops</p>
</div>
<div class="attachment-box">
</div>
</article> </div>
</div>
</body>
</html>