Difference between revisions of "HOWTO visually inspect the simulation geometry"
From GlueXWiki
| Line 4: | Line 4: | ||
'''Using hdgeant++''' | '''Using hdgeant++''' | ||
* hdgeant++ is based on GEANT3 and uses also paw. So being familiar with kumac is usefull. To check if some modification in an xml file has been done correctly you do the followoing: | * hdgeant++ is based on GEANT3 and uses also paw. So being familiar with kumac is usefull. To check if some modification in an xml file has been done correctly you do the followoing: | ||
| − | 1) generate the geometry fortran file in the hdds directory by "make hddsGeant3.F" | + | 1) generate the geometry fortran file in the hdds directory by "make hddsGeant3.F" |
| − | 2) copy hddsGeant3.F into the HDGeant directory and recompile hdgeant++ by "make clean; make" | + | 2) copy hddsGeant3.F into the HDGeant directory and recompile hdgeant++ by "make clean; make" |
| − | 3) make sure you have "wc.kumac" and "wc.f" in your working directory | + | 3) make sure you have "wc.kumac" and "wc.f" in your working directory |
| − | 4) start "hdgeant++" in your working directory | + | 4) start "hdgeant++" in your working directory |
| − | + | * how to use the wc\#modules in hdgeant++ | |
Revision as of 10:41, 22 July 2008
This page shows how to use geant++ and root to check if the detector geometry has been done right.
Using hdgeant++
- hdgeant++ is based on GEANT3 and uses also paw. So being familiar with kumac is usefull. To check if some modification in an xml file has been done correctly you do the followoing:
1) generate the geometry fortran file in the hdds directory by "make hddsGeant3.F" 2) copy hddsGeant3.F into the HDGeant directory and recompile hdgeant++ by "make clean; make" 3) make sure you have "wc.kumac" and "wc.f" in your working directory 4) start "hdgeant++" in your working directory
* how to use the wc\#modules in hdgeant++
