Project

General

Profile

Support #15000

Audit all messages produced by artdaq during normal running

Added by Eric Flumerfelt almost 3 years ago. Updated 10 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Needed Enhancements
Target version:
-
Start date:
04/15/2015
Due date:
05/08/2015
% Done:

67%

Estimated time:
(Total: 20.00 h)
Experiment:
-
Co-Assignees:
Duration: 24

Description

We should take the time to double check what messages are being sent at various levels of verbosity. I have started a framework in artdaq/DAQdata/Globals.hh for assigning TRACE levels to various aspects of the system. MessageFacility can be configured to send TRACE messages in 4 levels (LogError, LogWarning, LogInfo, LogDebug), with an offset. My initial idea for a priority scheme would be the following:

1. Error (MessageFacility)
2. Warning (MessageFacility)
3. Info (MessageFacility)
4. Debug (MessageFacility)
5. Verbose (TRACE level Debug + 1)
6. Trace (TRACE)
7. <Module Specific 1> (TRACE)
8. <Module Specific 2> (TRACE)

We should certainly avoid generating tons of MessageFacility messages during "normal" running.


Subtasks

Idea #13389: Make sure error messages are as useful as possible for end usersClosedJohn Freeman

Feature #8343: Investigate new warnings since we started using art v1_13_01Closed

Support #18155: create message logging best practicesNewRon Rechenmacher

History

#1 Updated by Eric Flumerfelt almost 3 years ago

  • Category set to Needed Enhancements


Also available in: Atom PDF