GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » Fairroot » General Discussion » Geometry input in ROOT (TGeo) format
Geometry input in ROOT (TGeo) format [message #13488] Wed, 16 May 2012 14:56 Go to previous message
Volker Friese is currently offline  Volker Friese
Messages: 365
Registered: April 2004
Location: GSI CBM
first-grade participant
From: *

we (CBM) would like eventually to step away from the ASCII geometry format and use ROOT files instead. The main motivations are that the creation of the geometry file seems easier when using TGeo, and that the geometry of a certain subdetector can be viewed and browsed with the ROOT TBrowser standalone, i.e. without invoking the FAIRROOT framework.

Now the documentation of FAIRROOT says that


Detector geometry in FairRoot can be defined via:

ASCII files (Hades Geometry interface)
Root files (TGeoManager Object in ROOT file)

However, I was told by Florian that instead of saving the TGeoManager object to the file, one should save the top volume, which must be of type TGeoVolumeAssembly. If that were true, it will have certain drawbacks:

  1. The top volume of type TGeoVolumeAssembly is not browsable (the geometry is not expanded). Of course, this can be helped by saving both objects, the top volume and the full TGeoManager to the geometry file.
  2. All media defined when creating the geometry file will be ignored by the framework, which will use at runtime those defined in the media.geo file.

Is it possible for the framework to read the TGeoManager instead of the top volume, and add all media defined there to those already defined from media.geo (checking, of course, for double occurences)?

Best regards,


Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Questions on HIts in detector and MCPoint
Next Topic: step length for VMC
Goto Forum:

Current Time: Sat Jun 22 11:33:45 CEST 2024

Total time taken to generate the page: 0.00945 seconds