e_ltb_runner - Man Page

manual page for e_ltb_runner 2.6-DEBUG Floral Guranse


e_ltb_runner [options] [Batchfile] [PATH_TO_EPROVER]


e_ltb_runner 2.6-DEBUG "Floral Guranse"

Read a CASC LTB batch specification file and process it.


Print a short description of program usage and options.
Print the version number of the prover. Please include this with all bug reports (if any).
Verbose comments on the progress of the program. This differs from the output level (below) in that technical information is printed to stderr, while the output level determines which logical manipulations of the clauses are printed to stdout. The short form or the long form without the optional argument is equivalent to --verbose=1.
-o <arg>
Redirect output into the named file.
-d <arg>
Directory for individual problem output files. Default is the current working directory.
Handle different variants for each problem base name as required for CASC-27. This is very specific hack.
Handle different variants for each problem base name as required for CASC-28. This is very specific hack. Note that this requires eprover-ho for the third variant.
For each batch file, enter interactive mode after processing batch the batch problems. Interactive mode allows the processing of additional jobs with respect to the loaded axioms set. Jobs are entered via stdin and print to stdout.
Equivalent to --output-level=0.
-l <arg>
Select an output level, greater values imply more verbose output. Level 0 produces nearly no output, level 1 will output each clause as it is processed, level 2 will output generating inferences, level 3 will give a full protocol including rewrite steps and level 4 will include some internal clause renamings. Levels >= 2 also imply PCL2 or TSTP formats (which can be post-processed with suitable tools).
-w <arg>
Set the global wall-clock limit for each batch (if any).

Reporting Bugs

Report bugs to <schulz@eprover.org>. Please include the following, if possible:

* The version of the package as reported by eprover --version.

* The operating system and version.

* The exact command line that leads to the unexpected behaviour.

* A description of what you expected and what actually happend.

* If possible all input files necessary to reproduce the bug.


July 2023 e_ltb_runner 2.6-DEBUG Floral Guranse