Proposal for getting the geometry from the SVT conditions database:

• On the Reconstruction side, all transient classes are contained in SvtGeom, and all persistent classes and proxies, in SvtGeomP. Similarly, all simulation persistent classes and proxies are contained in SvtSimGeomP, while the transients are in SvtSimGeom.



• Both reco and simulation persistent classes are stored in the same SVT conditions database. Since both types of the transient classes are completely independent of each other (only simulation transients are allowed to depend on the reco non-persistent classes), and since all handling is done via proxies, storing simulation persistent classes in the same database will have no effect on the reconstruction.



• Up to now, the loading of the SVT conditions database has been done by dedicated modules in SvtEnv. It has been announced at the last SVT reco software meeting that a new package (provisionally called SvtCondModules on my diagram) is being created specifically for this purpose. It has also been agreed that modules responsible for loading the simulation persistent classes into the database can be stored in this package. Since they will be ordinary framework modules, the user will always have the option of not loading the simulation classes (for example, by turning them off in the corresponding tcl script).



• I have tried implementing this design to the extent that's possible with the current state of the software. As far as I can tell, it does not impede the reco performance, and achieves all goals that are necessary for simulation.