[Halld-tagger] End user polarization

[Richard Jones]

Mike [trying again, with spelling fixed],

Would the value returned have discontinuities at the 100 MeV bin
boundaries, or be parameterized according to some peak/edge model? This is
particularly important at the location of the edge, where the polarization
is very energy dependent and possibly run dependent because of that.

-Richard J.

On Mon, Jun 5, 2017 at 2:33 PM, Richard Jones <richard.t.jones at uconn.edu>
wrote:

> Mike,
>
> Would the value returned have discontinuities at the 100 MeV bin
> boundaries, or be parameterized according to some peak/edge model? This is
> particular important that the location of the edge, where the polarization
> is very energy dependent and possibly run dependent because of that.
>
> -Richard J.
>
> On Mon, Jun 5, 2017 at 1:35 PM, <dugger at jlab.org> wrote:
>
>> Hi,
>>
>> I was thinking about event-by-event polarizations.
>>
>> While TPOL can not give an event-by-event polarization, we could provide
>> some sort of subroutine that gives the average run polarization on an
>> event-by-event basis. The subroutine would take as arguments the run
>> number and photon energy for an event, with the return value being the
>> polarization (based off a polarization binning of 100 MeV).
>>
>> Does this sound like the sort of thing that is desired?
>>
>> My plan is to go ahead with making the code that gives the polarization
>> for a set of runs (provided by the end user), and then have our grad
>> student (Sebastian Cole) create the final code that takes into account the
>> feedback we get from our fellow GlueX collaborators.
>>
>> Take care,
>> Michael
>>
>> _______________________________________________
>> Halld-tagger mailing list
>> Halld-tagger at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/halld-tagger
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld-tagger/attachments/20170605/82593607/attachment.html>