Make logging output not so scary for end-user
Created by: gkirgizov
During Graph verification (GraphVerifier
) & Pipeline evaluation (PipelineObjectiveEvaluate
with EvaluationDispatcher
) usually happen a lot of errors.
By default these errors are output to the logger and to the console. They bloat the console and create the impression that something goes terribly wrong. Fedot shouldn't create such impression and shouldn't by default output to the user information that's unhelpful,
I propose that
- console and log file must have different and configurable logging levels
- by default console should output only informative messages about optimization process
- all messages should by default go to the log file
- in tests console output must output all verification & evaluation errors
Regarding message log levels:
- critical evaluation errors (which could lead to the failure of optimisation) should be errors
- noncritical pipeline eval errors (from which optimiser recovers) should be warnings or debug-level messages (depending on severity)
- verification errors seem to be expected errors and possibly should be debug-level messages