Analytic Scene ================== Looking uptree from lvPmtHemi see many nodes without geometry and just physvol/logvol striping, does this need a separate "placement" tree ? Prepping for OptiX/OpenGL instancing ? * TODO: expand ddbase.py to handle this Checking users of lvPmtHemi AdPmts/geometry.xml uses paramphysvol to instance it around the rings etc..:: simon:pmt blyth$ pmt-dfind lvPmtHemi ./AdPmts/geometry.xml: simon:DDDB blyth$ pmt-dfind lvPmtHemiwPmtHolder ./AdPmts/geometry.xml: ./PMT/geometry.xml: ./PMT/hemi-pmt.xml: simon:DDDB blyth$ AdPmts/geometry.xml:: 33 34 35 36 37 38 39 40 41 42 43 44 45 46 Detdesc generation -------------------- Detdesc generation complicates things greatly... Take a look at GDML /usr/local/env/dyb/NuWa-trunk/dybgaudi/Detector/XmlDetDesc/python/XmlDetDescGen Multi File Detdesc Parsing with ddbase.py ? ----------------------------------------------- * https://wiki.bnl.gov/dayabay/index.php?title=Tutorial:DetDesc/XML_Files Detdesc using catalog to handle cross-file ? Always ? :: simon:PMT blyth$ pmt-dfind hemi-pmt.xml ./PMT/geometry.xml: ./PMT/geometry.xml: ./PMT/geometry.xml: ./PMT/geometry.xml: ... 06 7 8 9 10 11 12 13 14 15 16