[Halld-tagger] [EXTERNAL] Re: DBeamPhoton tests

[Alexander Austregesilo]

Thank you Sean. I merged the master into both branches before running 
the test in order to avoid that unrelated changes to the code base 
affect the results.

On 4/14/2020 5:23 PM, Sean Dobbs wrote:
> Hi all,
>
> Just to clarify, I don't believe sdobbs_beamphoton_mod was ever merged
> with the master branch.  The difference between this branch and
> Richard's is [for the sake of testing], my branch required a TDC/ADC
> match for both TAGH and TAGM hits, but did not touch the TAGM software
> thresholds, while Richard's branch required a TDC/ADC match for TAGM
> and removed the software thresholds, and didn't touch the TAGH.
>
> Cheers,
> Sean
>
> On Tue, Apr 14, 2020 at 2:33 PM Alexander Austregesilo
> <aaustreg at jlab.org> wrote:
>> Dear beamline group,
>>
>> I produced 3 runs from the current data taking period with three
>> different versions of the beam photon factory:
>>
>> runs:
>> 71463: 150nA
>> 71469: 250nA
>> 71724: 350nA
>>
>> versions:
>> ver09: master (April 7th)
>> ver10: sdobbs_beamphoton_mod (merged with master April 7th)
>> ver11: tagm_fixes_for_2020_rtj (merged with master April 7th)
>>
>>   From a first look at the monitoring plots (easiest with version browser
>> https://urldefense.com/v3/__https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/versionBrowser.py__;!!PhOWcWs!n_n_6j968NmGfZQFB8ws4G0xbZf2SB2KgvQ3uarvNDfckSYCSla5zIoD-21f4Q$ ),
>> I see almost no difference for the 350nA run:
>>
>> version | rho yield | DBeamPhotons
>> ver09  |  5.08    |  67.7
>> ver10  |  4.96    |  65.2
>> ver11  |  5.03    |  67.6
>>
>> For the other 2 runs, I see a significant decrease in the number of beam
>> photons from Sean's branch (~20%), while the decrease is smaller for
>> Richard's. Both branches show a loss of about 10% in rho yields.
>>
>> All merged histogram files can be found here:
>>
>> /cache/halld/offline_monitoring/RunPeriod-2019-11/ver{09,10,11}/hists/hists_merged
>>
>> Please have a look for yourself. I hope somebody can summarize this
>> study during the production and analysis meeting tomorrow.
>>
>> Cheers,
>>
>> Alex
>>
>>