Ticket #122 (closed: fixed)

Opened 12 years ago

Last modified 5 years ago

Alter Algorthim to Produce Useful logging before and after exec

Reported by: Nick Draper Owned by: Dickon Champion
Priority: major Milestone: Iteration 8
Component: Keywords:
Cc: Blocked By:
Blocking: Tester:

Description (last modified by Nick Draper) (diff)

The Algorithm base class should log at INFO level the following:

  • Algorithm Name and version
  • Parameters names and values (and if the values is the default)

just prior to execution.

and it should also log

  • Completion status (successfull, failed etc.)
  • Execution duration

just after execution.

Much of this data is already compiled for the AlgorithmHistory records, so you may be able to use some of that.

Change History

comment:1 Changed 12 years ago by Nick Draper

  • Owner set to Dickon Champion
  • Description modified (diff)
  • Summary changed from Alter Algorthim to Produce Usefull logging before and after exec to Alter Algorthim to Produce Useful logging before and after exec

comment:2 Changed 12 years ago by Dickon Champion

  • Status changed from new to closed
  • Resolution set to fixed

(In [951]) fixes #122

Simple logging implemented of algorithm parameters and values with g_log.information()

comment:3 Changed 12 years ago by Dickon Champion

  • Status changed from closed to reopened
  • Resolution fixed deleted

comment:4 Changed 12 years ago by Dickon Champion

  • Status changed from reopened to closed
  • Resolution set to fixed

(In [982]) fixes #122 removed logging for child algorithms

comment:5 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​970

Note: See TracTickets for help on using tickets.