<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi, <br>
<br>
I pasted the minutes of the todays HPS controls meeting to the
bottom of this message and posted them at:<br>
<br>
<a class="moz-txt-link-freetext" href="https://confluence.slac.stanford.edu/display/hpsg/2013.06.10+Biweekly">https://confluence.slac.stanford.edu/display/hpsg/2013.06.10+Biweekly</a><br>
<br>
Hovanes. <br>
<br>
<h2>Minutes</h2>
<p>Present at JLab: Hovanes, Nerses, Stepan, Sergey .</p>
<p>Present at SLAC: Sho, Pele.</p>
<h4><a name="2013.06.10Biweekly-MeetingSchedule"></a>Meeting
Schedule</h4>
<ul>
<li>The meetings will be held biweekly until there is a need for
weekly meetings.</li>
</ul>
<h4><a name="2013.06.10Biweekly-Representativesfromdetectorgroups"></a>Representatives
from detector groups</h4>
<p>It was suggested that it would be good to have a single point
of contact for each detector group even for the cases when more
than one person contributes to the controls for a particular
detector.</p>
<ul>
<li>Stepan will be representing ECAL</li>
<li>F.-X. will be representing beamline</li>
<li>Sho will find out who will be the contact for SVT</li>
<li>Muon system did not have anyone at the meeting, we will find
this out offline.</li>
</ul>
<h4><a name="2013.06.10Biweekly-Volunteersforslowcontrols"></a>Volunteers
for slow controls</h4>
<ul>
<li>Ani Simonyan from Yerevan volunteered to help with the ECAL
voltage controls.</li>
<li>Show and Pele will both contribute to SVT controls. Hovanes
promised to help them with EPICS issues.</li>
</ul>
<h4><a name="2013.06.10Biweekly-HallBcomputinginfrastructure"></a>Hall
B computing infrastructure</h4>
<ul>
<li>In a couple of weeks Sergey will be able to move equipment
into Hall B counting house. Hovanes asked an access to a Linux
server with <b><em>epics, clas12run, clasrun</em></b> local
accounts. </li>
<li>Stepan suggested to use CLAS6 directory structure to
minimize efforts.</li>
<li>HPS will develop its custom software, but will rely on Hall
B EPICS BASE, support, extensions. Details will be worked out
offline.</li>
<li>Hovanes needs to compile a full list of items that need to
be controlled during the HPS run so that there is a finite
number of things that need to be checked when moving to
VxWorks 5.5 and EPICS 3.14.12.13 .</li>
</ul>
<h4><a name="2013.06.10Biweekly-&nbsp;ECALvoltagecontrols"></a> ECAL
voltage controls</h4>
<ul>
<li>ECAL needs controls for HV for APDs and LV for preamps.</li>
<li>ECAL HV will use old CAEN SY1527 chassis wilth A1520 HV
boards that were used for DVCS IC. Basic EPICS support exists.</li>
<li>ECAL LV system will use a single MPV18008 board in Wiener
MPOD chassis. Basic EPICS support exists.</li>
<li>SY1527 HV chassis with the boards soon will be moved into
PCAL area (Stepan). They will be connected to the internal
Hall B network.</li>
<li>SVT group will let us use their spare MPOD chassis, although
we might not be able to physically move it to the most
convenient place for us. It will be on Hall B network.</li>
<li>The final mapping of the channels and detector modules is
not finalized, it is expected to be ready in approximately one
month.</li>
</ul>
<br>
</div>
</body>
</html>