[Coin-discuss] Re: Message Control
John J Forrest
jjforre at us.ibm.com
Tue Dec 6 09:51:18 EST 2005
Edgardo,
When I tried what you suggested it did not work as I did not get any error
messages when I tried an example. As I have said many times before, the
very loosely connected structure of Coin makes unified message handling
difficult. With Cbc at least you can get at the solver and so affect its
message handling. For Clp there was no way to affect the Coin messages,
even though you could make sure they shared a common message handler. I
intend to modify this by the end of the week so that the Coin messages
will be visible to the Clp user.
John Forrest
Edgardo Fuchs <edgardo_fuchs at mi.cl>
Sent by: coin-discuss-bounces at list.coin-or.org
12/05/2005 12:50 PM
Please respond to
edgardo_fuchs and Discussions about open source software for Operations
Research
To
coin-discuss at list.coin-or.org
cc
Subject
[Coin-discuss] Re: Message Control
John,
Thank you for your prompt response.
Solving a linear model with OsiClp, assuming that clpModelPtr is a pointer
to the Clp model, returned by getModelPtr():
clpModelPtr->messagesPointer()->setDetailMessages(10, 0, 2999);
effectively turns off informational messages from Clp, but does not turn
off messages from Coin (example Coin0506I Presolve).
The following alternative to explicitly turn on the warning and error
messages seems to work fine:
clpModelPtr->messageHandler()->setLogLevel(0);
clpModelPtr->messagesPointer()->setDetailMessages(3, 3000, 9000);
Although, it seems the newLevel values have different meaning than the
setLogLevel parameter. Where can I find the possible values and their
meanings for the newLevel parameter?
Regards,
Edgardo Fuchs
coin-discuss-request at list.coin-or.org wrote:
Send Coin-discuss mailing list submissions to
coin-discuss at list.coin-or.org
To subscribe or unsubscribe via the World Wide Web, visit
http://list.coin-or.org/mailman/listinfo/coin-discuss
or, via email, send a message with subject or body 'help' to
coin-discuss-request at list.coin-or.org
You can reach the person managing the list at
coin-discuss-owner at list.coin-or.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Coin-discuss digest..."
Today's Topics:
1. Message control (Edgardo Fuchs)
2. Re: Message control (John J Forrest)
3. Re: Message control (John J Forrest)
----------------------------------------------------------------------
Message: 1
Date: Fri, 02 Dec 2005 21:19:23 -0300
From: Edgardo Fuchs <edgardo_fuchs at mi.cl>
Subject: [Coin-discuss] Message control
To: COIN <coin-discuss at list.coin-or.org>
Message-ID: <4390E48B.6060109 at mi.cl>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
http://list.coin-or.org/pipermail/coin-discuss/attachments/20051202/76fb1aa4/attachment-0001.html
------------------------------
Message: 2
Date: Sat, 3 Dec 2005 05:39:34 -0500
From: John J Forrest <jjforre at us.ibm.com>
Subject: Re: [Coin-discuss] Message control
To: Discussions about open source software for Operations Research
<coin-discuss at list.coin-or.org>
Message-ID:
<OF2BF965AF.8A89BBEE-ON052570CC.0039C7E4-052570CC.003A81F9 at us.ibm.com>
Content-Type: text/plain; charset="us-ascii"
Edgardo,
You can use setDetailMessages (examples in Cbc/Samples) to set the detail
level for all messages < 6000 to high.
At present the best way would be to use one form of setDetailMessages to
switch off all messages and then switch back the >= 6000 messages one by
one.
As that seems inelegant I will add a new setDetailMessage to do by range.
Then it would be
.messageHandler()->setDetailMessage(3,0,5999);
Should be in a few hours.
John Forrest
Edgardo Fuchs <edgardo_fuchs at mi.cl>
Sent by: coin-discuss-bounces at list.coin-or.org
12/02/2005 07:19 PM
Please respond to
edgardo_fuchs and Discussions about open source software for Operations
Research
To
COIN <coin-discuss at list.coin-or.org>
cc
Subject
[Coin-discuss] Message control
Dear COIN list,
I need to control the message output, prinitng only those messages with
return code greater or equal than 6000 (ie warning or error).
I tried using setLogLevel, but even level 1 is too verbose, including
informational messages.
Is there another option to control the output in that way, or do I need to
write a message handler function?
Regards,
Edgardo Fuchs
--
Edgardo Fuchs
Santiago, Chile
Tel: +56 (2) 435 0090
Cel: +56 9837 8433
_______________________________________________
Coin-discuss mailing list
Coin-discuss at list.coin-or.org
http://list.coin-or.org/mailman/listinfo/coin-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.coin-or.org/pipermail/coin-discuss/attachments/20051206/e4197c1a/attachment.html>
More information about the Coin-discuss
mailing list