<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Folks,
<div class=""><br class="">
</div>
<div class="">As we discussed at CALCOM last week, it is time to converge on completing the creation and</div>
<div class="">filling of the hardware status tables for the different subsystems.</div>
<div class=""><br class="">
</div>
<div class="">We agreed on a status definition convention last year and the definitions for the different subsystems </div>
<div class="">are linked to a document on the CALCOM wikipage at:</div>
<div class=""><a href="https://clasweb.jlab.org/wiki/images/b/b9/Clas12-hardware-status-words.pdf" class="">https://clasweb.jlab.org/wiki/images/b/b9/Clas12-hardware-status-words.pdf</a></div>
<div class="">Please review this and let me know if you have any questions or if anything has changed. The basic convention </div>
<div class="">is that a channel status of “0” is good. Other faults or issues are assigned a postive integer.</div>
<div class=""><br class="">
</div>
<div class="">In the near future, we will get reports from the different subsystem teams on the creation of the</div>
<div class="">tables and their filling with values that reflect the true hardware status.</div>
<div class=""><br class="">
</div>
<div class="">In addition, I would like at some point when we have our tables ready and the reconstruction code</div>
<div class="">is set to handle the tables, that we run some MC to do a check to make sure that the knock-out is working</div>
<div class="">as expected.</div>
<div class=""><br class="">
</div>
<div class="">Other issues are how we handle 1) inefficient channels (keep them as status “0” and account for them</div>
<div class="">with an efficiency correction or knock them out) and 2) channels that started the run period functioning</div>
<div class="">and then dropped out during the run (or vice versa). These points will be discussed at an upcoming CALCOM </div>
<div class="">meeting so that we have clarity on table filling.</div>
<div class=""><br class="">
</div>
<div class="">Given that this work on the status tables is supposed to be completed and validated before pass-2 cooking,</div>
<div class="">we want to converge on this by (roughly) the end of next month.</div>
<div class=""><br class="">
</div>
<div class="">Regards,</div>
<div class="">Daniel</div>
<div class=""><br class="">
<div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class="">*****************************************************************************<br class="">
*<br class="">
* Dr. Daniel Carman <a href="mailto:carman@jlab.org" class="">e-mail: carman@jlab.org</a><br class="">
* Staff Scientist office: (757)-269-5586 <br class="">
* Jefferson Laboratory web: <a href="http://userweb.jlab.org/~carman" class="">http://userweb.jlab.org/~carman</a><br class="">
*<br class="">
*****************************************************************************<br class="">
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br class="">
</div>
</body>
</html>