Project

General

Profile

Milestone #1144

Defining categories for the error logger

Added by Rob Kutschke over 8 years ago. Updated over 1 year ago.

Status:
Accepted
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
-
Start date:
04/04/2011
Due date:
09/30/2013
% Done:

0%

Estimated time:
16.00 h
Experiment:
-
Duration: 911

History

#1 Updated by Rob Kutschke over 8 years ago

At the last Friday meeting I showed some of my proposed example code for an art example package. The first module uses std::cerr to print the event number. Chris suggested changing it to use LogInfo. My first thought was that this makes sense. But it does not really make sense to introduce the message logger system without describing what categories mean and how to use them. I am a little worried that this is getting too overwhelming for one of the intended audiences. Any suggestions here? Maybe a category of "Heartbeat"? All of the examples that I have generate only heartbeat messages. Does the current message logger have an interface that takes a category type so that we can restrict the categories used by people?

#2 Updated by Walter E Brown over 7 years ago

  • Tracker changed from Feature to Meeting

#3 Updated by Christopher Green almost 6 years ago

  • Tracker changed from Meeting to Milestone
  • Due date set to 09/30/2013
  • Category set to Infrastructure
  • Status changed from New to Accepted
  • Estimated time set to 16.00 h
  • Experiment - added

#4 Updated by Kyle Knoepfel over 4 years ago

  • Target version set to 521

#5 Updated by Kyle Knoepfel over 1 year ago

  • Target version deleted (521)


Also available in: Atom PDF