[Color_transp] [EXTERNAL] BCM weighted average update

Holly Szumila-Vance hszumila at jlab.org
Fri Jan 17 19:52:22 EST 2020


We’ve been using runs 2424 and 2423 in the Q2=14.3 LH2 kinematics. We can exclude these going forward. 

> On Jan 17, 2020, at 6:10 PM, Dipangkar Dutta <d.dutta at msstate.edu> wrote:
> 
> Hi John,
> Runs 2423 and 2424 are lost causes, just ignore them. Are we using
> these two runs... maybe we should consider dropping them.
> 
> For the rest your stable regions look fine to me.
> 
> The next step win calculating the combined  average current would be
> to do the weighted average.
> For example say region 1 had a counts starting at 0 and ending at 100
> then the uncertainty in counts is 10 and the uncertainty in current is
> curret/sqrt(N) = 0.1*current
> If the region two started from 150 and went 1050 then the count is 900
> and the uncertainty in the current is current*0.033
> 
> You can then calculate the weighted average using the uncertainty in
> the current as the weight ie av = [Sum_i (Current_i/wt_i^2)]/[Sum_i
> 1/wt_i^2]
> 
> Cheers
> Dipangkar
> 
>> On Fri, Jan 17, 2020 at 4:40 PM John Matter <jcm6fv at virginia.edu> wrote:
>> 
>> Hi all,
>> 
>> I just posted a small update to the elog about weighted beam current averages.
>> 
>> https://hallcweb.jlab.org/elogs/Color+Transparency/32
>> 
>> - John
>> _______________________________________________
>> Color_transp mailing list
>> Color_transp at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/color_transp
> _______________________________________________
> Color_transp mailing list
> Color_transp at jlab.org
> https://mailman.jlab.org/mailman/listinfo/color_transp



More information about the Color_transp mailing list