Minor Update : new version SGV 2.21
Functional Changes:
- The routine ZTDTGE now also returns the type of calorimeters (electromagnetic, hadronic or both). NB: this means that the calling sequence has changed!
- Two new arrays have been added to the common block /ZACLU/: CDCLU (the particle identification code of the cluster), and CHACLU (the charge of the cluster). For details, see here .
- In the interface to SUSYGEN, the calling sequence has been updated to that of SUSYGEN version 2.20/03. The old calling sequence is kept in the code, but is commented out.
- Several changes has been made in the organization of the code
and in the com-files/scripts.
To take advantage of these new features, it is
HIGHLY
RECOMMENDED to run CRESGVEXE with the "crecra" argument
once, to get a new patchy-cradle that is correct for
the new organisation of the source-code. This cradle is
well-commented, and describes how to activate the new
features.
The changes are:
- The user pam-file has been split in two: SGVUSER.CAR and SGVEVSIM.CAR. For all users content with the default generators (JETSET, PYTHIA, SUSYGEN, external read), this saves space and effort. For those having their own generator interfaces, this instruction should be enough to understand how to incorporate it.
- A simple method to get the latest corrections has been introduced.
- If the argument "debug" is used with CRESGVEXE, not only the user-code will be ready for debugging, but also the full SGV libraries. This assumes that the libraries where created both in optimized and debug mode. The script will correctly take hand of selecting the right version.
- On UNIX, all the SGV-scripts now have mode "x", so it is no longer needed to specify "ksh" before executing them. In addition, the set-up script "sgvenv" adds $SGV_PAM to the end of Your path-variable, so it will be enough to type just the name of the script.
- On UNIX under afs, the SGV_LIB symbol now uses the '@sys'-construct, meaning that it will be completely transparent to move from one system to another: SGV_LIB will always refer to the library compiled for the present system.
- Also on UNIX, the soft-links made by the scripts sgvass now have the option "-f", meaning that it's no longer needed to remove old links before executing the script.
Bug fixes :
- The polar angle of the thrust-axis was not calculated correctly in ZAUTHR. This has been fixed. Note that all other values calculated by this routine were already correct.
- In ZDETSI, the calling sequence of ZDPAIR was wrong. This has been fixed.
- Also in ZDETSI, a protection has been introduced against events over-flowing the space in the ZX common-blocks. If this occurs, a warning is printed, the event is skipped, ant execution continues with the next event.
- The initialization in ZDBREM was not correct, which on rare occasions could make the results wrong. This has been fixed.
- The way user-defined random-generator seeds were transferred from ZXGORD to ZXINI could occasionally yield rounding-errors, so that the seed actually loaded was not the one specified. This has been fixed.
- In ZXRUEN, the call to the user ending routine ZARUEN was after hbook-files had been closed. Hence, the user couldn't fill ntuples or histograms with end-of-run values. Therefore, the call to ZARUEN has been moved to a position before the hbook ending.
- In ZDCALO, a protection has been put in against the case when a spiraling hadron hits a forward electromagnetic calorimeter with a very slanting angle. This configuration caused crashes on some systems when attempting to calculate how much energy the particle would loose while traversing the calorimeter.
- In ZTFOLN, neutrals not hitting any detector layers were not treated correctly. This could give rise to events where the total true energy was above the generated CMS energy. This has been fixed.
- In ZXHINI and ZXHEND, a conditional section in the declaration part has been introduced, to cope with the fact that LINUX/G77 does not accept the construct CHARACTER*(*) as a declaration of a routine argument. If this is a bug in G77 or SGV is unclear.
Documentation :
- The users guide and reference manual has been updated due to the changes above.