Open chcorbato opened 4 years ago
Pellet uses JDK logging. The verbosity of this logging can be controlled with a configuration file. The distribution includes a sample
configuration,examples/logging.properties
. The location of the configuration file can be specified by setting the systempropertyjava.util.logging.config.file
. The location should be specified as a (relative or absolute) path. For example, the following command would use a local file located in the current directory:java -Djava.util.logging.config.file=my-logging.properties -jar lib\pellet-cli.jar
Note that, in the configuration file, in addition to changing the log level for specific loggers, you must change the handler’s level (you can think of it as two levels of severity checks — one at log record generation, one at consumption). You can find more information about JDK logging here.
It was very promising, but I am not familiar at all with java logging and I could not follow the pointers:
configuration,examples/logging.properties
-> I could not find it
You can find more information about JDK logging [here(http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/overview.html)
-> link not working anymore
The Pellet reasoner called with owlready2 produces and output that is annoying when debugging (see below) I could not figure out how to remove it from the output. Owlready2 documents do not explain how to handle that I tried this to temporarily remove it form the
stdout
, but it did not work.Any ideas are welcome @gavanderhoorn @ipa-hsd @ipa-nhg @marioney
https://github.com/rosin-project/mros1_reasoner/blob/8de2e484650154245ed1eae0efebaa9ee711fe1b/mros1_reasoner/scripts/mros1_reasoner.py#L230
OUTPUT