CuCu reproduction

 CuCu data (from run 5) has been reprocessed by including in the MuDst files the covariance matrix information.

These parameters are needed to properly evaluate the StDcaGeometry, therefore the DCA in transverse and Z direction.

Web page with trigger information :

Trigger Id Type Offline vertex cut Trigger setup
66007 Min Bias (cu-zdc-narrow) |vz|<30 cm cuProductionHighTower, cuProductionMinBias
66203 Barrel High Tower (cu-bemc-ht18) |vz|<30 cm cuProductionHighTower
 

details: here 

centrality selection is 139, 98, 67, 46, 30, 19 (0-10,10-20,20-30,30-40,40-50,50-60)

details: here

Svt rdo boards for run 5 : plot here 

Mail from Lidia with the data locations :

 

cucu 200GeV & 62GeV run 2005 MuDst reproduction with an error matrix
  saved in MuDst requested in:
  http://www.star.bnl.gov/HyperNews-star/get/starprod/379.html
  is completed.
  Produced MuDst files are located in the disks
  /star/data86, data88, data89 on the path:
  /star/data8X/reco/cuProductionMinBias/*/P07ic/2005/*
  /star/data8X/reco/cu62productionMinBias/*/P07ic/2005/*

Additional info :
CuCu@200GeV goes from  :
        1. day 13 to day 46 : RFF (which is 13th, january to 15th, February)
        2. day 47 to day 65 : FF (which is 16th, february to 6th, March)
  1. QA work

                      primary vertex resolution X vs gRefMult (gRefMult is the definition from run 7, may be not adequate here) :here

                      number of vertices per event : here

     2.  QA work done 

  • vertex : the Zvertex distribution day-by-day is here
  • summary : <Vz> and ResolutionVz vs, run number : here
  • tracks.

I've run over files from 

 

/star/data86/reco/cuProductionMinBias/*/P07ic/2005/*

 

 with the zvertex selection |Vz|<30 cm and the correct trigger id.

The primary tracks selection is :

  • pT > .1 GeV/c
  • ratio (TPC fit)/(TPC poss) > .51
  • |eta|<1.2
  • |DCA global|<3cm
  • when I did a selection on the particle, it is done by requiring |ndEdx|<2 (ex dca plots for pions candidates are done with a cut |ndEdx_pi|<2

Results : dcaXY resolution at P=1GeV/c vs run number 

We see that there are some days w/o SVT and/or SSD data : these days are coherent with the entry of the run log browser

However, the dcaXY is pretty stable (compared to run 7) with a similar level

The details day-by day are here :

  1. all tracks
  2. pions candidates
  3. kaons candidates

Results : distribution of silicon hits (#SSD hit vs #SVT hits) : here 

This pdf file shows, day-by-day :

  1. plot left 2d plots with Y-axis = number of SSD hit ; X-axis = number of SVT hits
  2. plot middle : SSD hit distribution
  3. plot right : SVT hits distribution

     3. QA for CuCu@62GeV

The summary plot shows, for each run, if there is 0 or 1 (0,1,2 or 3) tracks with SSD (SVT)

So basically, we're looking for runs with SSD=1 (blue filed circles) and SVT>1 (red circles)

10/25 : UPDATE : final cuts

 

static const Double_t pTCut          = 0.5;  // transverse momentum cut

static const Double_t PCut           = 1.5;  // momentum cut

static const Double_t sumPCut        = 1.5 ; // sum of momentum(kaon)+momentum(pion)

static const Double_t mKpiMin        = 1.2;  // min mass of (Kpi) association 

static const Double_t mKpiMax        = 2.2;  // max mass of (Kpi) association 

static const Double_t DcaCut         = 0.2;  // single track DCA to PV

static const Int_t    TpcCut         = 25;   // TPC hits fitted

static const Float_t  TpcRatioCut    = 0.51; // TPC hits fitted / TPC hits Poss

static const Double_t TrackLengthCut = 40;   // min value for dEdxTrackLength 

static const Int_t    SiCut          = 2;    // (SVT+SSD) hits fitted

static const Int_t    SvtCut         = 3;    // (SVT) hits fitted

static const Int_t    SsdCut         = 1;    // (SSD) hits fitted

static const Float_t  RadiusCutSvt1  = 9.0;

static const Float_t  RadiusCutSvt2  = 13.0;

static const Float_t  SigmaPionCut   = 2.5;    // nsigma for pion

static const Float_t  SigmaKaonCut   = 2.5;    // nsigma for kaon

static const Float_t  SigmaProtonCut = 2.5;    // nsigma for Proton

static const Double_t EtaCut         = 1.2;   // track pseudorapidity

static const Double_t zcut           = 15;    // zvertex cut

static const Double_t PrimZResCut    = 0.008; // zvertex resolution cut

static const Double_t cosThetaCut    = 1;

static const Double_t rapCandCut     = 1.0;

static const Double_t slengthCut     =.2;     // max value of decaylength calculated by TCFIT

static const Double_t dslengthCut    =.2;     // max value of the error associated to the decaylength from TCFIT

static const Double_t ProbCut        =.01;    // min value of probability of FIT

static const Int_t    writeHisto     = 1;     // flag to write histos