1. 2009-08-1Gene, S&C meeting TPC residuals with Run 8 data , in particular slides 6,7... show pp 500 from 2009
  2. Rosi computed beam line constrain for pp500 data in run 2009

    BFC options to print tracks needed for the beam line code 
     root4star -b -q bfc.C'(1,10,"B2009.2,VtxSeedCalG,emcDY2,ITTF,VFPPVnoCTB,BEmcChkStat,beamLine,Corr4,OSpaceZ2,OGridLeak3D -dstout -evout " ,"/star/data03/daq/2009/Weve/sampler100X/st_W_10079002_raw_4180001.daq")' > & LogB
  3. Tonko: document describing my procedure on how to tune the ALTRO tail suppression.
    Local copy:
  4. Gene: slewing in the Run 9 TPC , i.e. dependence of ]cluster time determination on cluster charge, day ~180, low lumi pp2pp
  5. Gene uploaded Field cage shorts in the DB, September 22, 8 pm, tpc-hn
  6. TPC "prompt" hits and reality check - long list of tasks to make use of them
    Subject: Re: TPC "prompt" hits and reality check
    Date: September 30, 2009 2:32:04 PM EDT
    To: phana-hn@orion.star.bnl.gov
  7. Carl explains:
    • I believe these prompt hits have the potential to be very useful in
      separating real tracks that punch out the ends of the TPC from
      pile-up tracks. As such, they could be quite useful for vertex finding.
    • In contrast, you are asking about "really short tracks". The
      matching efficiency for those is going to be quite low. Only ~20% of
      the inner sector pad plane area is active. Particles that punch out
      through the other ~80% of the MWPC area will leave "invisibly".
  8. on the topic of charge sign discrimination
    If we want charge sign to be good up to 50 GeV, then we need to keep primary track sagitta errors below 1.2 mm. This will have two additive components: systematic error in the sagitta (e.g. the TPC alignment is pervasively slightly wrong or the SpaceCharge correction is always slightly low) plus resolution of the sagitta (e.g. variance in alignment from sector-to-sector or in the SpaceCharge correction event-to-event, combined with the intrinsic resolution of the detector). If we want something like 95% confidence, then we should plan on being within 2 sigma. So:

sagitta systematic error + 2 * sagitta resolution < 1.2mm

In the past, we've obtained a resolution of about 250 microns on the sagitta of primary tracks. If we can achieve 400 micron resolution, then we need to get the systematic errors below 400 microns.

Thanks,-Gene

TpcRS - new slow simu for TPX

Jan:I make observation TpcRS crashes on M-C events generated with geometry 2008. Although real TPX electronic was installed in year 2009 people have many old (expensive to produce) simulations which they may want to still use to estimate performance in the future years.
Would be the best if TpcRS is able to process old .fzd fils and has settings appropriate to different ASIC setup.

Yuri: ASIC means old TPC electronics. ALTRO is new (TPX) electronics.
These are two completely different approaches (analog and digital fitering).
The main goal for TpcRS is TPX. There are a lot of DB parameters which are associated with y2009 time stamps.
When you run TpcRS for y2008 it uses 23 TPC + 1TPX configuration. TPC has not been tuned enough.
If you like to do this then I give you complete set of instructions for that.

SC & GL calibration progress

Yuri improved TpcRS so embedding is possible slides

Helen studied PT resolution of TPC using W electrons : [ Helen study | http://rnc.lbl.gov/wiki/index.php/High_pt_tracks_from_the_W_analysis]

Improvement in tracking 'CA'-seed finder, presented at S&C on August 25, 2010 by Maksym Zyzak

  • No labels