Seperating advanced and simple models

[laurac8r]

Additional source and header files must be created to allow a clean separation of the advanced and simple models being developed.

This issue can be solved simultaneously with issue #3

[nnaemeka]

Well done. I propose using the G01 example in persistency/GDML example to modify the code so that one can either use the simple geometry built using the native geometry builder or load the more complex gdml integrated modules. But that will be after the item #3.

…

On Sat, Feb 25, 2017 at 10:18 PM, Yaro Kaminskiy ***@***.***> wrote: Additional source and header files must be created to allow a clean separation of the advanced and simple models being developed. This issue can be solved simultaneously with issue #3 <#3> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKQ3auFebHHcv8iwwUuGD3yeX_ivHfq8ks5rgRk4gaJpZM4MMQ2Q> .

-- Nnaemeka Nnamani, Department of Nuclear Engineering, University of California Berkeley. California, USA.

[laurac8r]

Hmmm good point. Definitely something to look into down the line. Like having one call a main GDML file with all the HFNG geometry when calling the executable to run or not running the main GDML file with an executable so as to allow the simple geometry to run. Quite brilliant actually!