rerun PXL code with upgr15 (SL08f) : quick QA

1) input : 1k events,  20pions/event 
detp geometry upgr15
make geometry
make gstar
gclose all
debug on
gfile o 20pions_1kev.fz
user/vxyz 0.0001 0.0001 0.01
user/vsig 0.01 5.
gkine 20 8 0.1 5.0 -1.2 1.2 0 6.28 
trig 1000
2) BFC chain : some checks
a) bfc chain used :
root4star -b -q 'bfc.C(1,1,"DbV20090305,trs,upgr15,ssdfast,pixFastSim,Idst,IAna,l0,tpcI,fcf,Tree,logger,ITTF,  Sti,StiRnd,PixelIT,IstIT,StiPulls,VFMCE,NoSvtIt,SsdIt,MakeEvent,McEvent,geant,evout,IdTruth,tags,bbcSim,emcY2,  EEfs,big,-dstout,fzin,McEvOut,clearmem,MiniMcMk,McAna,"20pions_1kev.fz")>log_cdr'
b) hit errors



✓ Running this BFC chain takes the tables we have defined for upgr15 : pixelHit errors and istHitErrors

c) tpc RDO masks



✓ same for the TPC rdo masks table : this table was the table we have defined for upgr15
(recall :it was based on Jan Kapitan's suggestion to make a copy of tpcRdoMasks.dev2005.C where all sectors were OK)

3) DCA (MuDst) : some checks
cuts used :
global tracks
TPC : nFit/nPoss > .52
|eta|<1.0
globalDca < 3cm 
|dcaXY|<1cm
error on dcaXY < 1cm
Pt >0.1
ssdHit =1 && istHit=1 && pixHit =2

phi vs. eta

dcaXY vs. Pt

pointing Resolution in XY (using FitSlicesY of previous plot) vs. Pt


number of hits used in tracking for SSD, IST nad PXL