<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    I agree. The gain from saving the module info is speculative at this
    point.<br>
    <br>
    <div class="moz-cite-prefix">On 05/26/2016 07:23 AM, Curtis A. Meyer
      wrote:<br>
    </div>
    <blockquote cite="mid:36DF9BF9-A95B-4593-B884-2CAED98DDBB4@cmu.edu"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      Unless we have a reallly good reason (that I don’t see), we should
      avoid a large increase to
      <div class="">the REST footprint. Our goal has been for that to be
        compact an movable. Let’s not bloat </div>
      <div class="">it.</div>
      <div class=""><br class="">
      </div>
      <div class="">Curtis<br class="">
        <div class="">
          <span class="Apple-style-span" style="border-collapse:
            separate; color: rgb(0, 0, 0); font-family: Helvetica;
            font-style: normal; font-variant: normal; font-weight:
            normal; letter-spacing: normal; line-height: normal;
            orphans: 2; text-align: -webkit-auto; text-indent: 0px;
            text-transform: none; white-space: normal; widows: 2;
            word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
            -webkit-border-vertical-spacing: 0px;
            -webkit-text-decorations-in-effect: none;
            -webkit-text-size-adjust: auto; -webkit-text-stroke-width:
            0px; ">
            <div class="">
              <div class="">---------</div>
              <div class="">Curtis A. Meyer<span class="Apple-tab-span" style="white-space: pre; ">                   </span>MCS Associate
                Dean for Faculty and Graduate Affairs</div>
              <div class="">Wean:    (412) 268-2745<span class="Apple-tab-span" style="white-space: pre; ">   </span>Professor
                of Physics</div>
              <div class="">Doherty: (412) 268-3090<span class="Apple-tab-span" style="white-space: pre; ">   </span>Carnegie
                Mellon University</div>
              <div class="">Fax:         (412) 681-0648<span class="Apple-tab-span" style="white-space: pre; ">       </span>Pittsburgh,
                PA 15213</div>
              <div class=""><a moz-do-not-send="true"
                  href="mailto:curtis.meyer@cmu.edu" class="">curtis.meyer@cmu.edu</a><span class="Apple-tab-span" style="white-space: pre; ">   </span><a class="moz-txt-link-freetext" href="http://www.curtismeyer.com/">http://www.curtismeyer.com/</a></div>
            </div>
            <div class=""><br class="">
            </div>
          </span><br class="Apple-interchange-newline">
        </div>
        <br class="">
        <div>
          <blockquote type="cite" class="">
            <div class="">On May 25, 2016, at 9:52 PM, Paul Mattione
              <<a moz-do-not-send="true" href="mailto:pmatt@jlab.org"
                class="">pmatt@jlab.org</a>> wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <div class="">Well, if, for example, the timing in a TOF
                paddle was mis-calibrated, rather than having an
                acceptance hole, you may not want to cut on the timing
                from that paddle at all when you do your analysis.  But
                you’d need to have the paddles saved to do that.  <br
                  class="">
                <br class="">
                Perhaps this doesn’t work for the calorimeters though.  <br
                  class="">
                <br class="">
                - Paul<br class="">
                <br class="">
                On May 25, 2016, at 9:47 PM, Shepherd, Matthew <<a
                  moz-do-not-send="true"
                  href="mailto:mashephe@indiana.edu" class=""><a class="moz-txt-link-abbreviated" href="mailto:mashephe@indiana.edu">mashephe@indiana.edu</a></a>>
                wrote:<br class="">
                <br class="">
                <blockquote type="cite" class=""><br class="">
                  Paul,<br class="">
                  <br class="">
                  I'd argue that if we find out a detector element is
                  inefficient or miscalibrated, we modify our MC to
                  simulate this effect and then it will be accounted for
                  in our efficiency determination.  Some fiducial cuts
                  will need to be made, but I don't think that will
                  require module information.  Saving only the module
                  information for the block with the most energy in a
                  shower doesn't seem to be too useful.  <br class="">
                  <br class="">
                  Matt<br class="">
                  <br class="">
---------------------------------------------------------------------<br
                    class="">
                  Matthew Shepherd, Associate Professor<br class="">
                  Department of Physics, Indiana University, Swain West
                  265<br class="">
                  727 East Third Street, Bloomington, IN 47405<br
                    class="">
                  <br class="">
                  Office Phone:  +1 812 856 5808<br class="">
                  <br class="">
                  <blockquote type="cite" class="">On May 25, 2016, at
                    5:50 PM, Paul Mattione <<a moz-do-not-send="true"
                      href="mailto:pmatt@jlab.org" class="">pmatt@jlab.org</a>>
                    wrote:<br class="">
                    <br class="">
                    Should we save the detector elements in REST?  In
                    other words, the:<br class="">
                    <br class="">
                    BCAL module, FCAL column/row, SC paddle, TOF
                    paddles, TAGM counters, TAGH columns<br class="">
                    <br class="">
                    We haven’t been so far, but I think they could be
                    useful.  For example, if we determine later that a
                    detector element is inefficient, or miscalibrated,
                    we may need to cut all data from that particular
                    detector element from our analyses.  It would cost
                    an extra couple bytes per object.  Thoughts?  <br
                      class="">
                    <br class="">
                    - Paul<br class="">
                    <br class="">
                    <br class="">
                    _______________________________________________<br
                      class="">
                    Halld-offline mailing list<br class="">
                    <a moz-do-not-send="true"
                      href="mailto:Halld-offline@jlab.org" class="">Halld-offline@jlab.org</a><br
                      class="">
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/halld-offline">https://mailman.jlab.org/mailman/listinfo/halld-offline</a><br class="">
                  </blockquote>
                  <br class="">
                </blockquote>
                <br class="">
                <br class="">
                _______________________________________________<br
                  class="">
                Halld-offline mailing list<br class="">
                <a moz-do-not-send="true"
                  href="mailto:Halld-offline@jlab.org" class="">Halld-offline@jlab.org</a><br
                  class="">
                <a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/halld-offline">https://mailman.jlab.org/mailman/listinfo/halld-offline</a><br
                  class="">
              </div>
            </div>
          </blockquote>
        </div>
        <br class="">
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Halld-offline mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Halld-offline@jlab.org">Halld-offline@jlab.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/halld-offline">https://mailman.jlab.org/mailman/listinfo/halld-offline</a></pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
<a class="moz-txt-link-abbreviated" href="mailto:marki@jlab.org">marki@jlab.org</a>, (757)269-5295
</pre>
  </body>
</html>