<xml>
  <records>
    <record>
       <contributors>
          <authors>
             <author>Hill, J.O.</author>
          </authors>
       </contributors>
       <titles>
          <title>
             Lua-Language-Based Data Acquisition Processing EPICS Subscription Filters
          </title>
       </titles>
		 <publisher>JACoW Publishing</publisher>
       <pub-location>Geneva, Switzerland</pub-location>
		 <isbn>2226-0358</isbn>
		 <isbn>978-3-95450-209-7</isbn>
		 <electronic-resource-num>10.18429/JACoW-ICALEPCS2019-MOPHA058</electronic-resource-num>
		 <language>English</language>
		 <pages>342-346</pages>
       <pages>MOPHA058</pages>
       <keywords>
          <keyword>EPICS</keyword>
          <keyword>timing</keyword>
          <keyword>factory</keyword>
          <keyword>site</keyword>
          <keyword>data-acquisition</keyword>
       </keywords>
       <work-type>Contribution to a conference proceedings</work-type>
       <dates>
          <year>2020</year>
          <pub-dates>
             <date>2020-08</date>
          </pub-dates>
       </dates>
       <urls>
          <related-urls>
              <url>https://doi.org/10.18429/JACoW-ICALEPCS2019-MOPHA058</url>
              <url>https://jacow.org/icalepcs2019/papers/mopha058.pdf</url>
          </related-urls>
       </urls>
       <abstract>
          A previous paper described an upgrade to EPICS enabling client side tools at LANSCE to receive subscription updates filtered selectively to match a logical configuration of LANSCE beam gates, as specified dynamically by control room application programs. This update paper will examine evolving enhancements enabling Lua-language based data acquisition processing subscription update filters, specified by snippets of Lua-language source-code embedded within the EPICS channel-name’s postfix. We will discuss the generalized utility of this approach across a wide range of data acquisition applications, projects, and platforms; the performance and robustness of our production implementation; and our operational experience with the software at LANSCE.
       </abstract>
    </record>
  </records>
</xml>
