Ticket #6205 (assigned)
Separate non-algorithm objects that log in algorithms don't observe the setLogging flag
Reported by: | Martyn Gigg | Owned by: | Anyone |
---|---|---|---|
Priority: | minor | Milestone: | Backlog |
Component: | Framework | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description ¶
The script below still outputs some logging information from a helper class that does not respect the value of the setLogger property on the algorithm.
from mantid.api import * def run_algorithm(name, logging, **kwargs): alg = AlgorithmManager.createUnmanaged(name) alg.initialize() alg.setLogging(logging) for key, value in kwargs.iteritems(): alg.setProperty(key, value) alg.execute() return alg #=================================================================== run_algorithm('LoadRaw',logging=False, OutputWorkspace='ws',Filename='CSP79590.raw')
Change History
comment:1 Changed 8 years ago by Nick Draper
- Owner set to Anyone
- Status changed from new to assigned
comment:2 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.4 to Release 2.5
Moved at the code freeze for release 2.4
comment:6 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to the Backlog after the code freeze for R2.6
Note: See
TracTickets for help on using
tickets.
Perhaps we do want a shared base class for algorithm helper classes, to sort out things like this.