Warning, /geant4/CHANGELOG/ReleaseNotes4.1.0.txt is written in an unsupported language. File is not indexed.
0001
0002 Geant4 1.0 Release Notes
0003 ------------------------
0004
0005 7th December 1999
0006
0007 These are the main new features/fixes included in this release (for the
0008 detailed list of fixes/additions, please refer to the related History files):
0009
0010 o Electromagnetic Processes:
0011 - Multiple scattering: fine tuning and fixes for low energy e-;
0012 inclusion of nuclear size effect for high energy (e+,e- > 100 MeV,
0013 hadrons > 1 GeV);
0014 - IonisationPlus: improved code and testing, for electrons and hadrons.
0015 - LowEnergy: implemented hadron and ion ionisation; minor fixes in
0016 photo electric process.
0017 - Xrays: fixes in Cerenkov process.
0018 - Created new examples in examples/extended/electromagnetic.
0019
0020 o Geometry:
0021 - Field: minor fixes, more access to user parameters and clearer warnings;
0022 - CSG/Booleans: fixes and more detailed unit tests;
0023 - BREPS/STEP: fix to the NIST STEP reader for complex surfaces;
0024 - Volumes: first implementation for visualization of voxels;
0025 - Transportation: added protection for zero step in field.
0026
0027 o Globals:
0028 - STLInterface:
0029 major modifications for removing all references to Rogue Wave classes;
0030 removed wrappers for hash dictionaries; reorganised classes/files.
0031 - management:
0032 introduced 'g4std' wrappers and keywords for migration to the ISO/ANSI
0033 C++ standard and usage of the std namespace; fixed minor bug in
0034 G4PhysicsVector.
0035
0036 o Hadronic Processes:
0037 - new isotope-production models for neutron induced production and
0038 corresponding design updates in hadronic/management;
0039 - additional string model for proton induced reactions;
0040 - design iteration on multi-fragmentation;
0041 - memory usage optimization in the neutron transport.
0042 NOTE: an updated set of neutron data files is now required.
0043
0044 o Particles:
0045 - introduced dynamical electric charge in G4DynamicParticle to allow
0046 change of charge for ions;
0047 - introduced new G4IsotopeTable to manage excitation energy, lifetime,
0048 and decay modes for isotopes;
0049 - corrected identifier for isotopes Promethium and Prasceodym;
0050 - corrected spelling for file-names and keyword "barion" to "baryon".
0051
0052 o Persistency:
0053 - added association of HitsCollection and PrimaryVertex to G4PEvent;
0054 added persistency of Boolean solid types; fixes for ODMG compliance;
0055 added G4PPRimaryParticle;
0056 - added new examples in examples/extended/persistency.
0057
0058 o Visualization:
0059 - introduced visualization of *components* of a boolean solid.
0060 Visualisation of the *result* of the boolean operation will be
0061 available in a future release;
0062 - introduced new commands (use help <command name> for more information):
0063 /vis/scene/add/logicalVolume
0064 /vis/viewer/update
0065 - improvements to FukuiRenderer (DAWN):
0066 made destination directory of g4.prim and g4.eps customizable
0067 with the environmental variable G4DAWNFILE_DEST_DIR; auto
0068 incrementation of output file names is now supported;
0069 - removed ray tracing, pending re-implementation.
0070
0071 Notes:
0072
0073 o Geant4 1.0 is based on STL. All direct references to Rogue Wave have
0074 been removed from the code. See notes below.
0075
0076 o The code released in Geant4 1.0 is not ISO/ANSI C++ compliant.
0077 A future minor release or patch will be provided that
0078 will include the ability to choose between using namespaces in
0079 ISO/ANSI mode or using traditional style "includes".
0080
0081 This code and some binary libraries are available through our "Source
0082 Code" Web page:
0083 - see our Geant4 Home Page (http://cern.ch/geant4).
0084
0085 Please refer to the Geant4 User Documentation
0086 (http://cern.ch/geant4/G4UsersDocuments/Overview/html)
0087 for further information about using Geant4.
0088 Updates to the documentation for Geant4 1.0 are still in preparation and are
0089 expected to be published within three weeks.
0090
0091
0092 Contents
0093 --------
0094
0095 1. Supported and Tested Platforms
0096 2. CLHEP 1.4
0097 3. The Standard Template Library (STL)
0098 4. Persistency
0099 5. Compiler Specific Problems
0100 6. Known Run-Time Problems
0101 7. Compilation Warnings
0102 8. Known Run-Time Warnings
0103
0104
0105 1. Supported and Tested Platforms
0106 ---------------------------------
0107
0108 o SUN Solaris 5.6, C++ 4.2 patch 104631-04.
0109 o HP 10.20, aCC C++ B3910B A.01.18 or A.01.21
0110 o Linux 2.0.35, gcc C++ egcs-2.91.66 (egcs 1.1.2).
0111 This configuration was tested in the RedHat 5.1 distribution, but
0112 versions of Geant4 have also been compiled successfully on RedHat 6.1,
0113 Debian and Suse distributions.
0114
0115 Platforms also tested but giving rise to some problems - see below:
0116
0117 o DEC V4.0, cxx C++ V6.1-027.
0118 o NT 4.0 with Service Pack 4 and Cygnus Tools b20 with:
0119 Visual C++ 6.0 Service Pack 2
0120
0121 Platforms configured but not tested and not supported:
0122 o SGI V6.5.5, CC 7.2.1 with ObjectSpace
0123 o AIX 4.3.2, xlC compiler with ObjectSpace
0124
0125 2. CLHEP 1.4
0126 ------------
0127
0128 Geant4 1.0 requires the installation of CLHEP 1.4.
0129
0130 See CLHEP 1.4 (http://cern.ch/clhep/INSTALLATION/clhep.html).
0131
0132 The following platform specific instructions apply:
0133
0134 DEC: Do *not* use the compiler option "-std strict_ansi".
0135
0136 NT: After configure, edit the file config/CLHEP-x86-cygnus-win32
0137 and comment out "#define HEP-USE-STD 1".
0138
0139
0140
0141 3. The Standard Template Library
0142 --------------------------------
0143
0144 The following versions of STL have been tested:
0145
0146 ObjectSpace STL on
0147 DEC, HP, NT and SUN.
0148
0149 See ObjectSpace (http://www.objectspace.com).
0150
0151 "Native" STL on: Linux, HP.
0152
0153 This is selected at installation/compile time by the environment variable
0154 G4USE_OSPACE in the case of the former - see documentation.
0155
0156 NOTES:
0157 - Be aware that by default, the installation scripts will expect to use
0158 the native STL implementation. You must set the G4USE_OSPACE variable
0159 in the environment in order to select the ObjectSpace implementation.
0160
0161 - Platform specific setup:
0162 o DEC: ObjectSpace is required.
0163 o HP: either ObjectSpace or native STL can be used. In order to use
0164 native STL you must also set the environment variable
0165 G4NO_STD_NAMESPACE.
0166 o SUN: ObjectSpace is required.
0167 o Linux: native STL is required.
0168 o NT: ObjectSpace is required.
0169 Support for native STL and ISO/ANSI installation will be added
0170 soon (future patch or minor release).
0171
0172 - A future minor release or patch will allow ISO/ANSI compliant installations.
0173 Their characteristics will be:
0174 o DEC: Native STL will be used
0175 o HP: The setup for native STL will trigger by default the ISO/ANSI
0176 installation (set G4NO_STD_NAMESPACE in the environment to avoid it.)
0177 o SUN: Support for CC 5.0 compiler and native STL (ISO/ANSI installation)
0178 o NT: Support for native STL and ISO/ANSI installation
0179 The modifications to support these installations will be tested soon.
0180 They will be made available in a patch or minor release.
0181
0182 Geant4 1.0 is the first release requiring the Standard Template Library.
0183 In the interest of stability, a significant part of the code still makes use
0184 of the "STL Interface" wrapper classes. For these the emphasis has remained
0185 on correct behaviour, rather than performance. The size of libraries and
0186 executables can appear considerably larger than the previous Rogue-Wave based
0187 versions.
0188
0189 4. Persistency
0190 --------------
0191
0192 - Platforms
0193
0194 Persistency in Geant4 1.0 release has been tested on the following
0195 platforms/software versions:
0196
0197 G4SYSTEM OS C++ compiler HepODBMS Objectivity
0198 --------- ----------- ------------ --------- -----------
0199 SUN-CC SunOS 5.6 CC 4.2 0.3.1.0 5.2
0200 HP-aCC HP-UX 10.20 aCC A.01.18 0.3.0.1 5.1.2
0201 Linux-g++ Linux RH5.1 egcs 1.1.2 0.3.0.1 5.1.2
0202
0203 A patch to run persistency examples on DEC-cxx will be released
0204 later, pending a fix to HepODBMS library.
0205
0206 - Known Problems
0207
0208 1) The following warning messages appear on some platforms during the
0209 installation of the libraries and the compilation of the example
0210 files. The message comes from the parser of the Objectivity
0211 preprocessor. It can be ignored.
0212
0213 -------------------------------------------------------------------------
0214 "/opt/SUNWspro/SC4.2/include/CC/generic.h", line 29: warning: omission of
0215 explicit type is nonstandard ("int" assumed)
0216 extern genericerror(int, char*);
0217 ^
0218 "/opt/SUNWspro/SC4.2/include/CC/iostream.h", line 781: warning: integer
0219 conversion resulted in a change of sign
0220 unsafe_istream& wignore(int=1, wchar_t=WEOF);
0221 ^
0222 "/opt/SUNWspro/SC4.2/include/CC/iostream.h", line 962: warning: integer
0223 conversion resulted in a change of sign
0224 istream& wignore(int=1, wchar_t=WEOF);
0225 -------------------------------------------------------------------------
0226
0227 2) The following warning messages appear during the installation of the
0228 library. This is due to a design choice of the persitent object
0229 and it can be safely ignored.
0230
0231 -------------------------------------------------------------------------
0232 warning: persistent-capable class member type is a problem
0233 The type of base class vector<G4VPhysicalVolume * > is a problem
0234 The type of member vector<G4VPhysicalVolume * >::start_ is pointer
0235 The type of member vector<G4VPhysicalVolume * >::finish_ is pointer
0236 The type of member vector<G4VPhysicalVolume * >::end_of_storage_
0237 is pointer
0238 The type of member vector<G4VPhysicalVolume * >::alloc_ is a
0239 problem
0240 The type of member allocator<G4VPhysicalVolume * >::impl_ is
0241 pointer
0242 G4VPhysVolRefVArray transPhysVolPtrs;
0243 ^
0244 -------------------------------------------------------------------------
0245
0246 3) The following warning messages appears during the installation of the
0247 libraries and the compilation of the example files. Dependency
0248 file is used to solve the GNUmake dependencies inside the Geant4
0249 categories and it can be safely ignored.
0250
0251 -------------------------------------------------------------------------
0252 In file included from /afs/cern.ch/sw/lhcxx/specific/@sys/HepODBMS/0.3.1.0/
0253 include/HepODBMS/odbms/HepODBMS.h:75,
0254 from include/G4PersistentTypes.hh:21,
0255 from include/G4VPersistentSubMan.hh:34,
0256 from src/G4VPersistentSubMan.cc:16:
0257 /afs/cern.ch/sw/lhcxx/specific/sun/Objectivity/5.2/include/oo.h:57:
0258 warning: No include path in which to find generic.h
0259 -------------------------------------------------------------------------
0260
0261 4) The following error messages appear at the end of the library
0262 installation, and it can be safely ignored.
0263
0264 -------------------------------------------------------------------------
0265 installing schema header files ...
0266 cp: cannot access /afs/cern.ch/sw/geant4/stt/ref+/AIX-xlC/debug/persistency/
0267 STL/tmp/SUN-CC/G4pglobal/*.hh
0268 schema header file does not exist, so ignore the error message...
0269 -------------------------------------------------------------------------
0270
0271 5) The following warning message appears at the runtime of the persistency
0272 examples, which is generated by HepDbApplication in HepODBMS.
0273 It can be ignored.
0274
0275 -------------------------------------------------------------------------
0276 Opening federated database OO_FD_BOOT.
0277 WARNING: g4example: Could not find naming root directory:
0278 Naming will be disabled.
0279 -------------------------------------------------------------------------
0280
0281
0282 5. Compiler Specific Problems
0283 -----------------------------
0284
0285 o DEC V4.0, cxx C++ V6.1-027.
0286
0287 We have found cases of mis-compilation of min and max templates
0288 on DEC. We have traced those which cause serious malfunction
0289 but there is no guarantee that there are no other cases.
0290 Detailed inspection of assembler output suggests that this
0291 problem might not be confined to min and max. This has been
0292 reported to DEC/Compaq. We understand a new version 6.2 of the
0293 compiler is now available. However we cannot guarantee correct
0294 execution of Geant4 on DEC with the current version of the
0295 compiler.
0296
0297 o NT
0298
0299 - Due to limitations of the VC++ optimiser, testing was done using
0300 the debuggable version only.
0301 - g3tog4 has not been ported to NT.
0302 - During the making of dependency files during compilation there
0303 are repeated warnings ("Strstrea.h not found") - this is an
0304 artifact of using g++ for this purpose.
0305 - Ignore linker warnings: "conflicts with use of other libs".
0306 - Ignore linker errors: "unresolved external symbol
0307 __imp__MessageBoxA@16".
0308
0309
0310 6. Known Run-Time Problems
0311 --------------------------
0312
0313 o Reading STEP files on DEC with optimised libraries causes a Memory
0314 fault - but see notes on DEC above.
0315 o In rare cases heavy ions appear not to be properly stopped and killed
0316 in tracking, therefore Geant4 sticks making many small steps. This
0317 behaviour has been observed on SUN and is under investigation.
0318 o On WindowsNT, a problem can occur reading the data files associated with
0319 the environment variable G4LEVELGAMMADATA. (Usually the value
0320 for this variable is $G4INSTALL/geant4/data/PhotonEvaporation .)
0321 A correction that resolves this anomalous behaviour will be issued
0322 soon, in a patch.
0323
0324
0325 7. Compilation Warnings
0326 -----------------------
0327
0328 There are compilation warnings on some platforms. We do not believe
0329 that any will lead to incorrect run-time behaviour, but we are working
0330 on reducing them.
0331
0332
0333 8. Known Run-Time Warnings
0334 --------------------------
0335
0336 The following messages can be written to error output while tracking. We
0337 believe none give rise to incorrect behaviour.
0338
0339 o G4PropagatorInField::LocateIntersectionPoint: Warning: Integration
0340 inaccuracy requires an adjustment in the step's endpoint Two
0341 mid-points are further apart than their curve length difference:
0342 Dist = xxx curve length = yyy
0343 o Warning in G4Navigator::ComputeStep: The Step's starting point has
0344 moved...
0345 o G4PropagateInField: Warning: Particle is looping
0346 - tracking in field will be stopped.
0347 It has performed 10000 steps in Field while a maximum of 10000
0348 are allowed.
0349
0350 For very high energy muons (ex. 1 TeV) warnings of this kind might be
0351 generated:
0352
0353 o G4ParticleChange::CheckIt : the Momentum Change is not unit vector !!
0354 Difference: 1e-09
0355 G4ParticleChange::CheckIt
