search

viadee / javaAnchorExplainer

Explains machine learning models fast using the Anchor algorithm originally proposed by marcotcr in 2018
BSD 3-Clause "New" or "Revised" License
15 stars 3 forks source link

Modify log-levels when creating global explanations #12

Closed TobiasGoerke closed 5 years ago

TobiasGoerke commented 5 years ago

Only a few info-level log messages get created when constructing a single anchor. Global explainers that aggregate local explanations accordingly spawn thousands of these log messages. While such log messages are relevant for the first scenario (that is why level info is set) they are impratical in the second one. Unfortunately, SLF4J does not allow to change the log level at runtime.

=> Find some way to change the log level to prevent bloated log files.

fkoehne commented 5 years ago

Why not shift this into debug level outputs?

fkoehne commented 5 years ago

On the server we can than switch spring profiles.

TobiasGoerke commented 5 years ago

The log output is most likely relevant when creating local explanations. Setting them to debug would mute any output in this scenario.

fkoehne commented 5 years ago

In my view, any relevant information (from a user perspective) should be contained in the calculation result. The info level is regularly understood as "interesting from an administrator perspective", i.e. "is the server started?" or "which modules are loaded?". Ok for you?

TobiasGoerke commented 5 years ago

This is okay for me. I've already reduced the amount of "irrelevant" info level log messages. So, global explanations are to include a number of messages, which is reasonable.