[Eg6_analysis] gpp

[Nathan Baltzell]

I linked e1dvcs's constants from run #1 for the entire GPP system 
to eg6's run index for runs 1-10.   I chose e1dvcs since they seemed
to have some more modern constants and also have something for
the IC.  The DC_WIRE subsystem needs to be updated for eg6.

Mohammad, this should solve your most recent issue with gpp ...

-Nathan




info: in calib_user.RunIndexeg6, runs 1-10 for GPP, DC, Reg1 now are linked with constant set ID 125, runIndexId is 435987
warning: no constants found linked to run 1 for system GPP, subsystem DC, item Reg1_mean in calib_user.RunIndexe1dvcs
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, DC, Reg2 now are linked with constant set ID 121, runIndexId is 435988
warning: no constants found linked to run 1 for system GPP, subsystem DC, item Reg2_mean in calib_user.RunIndexe1dvcs
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, DC, Reg3 now are linked with constant set ID 121, runIndexId is 435989
warning: no constants found linked to run 1 for system GPP, subsystem DC, item Reg3_mean in calib_user.RunIndexe1dvcs
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, DC_WIRE, sector1 now are linked with constant set ID 8, runIndexId is 435990
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, DC_WIRE, sector2 now are linked with constant set ID 5, runIndexId is 435991
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, DC_WIRE, sector3 now are linked with constant set ID 5, runIndexId is 435992
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, DC_WIRE, sector4 now are linked with constant set ID 5, runIndexId is 435993
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, DC_WIRE, sector5 now are linked with constant set ID 5, runIndexId is 435994
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, DC_WIRE, sector6 now are linked with constant set ID 5, runIndexId is 435995
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, IC, ic_a now are linked with constant set ID 4, runIndexId is 435996
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, IC, ic_b now are linked with constant set ID 6, runIndexId is 435997
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, IC, ic_c now are linked with constant set ID 1, runIndexId is 435998
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, IC, noise now are linked with constant set ID 2, runIndexId is 435999
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, IC, noiseRMS now are linked with constant set ID 2, runIndexId is 436000
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, IC, timeRMS now are linked with constant set ID 2, runIndexId is 436001
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, SC, Length now are linked with constant set ID 2, runIndexId is 436002
info: in calib_user.RunIndexeg6, runs 1-10 for GPP, SC, Sigma now are linked with constant set ID 2, runIndexId is 436003
warning: no constants found linked to run 1 for system GPP, subsystem SC, item Sigma57 in calib_user.RunIndexe1dvcs
warning: no constants found linked to run 1 for system GPP, subsystem tagr, item offset in calib_user.RunIndexe1dvcs
warning: no constants found linked to run 1 for system GPP, subsystem tagr, item sigma in calib_user.RunIndexe1dvcs




On Nov 26, 2014, at 11:42 PM, Stepan Stepanyan <stepanya at jlab.org> wrote:

> Hi Nathan,
> 
> Thanks for looking into this. I am not an expert, but I think
> parameters p0/p1/p2 should not depend on run, so you can
> get it from any run group, e.g. e1-6/g10 ...
> 
> Stepan
> On 11/26/14, 8:06 PM, Nathan Baltzell wrote:
>> The reason why Mohammad doesn't see any affect from changing the region 1
>> smearing factor in gpp turns out to be because the database has all zeroes for
>> GPP/DC/Reg1 (and non-zeroes for the other regions).  A number of calib_user
>> tables also have this issue, and also the main calib.RunIndex.
>> 
>> These missing constants are polynomial coefficients used to
>> calculate a sigma with which to smear doca in the DOCA bank:
>> 
>> sigma = p0 + p1*doca + p2*doca ….
>> 
>> Anyone know how to calculate them?
>> Or should we just copy them from another rungroup?
>> 
>> -Nathan
>> _______________________________________________
>> Eg6_analysis mailing list
>> Eg6_analysis at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/eg6_analysis
> 
> _______________________________________________
> Eg6_analysis mailing list
> Eg6_analysis at jlab.org
> https://mailman.jlab.org/mailman/listinfo/eg6_analysis