Log of /PamVMC/Makefile
Parent Directory
| Revision Log
Revision
1.5 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Fri Jun 12 18:38:51 2009 UTC
(15 years, 5 months ago)
by
pam-rm2
Branch:
MAIN
CVS Tags:
HEAD,
v1r0
Changes since
1.4: +4 -3 lines
Diff to
previous 1.4
,
to
selected 1.3
- Introduced user-defined names of output files and random seeds number.
Users can do it use options of PamVMCApplication constructor:
PamVMCApplication(const char* name, const char *title, const char*
filename="pamtest", Int_t seed=0).
The Random object that I use is TRandom3 object which has astronomical
large period (in case of default initialization 0). All random generators
in the code use this object by calling of gRandom singleton which keeps
it.
- Corrected TOF digitization routine. No problems with TDC hits due to
hadronic interactions anymore.
- Some small changes was done to compile code under Root 5.23. +
geant4_vmc v. 2.6 without any warnings
- Some classes of PamG4RunConfiguartion was changed for geant4_vmc v.
2.6.Some obsolete classes was deleted as soon as developers implemented
regions.
- Navigation was changed from "geomRootToGeant4" to "geomRoot", because on
VMC web page written that as soon as Geant4 has no option ONLY/MANY
translation of overlapped geometry to Geant4 through VGM could be wrong.
I'd like to stay with Root navigation:
http://root.cern.ch/root/vmc/Geant4VMC.html. This should be default
option.
- New Tracker digitization routine written by Sergio was implemented
- PamVMC again became compatible with geant4_vmc v.2.5 and ROOT 5.20.
The problem was that ROOT developers introduced in TVirtualMC class a new
method SetMagField and new base class:TVirtualMagField from which
user-defined classes shoukd be derived
Revision
1.3 -
(
view)
(
download)
(
annotate)
-
[selected]
Thu Feb 19 17:39:48 2009 UTC
(15 years, 9 months ago)
by
nikolas
Branch:
MAIN
Changes since
1.2: +9 -11 lines
Diff to
previous 1.2
Cleaning up before releasing
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
select a symbolic revision name using the selection box, or choose
'Use Text Field' and enter a numeric revision.