1 / 12

STAR simulations and ROOT

STAR simulations and ROOT. GSTAR root interface. GSTAR. STAR simulation framework since 96 has a hierarchical design to clearly separate user code from G3 implementation details (Rene Brun, PN 1994) has improved memory management elastic ZEBRA

spiro
Download Presentation

STAR simulations and ROOT

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. STAR simulations and ROOT GSTAR root interface

  2. GSTAR • STAR simulation framework since 96 • has a hierarchical design to clearly separate user code from G3 implementation details (Rene Brun, PN 1994) • has improved memory management • elastic ZEBRA • no limits on number of tracks, vertices, hits etc (apart from physical memory limits) • has a built-in database interface

  3. STAR geometry • Formalized description in specification language, including hits and DB access • Many developers, very detail geometry (almost 2,000 different volumes) • Altogether less then 8000 lines including field parameterization , easy to read • No step routine is needed in most of the detectors, no “if statement” problem

  4. GSTAR performance • Fast enough - 30 min/10,000 particles, with a general 1 MeV cuts • Calorimeter cuts tuned with test beam date down to 50 KeV • Interfaced to all event generators • Robust and well debugged production tool

  5. So what do we want more? • We do want more ! • Flexible, expandable access to geometry objects from reconstruction program • Modern visualization and navigation • Access to hits from a C++ code as if they were normal C++ objects • fun, and even more fun • Well, we decided to grow ROOTs

  6. Missing elements • Initially missing elements • Geometry navigator - trivial • Geometry decoder - not so trivial, but feasible • Volumes and positions separately - TVolume • Volumes as position container - TDataset • Hit navigator - trivial • Hit presenter - StGeantHits

  7. G3 geometry model TDataset TVolumePosition StGeant TVolume TVolumeView ctor ctor TNode TVolumeView TShape TVolumePosition list

  8. View as in G3

  9. OpenGL viewer

  10. Geant Hit Access Class class TPoints3DABC (from ROOT G3D) GZEBRA StGeantHits3D StGeantHits() ... GetNextHit(Int_t indx) aghitset() aghitget()

  11. Conclusions • Now we have all this done and working • what do we want more ? • TDataset ? Light named list of TDatasets • TVolume, TVolumeView, TVolumePosition as functional G3 analogs • and fun, even more fun

More Related