|
Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://theory.sinp.msu.ru/comphep_html/install/install.html
Дата изменения: Wed May 30 13:28:59 2001 Дата индексирования: Mon Oct 1 22:40:47 2012 Кодировка: |
Subsections
comphep_33.#.tar.gz
where # denotes a number of release. Unpack this file by
gzip -d comphep_33.#.tar.gz tar -xf comphep_33.#.tar
As a result a directory comphep_33.# should be created.
This directory contains source codes of the CompHEP package for UNIX platforms. After compilation of these codes the CompHEP binary executable files appear in the same directory. We shall refer to it below as a CompHEP root directory.
./create_c command started from the CompHEP root directory.
If the C compiler is detected and the C sources are compiled successfully you will see the message:
"C-part of code has been successfully compiled and linked."
"CompHEP could be started."
Otherwise the corresponding error message comes out. See the next section for a discussion of possible problems.
If the Fortran compiler is available and you would like to use Fortran for numerical calculation launch the
./create_f command. If the Fortran compiler is detected and the Fortran sources are also compiled successfully, the message appears:
"Fortran code has been successfully compiled." See the next section in the case of problem with compilation.
The files in the CompHEP root directory will be used only for reading and execution during the user session. It provides us with a possibility to have one CompHEP root directory for several users. To set the appropriate files modes start the
./set_mod command.
Each user has to create his own directory to work with CompHEP. See an instruction for the user installation in the next section. However for an express check of compiled version you could go to the ./test directory and launch ./comphep there.
Due to its first instruction the create_c command tests the existence of the CC file in the CompHEP root directory. If this file exists, the C compiler name and its options are read from this file. Otherwise, as we usually have at the first start of create_c, this file is created and contains default parameters.
After that the create_c program tests the necessary compiler options. For this goal it generates various programs with the same name test.c and tries to compile and link them. If compilation is not satisfactory, the create_c command finishes with the corresponding error message and asks you to rewrite the command file CC in order to fit the requirement. The current test file test.c is saved. So in the case of such an error you could update your CC file and start create_c again. The options listed below must be supported by C compiler:
The work of create_f is similar to that of create_c described above. The Fortran compiler must possess long character variables (e.g. CHARACTER*5000). The name of Fortran compiler and options of compilation are stored in the F77 file.
If all tests are passed on successfully the message appears:
A correction of the CC and F77 files could be used to tune compiler options according to your UNIX platform. In this case you should create CC or F77 by starting makeCC or makeF77, perform tunings in the CC or F77 files and launch create_c or create_f after that. For example, you could switch on an optimization flag.
There are two macro definitions for the C code, which could be useful to tune:
The first one is STRSIZ. This is a maximum size of strings in the CompHEP models. By default STRSIZ=2048. If you would like to embed in CompHEP some new interaction with a very cumbersome vertex you have to increase this size by the
-DSTRSIZ=<new value> option.
The second macro defines a type of integer numbers which are used in symbolic calculations by CompHEP. By default CompHEP uses the 'long' type. -DNUM_LONG_LONG forces the compiler to use 'long long'. This type is not the ANSI standard and, perhaps, it is not supported in your case. Different realizations of the 'long long' type use different formats for reading and writing such numbers. The user may specify this format defining the 'NUM_STR'. By default CompHEP uses
#define NUM_STR "lld"
-DNUM_DOUBLE option forces CompHEP to emulate integer numbers via 'double' float ones.
The makeCC program inserts an option which guarantees 8-byte size integer calculation in CompHEP. If the size of the standard `long' type is not enough, then the 'double' one is used.
The CompHEP root directory is not intended to start a session. For this purpose the user has to prepare a special working directory. A few working directories may be created for various tasks and by different users.
In order to provide the programs with an
access to the CompHEP files and commands the environment variable
COMPHEP should contain the corresponding path. We recommend to define the
COMPHEP variable in the user startup file.
The name of the startup file and the syntax
of the assignment instruction depends on the command interpreter.
For example, in the case
of tcsh the name of startup file is ~/.tcshrc or
~/.cshrc and the assignment is realized by the instruction
setenv COMPHEP <Path to CompHEP directory>
Let you have defined the COMPHEP variable and create a directory,
say, WORK for the CompHEP session. To prepare this directory for
processing call the program install from within this directory:
$COMPHEP/install
As a result the following sub-directories and files
should appear in your WORK directory:
models/ tmp/ results/
comphep comphep.ini
The directory models is used for files which describe models of particle interactions. The directory tmp is created for temporal files. The directory results is assigned for a CompHEP output.
To start a CompHEP session you should issue a command
./comphep
The comphep.ini file allows to choose an appropriate text font for the CompHEP window, select the color or colorless mode for the window and also switch on/off the sound signal. The syntax of this file is self-explanatory.
In the case of problem with installation under Unix mail to ilyin@theory.sinp.msu.ru
The CompHEP Windows9x/NT version is distributed in a compiled form due to the absence of standard C/Fortran compiler under the Windows9x/NT. Thus the program does not provide the user with compiling and linking options within the working session. The user should use the "Numerical interpreter" option to get numerical results.
The installation file bNNi.zip (where NN denotes a number of the release) is available to copy from the CompHEP Web-page. The installation procedure is the following:
unzip bNNi.zip
As a result a set of files and subdirectories should be created. This set corresponds to the user working directory in the UNIX release (see section 1.3). Executable and other files corresponding to those in the CompHEP root directory of the UNIX version (see section 1.1) are stored in the subdirectory bin.
To start a CompHEP session the user should launch the command
comphep.pif
in the installation directory.
Contact person for the Windows9x/NT version of CompHEP is A.P.
Kryukov
(e-mail:
kryukov@theory.npi.msu.su)