[g13] g13b EC Reconstruction

[Paul Mattione]

>From the timestamps on the anahist files in /work/clas/clasg13/pass2/v1/AnaHistFiles/, we cooked g13b from September 30, 2010 to May 14, 2011.  The minutes from the past meeting agendas are not exactly clear on these dates, but they seem reasonable.  About 65% of the files (from anahist timestamps) were cooked prior to when Edwin found the EC problem in January 2011. This date was determined from time stamp on the uploaded image file, and the agenda minutes from January 18, 2011 (note typo in page title, view page history for correct date):

http://clasweb.jlab.org/rungroups/g13/wiki/index.php/Meeting_Agenda%2C_Jan_18%2C_2010

I don't know why I didn't see it earlier, but Cole changed the pedestal constants on January 11, 2011:

http://clasweb.jlab.org/cgi-bin/caldb/cq.pl?button=Run+Ranges&runMin=54042&runMax=55204&system=EC_CALIB&subsystem=EC_PEDESTALS&item=InnerU&run=&itemValueId=&date=&runIndexTable=calib_user.RunIndexg13&hostname=

You can probably guess which runs will be OK and which won't based on the timestamp of the AnaHistFiles, but the best way is to probably histogram the distributions anyway.  

 - Paul

On Mar 21, 2012, at 5:50 PM, Pawel Nadel-Turonski wrote:

> Hi Paul,
> 
> I think Cole tried to fix it and claimed that he had updated the database before the final recooking. I did not check, though. Perhaps you could ask him what he did?
> 
>    Pawel
> 
> On 3/21/2012 5:45 PM, Paul Mattione wrote:
>> There's an issue with the reconstruction of neutrals in Sector 5 of g13b.  This was noticed by Edwin; here's his plot of the neutral reconstruction distribution, circa January 2011:
>> 
>> http://clasweb.jlab.org/rungroups/g13/wiki_secure/index.php/Image:Fig_fiducial_neutrals.gif
>> 
>> Cole Smith determined that there was a problem with the pedestal values for runs after 54084 (basically all of g13b) due to an ADC hardware change for Sector 5.  He said that he updated the calibration constants, but I can't seem to find the updated values in the calibration database.  Anyway, to fix this would require a recook of g13b.  At least it's only for one sector.
>> 
>>  - Paul
>> 
>> 
>> _______________________________________________
>> g13 mailing list
>> g13 at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/g13