1 / 12

Test of TCFIT in reco. code (update )

Test of TCFIT in reco. code (update ). Test on pure D 0 (  ) Test on embedding : D 0 mixed with HIJING events Test with Real data. Estimation of D 0 cross-section.

meryl
Download Presentation

Test of TCFIT in reco. code (update )

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Test of TCFIT in reco. code(update ) Test on pure D0 () Test on embedding : D0 mixed with HIJING events Test with Real data

  2. Estimation of D0 cross-section • Rerun over files with loosening a bit some cuts (#tracks<700, |nK|<3, |nπ|<3, remove the cut on slength (linear) and put a cut on prob(TCFIT)>0.01 • Make inv. Mass plots for different pT bins • Estimate the number of counts (=entries per bins in the interesting range)(with BRTW macro) after background substraction • Make d2N/pTdpTdy plot (normalized by 1/Nevents*2π ), rapidity of D0 |y|<0.5

  3. Inv. Mass vs pT (no cut on #tracks)

  4. Inv. Mass vs pT (#tracks<200)

  5. comments • For both cases (no cut and cut on the number of tracks), a clear peak appears for high pT D0 • I have checked that the pT range of the hijing background and the D0 are the same : No possibility that for a given pT, there is only D0 • For #tracks<200, there is quasi no background is flat for pT>3 GeV/C • since a clear peak is needed for the estimation of counts, I use the #tracks cut

  6. Example : 2 <pT≤3 Raw histogram • After using the BRTW.C macro, the bottom histogram (blue curve) is after the background substraction (note the level ~ at 0) • I choose [1.82;1.94] for the mass range : • 114±38 counts in this range (the error is the sum of the bin error in the mass range)

  7. Number of events After |zvertex| cut After #tracks cut  The number of events used is then 5110

  8. This bin gives a very bad inv. Mass So the value and error are not very good spectra • The log plot does not look very nice • I would prefer to make the inv. Mass w/o the cut on #tracks

  9. Back up

  10. details Took macros used in HFT soft. Use y2007g geometry (last updated for AuAu in simu : http://drupal.star.bnl.gov/STAR/comp/prod/MCGeometry Follow these different steps : Produce AuAu MB 200GeV as background Produce 1 D0 per event Mix fz files from background and D0 Run the bfc to do the reco (with slow simulation) Analyze MuDst.root file (ie all reco. tracks) (with same macro used for real data analysis)

  11. AuAu background detp geometry y2007g make geometry make gstar … swit 2 3 vsig 0.01 20.0 gkine -1 0 0 5 -6.3 6.3 0 6.28 -40.0 40.0 gfile o outfile.fz user/input user infile.nt trig 50 • Y2007g geom. • Vertex at 0.01 with  = 20 cm • AuAu collisions in 0<pT<5 • 50 events

  12. D0 production #***************************************************** # Input for gkine set geometry=y2007g set pid=$3 set tracks_per_event=1 set ptlow=0.1 set pthigh=5.0 set ylow=-1.1 set yhigh=1.1 set philow=0.0 set phihigh=6.28 #***************************************************** • This step produces a .fz file with D0’s and used a • vertex file (containing the PV point) for correct mixing

More Related