STARSIM How-To

HOW-TO: create new detector

mkdir new_detector; cd new_detector, ALL further actions to be done in the this directory!
  1. To create new geometry description : cvs co pams/geometry
  2. cvs co StRoot/StTrsMaker - geant tables also reside here, so it needs to be recompiled also
  3. cd pams/geometry; mkdir crdegeo; cd crdgeo;
  4. touch crdegeo.g follow the examples here
  1. To integrate into STAR framework : cvs co pams/sim
  2. pams/sim/g2t/g2t_crd.F, not exists, create
  3. pams/sim/g2t/g2t_crd.idl, not exists, create
  4. pams/sim/idl/g2t_crd_hit.idl, not exists, create
  5. pams/sim/idl/g2t_track.idl - exists, add lines for crd
  6. pams/sim/g2t/g2t_volume_id.g - exists, add lines for crd
  7. Do cons (probably twice), top level directory where pams/.. is located
  1. To add hits into .geant.root : cvs co StRoot/St_geant_Maker
  2. add your hit code to StRoot/St_geant_Maker.cxx
  3. cons from top level directory where StRoot/.. is located

HOW-TO: BFC new detector

root4star -b -q bfc.C\(1,5,\"fzin,y2004,C3default,-NoHits,-emcY2,-PreVtx,trs,srs,fss,big,GeantOut\",\"mygamma.fzd\"\);

HOW-TO: Hijing + Geant + BFC

  1. Hijing : hijjet.x hijev.inp => evgen.1.nt
  2. Geant : starsim -w 0; exec hijing.kumac => myhijing.fzd
  3. STAR :root4star -b -q bfc.C(...,"myhijing.fzd") => event.root, geant.root
  4. WARNING: STI is the recommended tracker for Y2007+, so consider to change BFC option

HOW-TO: ...