[Rivet] RivetLogging with Herwig++

[Kiran Joshi]

Hi,

I was being stupid and expecting all of the error messages to be redirected to the screen, as was the case when I was testing with Pythia8. 
In fact, all of the debug and error messages were being safely stored in Herwig's .log file.

Thanks for the tip about MSG_X("...").

Sorry for wasting your time.

Kiran

 
On 24 Mar 2011, at 13:28, Andy Buckley wrote:

> On 24/03/11 12:17, Kiran Joshi wrote:
>> Hi,
>> 
>> I've having trouble getting any logging/debug messages out of Rivet when running it through Herwig++.
>> I've included the following lines in my Rivet analysis:
>> 
>> void analyze(const Event& event) {
>> 	...
>> 	Log& log = Log::getLog("Rivet.Analysis.MY_TEST_ANALYSIS");
>> 	log << Log::ERROR << "This is a test error message." << endl;
>> 	...
>> }
> 
> All I can say is that it's much better (for several reasons) to just write
> 
> MSG_ERROR("This is a test error message.");
> 
> and you should never need to explicitly call
> getLog("my.log.hierarchy")... Analysis::getLog() will put the name in
> automatically.
> 
>> and in my Herwig++ input file, I've done:
>> 
>> set /Herwig/Analysis/RivetAnalysis:Debug Yes
>> 
>> But I still don't see any messages when I run the analysis.
> 
> I don't know anything about how Herwig++ is interfacing Rivet... David,
> can you help?
> 
> Andy
> 
> -- 
> Dr Andy Buckley
> SUPA Advanced Research Fellow
> Particle Physics Experiment Group, University of Edinburgh
> 
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.hepforge.org/lists-archive/rivet/attachments/20110324/0e3de307/attachment.html>