Documents

 

THE HFT SOFTWARE DOCUMENTATION AREA
  • Older DOC pages (but with many goodies) are HERE
  •  
  • The Pixel detector maintains its own documentation area HERE

 

Older documentation pages

Data Sets/Chain Options/Geometry Tags


  1. The data sets used for the CD0 proposal in the Spring of 2007 are in the production pages: www.star.bnl.gov/public/comp/prod/TrackingUpgrade.html
  2. The BFC options used for that production are also there:  www.star.bnl.gov/devcgi/dbProdOptionRetrv.pl
  3. The production log files are gzipped in the prodlog area, eg.  /star/rcf/prodlog/P07ia/log/trs/rcf1298*.log.gz
  4. Geometry tags and explanation (sort of) are here: drupal.star.bnl.gov/STAR/comp/simu/r-d-geometry-tags/

CD0 -> CD1 Software TASK LIST

 

 There are two important areas that fall under our responsibility:

1) Physics analysis code/performance simulations

   The committe (see also the attached .doc file) asked for more detailed simulation of

   a) D0s : flow and RAA performance with realistic systematic errors

   b) B-meson capabilites quantified (see Question-3/4 related attached docs)

       * reconstruction channels, methods, rates

       * triggering

       - To begin look at the attached ppt file on B-meson work done for the SVT and some thoughts in attached Question_3.ppt file

       - The Yale group is willing to help someone start on this. Gang Wang (UCLA) and also Quan Wang (Purdue) have volunteered to work on this.

   c) L_c capabilities also quantified since these are unique to STAR

       - Jan Kapitan is currently refining his analysis using the CD0/UPGR13 production

       - YiFei is also interested (also in using TOF+HFT)

 

2) Infrastructure/Development

   a) Geometry. We need to move on and build/use a new geometry for our simulations. This impacts the Simulators and the tracking optimization. Gerrit initialized already the discussion with Andrew but expert help is critical.

  b) Tracking. We need to reconcile hand/Geant numbers, aka debug/optimize Sti performance. BNL core group involvemen  is a must here. We need to clean our code from fuzzy factors etc. Simplification of geometry for this particular study might be a good idea. Work on this item is reported in Tracking Efficiency Investigations

  c) Simulators. Xin Li (Purdue) showed interest in this task. He will present an outline of a plan soon.

  d) Calibration/Alignment procedures. Spiros to visit LBL to gather info from survey people.

  e) Web interface uplift. Willie will help with initial effort. Some templates were posted (see minutes of 3/21/08) HFT software meeting

 

This is an non prioritized list. We need to agree on an action plan with a timeline since the time for a new production for CD1 is near (before summer).

 

CDR-Software

Drafts for Software Chapters in HFT-CDR

 

Fast/Slow Simulators

  1. Nov. 2007: Willie made some updates to StPixelFastSim and his documentation is HERE
  2. TBD

Full GEANT/MC simulations

 

  1. Yifei's production page: http://www.star.bnl.gov/protected/lfspectra/yfzhang/hft/HFTproduction.htm
  2. My 10/12/2007 presentation on DCA resolution is at You do not have access to view this node
  3. Willies single track efficiency study (Nov/2007) is at Single-particle results

Hand Calculations by J. Thomas

The area where most recent talks/results/ were presented is at
rnc.lbl.gov/~jhthomas/public/HFT/

The code is on rcf in:

~jhthomas/STAR/hft/DetectorDesignV5.C (good on 10/1/2007)
It compiles in root with
>.x DetectorDesignV5.C++

The macro is sort of self-documented.

 

Hand Calculations-Formulas by H.Wieman/Gene VB/Victor P./


WARNING:
Many pages in Howard's area can only be viewed by IE or Safari browsers.
I have attached pdf files  of these pages at the bottom.


The point to begin about the derivation of 'Probability of finding the correct hit' is here:
www-rnc.lbl.gov/~wieman/HitFinding2DXsq.htm
Once you are there you can follow (backwards) the whole history through the embedded links.

The 'Hit association formula' is then compared with MC (MathCAD) and agreement is achieved here:
www-rnc.lbl.gov/~wieman/HitFindingStrip2DMC2Gory.htm

The specific area where 'strips' or 'pads' are handled (some warnings are posted there too):
www-rnc.lbl.gov/~wieman/HitFindingPadVsStrip.htm

Part of the warnings is discussed in this page by Gene:
www.star.bnl.gov/~genevb/IST_Study/Corrections.html


A summary of HW work on this in a presentation form is here:
www-rnc.lbl.gov/~wieman/HitAssociationMar2007Wieman.ppt

Gene's work was presented in March 2007 in a talk:
www.star.bnl.gov/~genevb/IST_Study/IST_HitMatching_03_2007.html

How-to pages

Code developers need to keep in mind that:

1) Need to follow STAR code standards
2) Need to supply some documentationTutorial [example]
3)
 Packages need to be peer reviewed

Below are attached some older 'HOW TO' documents.......

Patch Pixel prototype


The initial study for a Pixel prototype (patch) was done in MathCAD by Howard Wieman.
The goal was set to measure D cross section (flow and high-pt suppression seemed unrealistic for a
short run/life-time device). To that end one aims to catch the mean-pt region, ie around 1 GeV in pt.

The study is here:
www-rnc.lbl.gov/~wieman/D_efficiency.htm which was updated, for comparison to GEANT purposes, to this: www-rnc.lbl.gov/~wieman/D_efficiency_2.htm and later updated to this:
www-rnc.lbl.gov/~wieman/D_efficiency_3.htm
WARNING
:
These pages require IE or Safari to be viewed and played properly.
A pdf version is also attached (no .avi movies though) for universal viewing.

A GEANT simulation with some less ideal situation can be found here:
www.star.bnl.gov/protected/strange/margetis/hft/patch3.pdf


Pile-Up Studies


This page is for documentation of pile-up work. Pile-Up refers to
  1. Non-triggered events which occur during the Pixel readout
    1. Au+Au or p+p
    2. UPC background (mostly electrons)
  2. General beam background due to Pixel proximity to the beam
Initial hand estimates (9/2007) by Jim Thomas are encouraging and they can be found in the file below named 'SimulationRequest'.

Tracking Efficiency Investigations

 

  • A simplified geometry was used for these tests. It is tagged as UPG15. Some GEANT snapshots are attached at the bottom.
  • Resolution ....

 

documentation for analysis of simulated (McEvent) data


Jan's pages are
HERE