Starting and Restarting
KEPLER is initiated by typing:
KEPLER NAMEP ( GENERATOR | DUMP ) ( OPTION )*
kepler s25s2a s25s2ag s
is the executable which is to be run.
The version used for a given run and its date are recorded at the beginning of each ASCII output file.
is the character name given to the current problem. This name is also used to begin the names for various output and dump files created during this problem (see below).
- GENERATOR | DUMP
is a character name of either a generator file (in which case its name must end in g (e.g.,
s25s2ag), or a restart dump (in which case its name must not end in g (e.g.,
To generate from file NAMEPg.
To restart from file NAMEPz,
To restart from file NAMEP(with last character deleted)#presn.
To restart from file NAMEP(with last character deleted)#final.
similar to z, z1? z9 will star up dumps with that ending. The creation of these files is controlled by nzsave (p 488).
start from labeled dump with same base name.
*g, *z, *#*
separate out base name for run automatically.
Changed In Version <15.0.0: Added z[0-9]* and # options and automatic base name separation.
(optional) is a set of one or more space delimited words in arbitrary order chosen from among the following possibilities:
To suspend the code after starting.
do not load BURN data and kill burning, similar to the killburn command.
To destroy the ASCII output files after sending them to the microfiche printer (not currently implemented – see also the discussion of parameter iautoout (p 159).
To automatically make a paper copy of the ASCII output files (not currently implemented).
write out stored command file (overwrite existing).
append stored command file.
make plot on start-up.
suppress graphical output, e.g., for batch mode.
DEBUG mode. Allow running without proper git hash.
Extended DEBUG mode. Could be used to enable internal debugging code. Adds
Changed In Version >15.0.0: Added k option.
Changed In Version 17.1.0: Added c and a options.
Changed In Version 17.6.0: Added x option.
Changed In Version 17.11.7: Added p and n options.
Changed In Version 18.0.1: Added X option.
Due to automatic name decomposition, run names must not end in the
In the absence of any OPTIONs, the code will begin calculations
imniediately and keep its ASCII output files on disk. It will either
generate from cycle
0 if NAMEGIZ is the name of a valid
generator file or restart a previous problem if
NAMEGIZ is the name of a restart dump compatible with this
version of KEPLER. The code will attempt to restart from restart
dumps created by older versions of KEPLER by setting any newly added
parameters to their default values, and printing warning messages
concerning possible incompatibilities. Such compatibility, however,
is not guaranteed, and it is the user’s responsibility to carefully
check whether such a restart operation has been perfonned correctly
restart). If equation of state routine changes
have been made in the interim, the newe or eostrans commands
may be helpful.
Required Input Files
The current working directory must contain the specified compiled version of KEPLER, a link to a current version of KEPLER or KEPLER is in the PATH specification. The named generator or restart file must also be physically resident in the current directory.
All other files KEPLER needs should either be in the local
dicrectory (searched first), in the path set in the
variable using the datapath card in the generator (searched
second), or in the path provided in the
environment variable. In bash, e.g., in the
this can be set using the command
/ in the path spcification needs to be
If BURN co-processing has been specified, the directory in which
KEPLER is in must also contain the BDAT data file,
which contains the needed nuclear cross-sections for detailed isotopic
networks. This file by default is in
$HOME/kepler/local_data and can be soft-linked to the
current working directory by the command
ln -s ~/kepler/local_data/bdat .
Further files that are usually needed include
solabu.dat branch.dat nuccedat nuncdat nuccecdat adapnet.cfg opal95.dat alamos1.dat alamos2.dat alamos3.dat alamos4.dat wdat decay.dat condall06.dat
In order for MONGO plots to work, KEPLER needs to know where to
locate the corresponding font files. The easiest way is to set
environment variables to their location. Usually, these files should
be located in the subdirectory
~kepler/mongo. In bash
these can be set using
export HELPFILE=$HOME/kepler/mongo/help.dat export MONGOPS=$HOME/kepler/mongo/postscript/ export FONTDAT=$HOME/kepler/mongo/fonts.dat export FONTNEW=$HOME/kepler/mongo/fonts.vis
All see settings can also be done by the initialisation script,
which should conveniently be called from the
See also Setup.
KEPLER writes all I/O in big endian format. For the Intel
compiler one should therefore set the environment variable
accordingly. In bash, this can be done using the command
export F_UFMTENDIAN big
Debug and Production Runs
By default KEPLER will no longer run if built from a non-clean git
status of the
source directory. You can for running force
debug purpose if you specify the
x flag on the command line.
The purpose of this change is to ensure code git hashes for the KEPLER version running a problem remain accurate. Results from non-clean git repos can never be traced back later with any level of confidence.
New In Version 17.6.0.
Deprecated Since Version >15.0.0.
qlib file and the
Deprecated Since Version >15.0.0.
If post-processor dumps have been requested in the generator file (or
less desirably initiated by a command from the terminal), KEPLER
will create a (
qlib) library file with a name in the form
NAMEP.lib (e.g., :code`s25s2a.lib`) whith maintains a
record of zonal mass coordinates and stores a time history of the time
edit variables. A series of post-processor dump (
s25s2a.qa) which stores a compressed time
history of the dump variables specified by dump commands. These
files are updated every ncycqq (p 299) cycles. The
file can store information for up to
20000 * ncycqq (p 299)
KEPLER cycles and up to
17999 distinct grid points before
becoming full. For ease in handling, however, the post-processor dump
files are limited to a size of lenqmax (p 44) whose default value is
3000000 bytes. New post-processor dumps will be created as
required with suffixes in the sequence: .qa, .qb,
.qz, .q0, … .q9, .ra, .rb, .rz,
.r0, … .r9, etc. The qlib library file must always stay
on-line while the problem it corresponds to is running, but all but
the most recent post-processor dump (
Restart Dump Files
KEPLER will create a running restart (z) file named in the form
s25s2az), which it overwrites every
ndump (p 18) cycles. It will also create labeled restart dumps with
names in the form NAMEP#
s25s2aZ#12750) every ndump (p 18) * nsdump (p 156) cycles, where
ncyc is the current cycle number. If a file with the name
ncyc already exists, it will be overwritten.
Ascii Output Files
KEPLER will also create ASCII output files with names in the form
NCYCO is the cycle number at which the problem is being generated
or restarted. To prevent such files from becoming too large, however,
the current output file is closed whenever
,nnewoutf (p 197)
) = 0 (by current default every
2000 cycles) and a new output file with a name in the form
s25s2az_2000) is created.
These types of ASCII output file will overwrite any file by the same
name that might already exist.
Dump-Grid Status Files
Deprecated Since Version <15.0.0.
If post-processor dumps are being made, KEPLER will also alternately
create, read, and destroy files with names in the form NAMEP.0 and NAMEP.1 (e.g.,
s25s2a.1) which contain information about the grids currently
being used to represent each requested dump variable. This reduces
the size of the KEPLER executable file at the cost of some extra files
on disk. If for any reason (restart, disk crash, etc.), these flies
are not available, KEPLER will automatically generate a new set of
dump grids along with a warning message. This is not really a problem
except that it takes up a little extra space in the post-processor