Skip to content

Logger updates #58

@coderdj

Description

@coderdj

The logging system should get the following backend overhauls:

  • Rotating log files. Old log files should be zipped and stored.
  • LOG_LEVEL option in ini file. Errors, warnings, and major state changes should always be reported.
  • Error timeout. If there's an error that occurs repeatedly (like a CAEN read error that might get spammed 100 times) it's enough to report it once.
  • Function to easily create a log string out of several types of input. This is really easy in python but C++ is slightly trickier due to strict variable type checking. Make sure to differentiate between dec and hex for numbers for registers, etc.
  • Display log on dispatcher should be unified with online log.
  • Also run tags to that the log can easily be shown for a single run or group of runs

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions