<div dir="ltr">Sascha,<div><br></div><div>Finding the coh peak position requires considerable analysis, and polarization fraction even more. Are you sure you want to do this in EPICS? This sounds more like an online monitoring job, writing to a database.</div>
<div><br></div><div>-Richard J.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 25, 2014 at 9:40 AM, Alexander Somov <span dir="ltr"><<a href="mailto:somov@jlab.org" target="_blank">somov@jlab.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi,<br>
<br>
>From the Pair Spectrometer we'll record:<br>
- PS coincidence rate for specific energy bin (lumi monitor)<br>
- coh peak position<br>
- polarization fraction<br>
<br>
Note, PS has a special trigger type, there will be a lot<br>
of information available during data reprocessing.<br>
<br>
Cheers,<br>
Sasha<br>
<div><div class="h5"><br>
<br>
On Tue, 24 Jun 2014, Richard Jones wrote:<br>
<br>
> Hello David,<br>
><br>
> For the microscope, I would like to have a set of key voltage levels and<br>
> temperatures in the frontend recorded in the event stream.<br>
><br>
> -Richard J.<br>
><br>
><br>
> On Tue, Jun 24, 2014 at 7:52 AM, David Lawrence <<a href="mailto:davidl@jlab.org">davidl@jlab.org</a>> wrote:<br>
><br>
>> Hi All,<br>
>><br>
>> One of the features that will be implemented in the online is the ability<br>
>> to insert non-CODA events into the data stream. This would mainly include<br>
>> EPICS variables that might be useful in the offline analysis where the full<br>
>> EPICS archive is not readily available. For example, the electron beam<br>
>> current or a temperature in the hall. What is needed is a list of the EPICS<br>
>> variables that might have value in the offline and the frequency by which<br>
>> to read and insert them. Realistically, variables cannot be inserted more<br>
>> often than once every 2 seconds. I assume many of these though will not be<br>
>> written more than once per minute. If you know of good candidates of<br>
>> non-CODA data that should be inserted into the data stream, please send<br>
>> them to me along with a suggested insertion frequency. I will compile them<br>
>> into a configuration file that will also serve as the official list.<br>
>><br>
>> Regards,<br>
>> -David<br>
>> _______________________________________________<br>
>> GlueX-Collaboration mailing list<br>
>> <a href="mailto:GlueX-Collaboration@jlab.org">GlueX-Collaboration@jlab.org</a><br>
>> <a href="https://mailman.jlab.org/mailman/listinfo/gluex-collaboration" target="_blank">https://mailman.jlab.org/mailman/listinfo/gluex-collaboration</a><br>
>><br>
><br>
</div></div>_______________________________________________<br>
Halld-tagger mailing list<br>
<a href="mailto:Halld-tagger@jlab.org">Halld-tagger@jlab.org</a><br>
<a href="https://mailman.jlab.org/mailman/listinfo/halld-tagger" target="_blank">https://mailman.jlab.org/mailman/listinfo/halld-tagger</a><br>
</blockquote></div><br></div>