[Cgl] CglKnapsack PRINT_DEBUG

[Robin Lougee-Heimer]

Matt: 

Many people have (and use) write access to this cut generator, and the 
code inside the #define PRINT_DEBUG isn't being maintained (obviously). If 
there's still an issue will you submit a bug to the ticket system..or 
better yet, send fixes. 
We need more people maintaining the cuts.  Someone to improve the msg 
handling with log levels across all cut generators would be great, too. 

Robin

----------------------------------------------------------------------------------
Robin Lougee-Heimer, PhD
Program Manager, COIN-OR
IBM TJ Watson Research Center
1101 Kitchawan Road, Yorktown Heights, NY 10598
ph: 914-945-3032   fax: 914-945-3434 
robinlh at us.ibm.com
http://www.coin-or.org





Matthew Galati <magh at lehigh.edu> 
Sent by: cgl-bounces at list.coin-or.org
08/09/2009 09:10 AM

To
cgl at list.coin-or.org
cc

Subject
[Cgl] CglKnapsack PRINT_DEBUG






I am trying to debug something in my code (or CglKnapsack). I'd like some 
DEBUG dump from Cgl. There is a #define PRINT_DEBUG that looks helpful. 
However, if I uncomment it, there are lots of compiler errors. Can this be 
fixed? Or is there some log level for 'more information' when CglKnap is 
not doing what I expect?

Thanks,
Matt_______________________________________________
Cgl mailing list
Cgl at list.coin-or.org
http://list.coin-or.org/mailman/listinfo/cgl

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.coin-or.org/pipermail/cgl/attachments/20091210/46820da4/attachment.html