Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • F FEDOT
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ITMO-NSS-team
  • FEDOT
  • Issues
  • #800

Closed
Open
Created Aug 01, 2022 by Elizaveta Lutsenko@LizLutsenkoOwner

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
Assignee
Assign to
Time tracking