removing duplicate proof definition

git-svn-id: https://gapt.googlecode.com/svn/trunk@2364 85d21ef8-add0-11de-ae77-5bfb9c5a3f34
Added documentation and commits for the runOnProver9Proofs script.


git-svn-id: https://gapt.googlecode.com/svn/trunk@2365 85d21ef8-add0-11de-ae77-5bfb9c5a3f34
Fixing logging information in cut-introduction

git-svn-id: https://gapt.googlecode.com/svn/trunk@2366 85d21ef8-add0-11de-ae77-5bfb9c5a3f34
Fixing timeout for cut-introduction tests

git-svn-id: https://gapt.googlecode.com/svn/trunk@2367 85d21ef8-add0-11de-ae77-5bfb9c5a3f34
Increasing proof sequences incrementally

The test script for cut-introduction now tests the
proof sequences (n) by iteratively increasing n,
stopping only when a timeout is reached.

git-svn-id: https://gapt.googlecode.com/svn/trunk@2368 85d21ef8-add0-11de-ae77-5bfb9c5a3f34
Removing println from StandartClauseSet.
Removing logging

The logging mechanism, although useful, is being
in my opinion overly used in gapt. We shouldn't
use logging for debugging, and we shouldn't leave
debugging lines in the main repository code. Also,
making a class extend yet another interface is
really overloading its responsabilites and the
code is often harder to read with all the
debugging lines around. Another reason I can think
of for removing the logging from all these files
is the fact that we either need to keep a very
long (and constantly needing updates) log4j file
or we live with its warning messages.
For running the cut-introduction experiments, the
only logging that is left is the one in the test
script itself, and no other if I can help it.

Conflicts:
	source/algorithms/lk/src/main/scala/at/logic/algorithms/lk/solve.scala
	source/algorithms/resolution/src/main/scala/at/logic/algorithms/resolution/robinson.scala
	source/syntax/calculi/lk/src/main/scala/at/logic/calculi/lk/macroRules.scala