Difference between revisions of "Why Separate HDDS?"
From GlueXWiki
(first draft) |
(add link to hdds directory listing) |
||
Line 1: | Line 1: | ||
Proposal: move HDDS code and related geometry definition files out of the src tree. | Proposal: move HDDS code and related geometry definition files out of the src tree. | ||
− | =Motivation= | + | =Original Motivation= |
* make the builds easier | * make the builds easier | ||
Line 19: | Line 19: | ||
* Makes it obvious where the geometry is controlled | * Makes it obvious where the geometry is controlled | ||
− | * XML and programs are now kept in same directory, they should be separated | + | * XML and programs are now [http://clasweb.jlab.org/websvn/prod/listing.php?repname=GlueX&path=%2Ftrunk%2Fsrc%2Fprograms%2FSimulation%2Fhdds%2F#_trunk_src_programs_Simulation_hdds_ kept in same directory], they should be separated |
* Geometry may be needed in other contexts: separation shows logical relationship | * Geometry may be needed in other contexts: separation shows logical relationship | ||
* Geometry changes are uncoupled from tagged releases of reconstruction | * Geometry changes are uncoupled from tagged releases of reconstruction |
Latest revision as of 08:49, 21 October 2009
Proposal: move HDDS code and related geometry definition files out of the src tree.
Original Motivation
- make the builds easier
- make must
- go into src/programs/Simulation/hdds first
- build some tools
- copy files back to src/libraries/HDGEOMETRY
install: hdds-geant hdds-root hdds-mcfast hdds-root_h hddsGeant3.F hddsroot.h mkdir -p $(HALLD_HOME)/bin/$(BMS_OSNAME) cp $^ $(HALLD_HOME)/bin/$(BMS_OSNAME) if [ -e ../HDGeant ] ; then cp hddsGeant3.F ../HDGeant/hddsGeant3.F ; fi if [ -e ../../../libraries/HDGEOMETRY ] ; then cp hddsroot.h ../../../libraries/HDGEOMETRY/hddsroot.h ; fi
Other Reasons for Separation
- Makes it obvious where the geometry is controlled
- XML and programs are now kept in same directory, they should be separated
- Geometry may be needed in other contexts: separation shows logical relationship
- Geometry changes are uncoupled from tagged releases of reconstruction
- Allows development of a separate geometry management scheme
Disadvanges of Separation
- Creates another package to check out
- Creates the need for a separate geometry management scheme