Understanding log-files produced by Bonmin
I want to obtain a feasible point for a MINLP using the feasibility pump implemented in Bonmin which I access via Pyomo (I use the parameter SolutionLimit = 1
).
For some problems, however, the method does not yield such a point within a time limit of 30 minutes and I wish to determine the reason.
Looking at the log-files, it appears that the reason is that the first auxiliary MILP is not being solved with Cbc. In fact, for the problem du-opt from the MINLPLib, after some time there appears to be no more progess in the solution of the MILP(?), and the following lines are repeated in the log:
OCbc0014I Cut generator 0 (Probing) - 0 row cuts average 0.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 1 (Gomory) - 1 row cuts average 20.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 2 (Knapsack) - 0 row cuts average 0.0
elements, 0 column cuts (0 active) in 0.000 seconds - new frequency
is -100
OCbc0014I Cut generator 3 (Clique) - 0 row cuts average 0.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 4 (FlowCover) - 0 row cuts average 0.0
elements, 0 column cuts (0 active) in 0.000 seconds - new frequency
is -100
OCbc0014I Cut generator 5 (MixedIntegerRounding2) - 0 row cuts average
0.0 elements, 0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0010I After 0 nodes, 1 on tree, 1e+50 best solution, best possible
-189 (0.02 seconds)
OCbc0012I Integer solution of -189 found by rounding after 2 iterations and 1 nodes (0.02 seconds)
OCbc0001I Search completed - best objective -189, took 2 iterations
and 1 nodes (0.02 seconds)
OCbc0032I Strong branching done 4 times (10
iterations), fathomed 0 nodes and fixed 0 variables OCbc0035I Maximum
depth 0, 0 variables fixed on reduced cost
OCbc0031I 1 added rows had
average density of 20 OCbc0013I At root node, 1 cuts changed objective
from -189 to -189 in 2 passes
This coincides with the fact that the only source of nonlinearity for this problem stems from the objective function and hence the method should not have problems with finding any feasible point - except the initial MILP is difficult to solve. So basically, my questions are as follows.
- Do the problems du-opt as well as instances of the problem squfl have a structure which makes the projection problem of the feasibility pump hard to solve?
- Can anyone point me to a place where I can learn how to read the log-files?
- Is the Bonmin mailing list maybe an appropriate place to ask such a question?
pyomo coin-or-cbc
add a comment |
I want to obtain a feasible point for a MINLP using the feasibility pump implemented in Bonmin which I access via Pyomo (I use the parameter SolutionLimit = 1
).
For some problems, however, the method does not yield such a point within a time limit of 30 minutes and I wish to determine the reason.
Looking at the log-files, it appears that the reason is that the first auxiliary MILP is not being solved with Cbc. In fact, for the problem du-opt from the MINLPLib, after some time there appears to be no more progess in the solution of the MILP(?), and the following lines are repeated in the log:
OCbc0014I Cut generator 0 (Probing) - 0 row cuts average 0.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 1 (Gomory) - 1 row cuts average 20.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 2 (Knapsack) - 0 row cuts average 0.0
elements, 0 column cuts (0 active) in 0.000 seconds - new frequency
is -100
OCbc0014I Cut generator 3 (Clique) - 0 row cuts average 0.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 4 (FlowCover) - 0 row cuts average 0.0
elements, 0 column cuts (0 active) in 0.000 seconds - new frequency
is -100
OCbc0014I Cut generator 5 (MixedIntegerRounding2) - 0 row cuts average
0.0 elements, 0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0010I After 0 nodes, 1 on tree, 1e+50 best solution, best possible
-189 (0.02 seconds)
OCbc0012I Integer solution of -189 found by rounding after 2 iterations and 1 nodes (0.02 seconds)
OCbc0001I Search completed - best objective -189, took 2 iterations
and 1 nodes (0.02 seconds)
OCbc0032I Strong branching done 4 times (10
iterations), fathomed 0 nodes and fixed 0 variables OCbc0035I Maximum
depth 0, 0 variables fixed on reduced cost
OCbc0031I 1 added rows had
average density of 20 OCbc0013I At root node, 1 cuts changed objective
from -189 to -189 in 2 passes
This coincides with the fact that the only source of nonlinearity for this problem stems from the objective function and hence the method should not have problems with finding any feasible point - except the initial MILP is difficult to solve. So basically, my questions are as follows.
- Do the problems du-opt as well as instances of the problem squfl have a structure which makes the projection problem of the feasibility pump hard to solve?
- Can anyone point me to a place where I can learn how to read the log-files?
- Is the Bonmin mailing list maybe an appropriate place to ask such a question?
pyomo coin-or-cbc
add a comment |
I want to obtain a feasible point for a MINLP using the feasibility pump implemented in Bonmin which I access via Pyomo (I use the parameter SolutionLimit = 1
).
For some problems, however, the method does not yield such a point within a time limit of 30 minutes and I wish to determine the reason.
Looking at the log-files, it appears that the reason is that the first auxiliary MILP is not being solved with Cbc. In fact, for the problem du-opt from the MINLPLib, after some time there appears to be no more progess in the solution of the MILP(?), and the following lines are repeated in the log:
OCbc0014I Cut generator 0 (Probing) - 0 row cuts average 0.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 1 (Gomory) - 1 row cuts average 20.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 2 (Knapsack) - 0 row cuts average 0.0
elements, 0 column cuts (0 active) in 0.000 seconds - new frequency
is -100
OCbc0014I Cut generator 3 (Clique) - 0 row cuts average 0.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 4 (FlowCover) - 0 row cuts average 0.0
elements, 0 column cuts (0 active) in 0.000 seconds - new frequency
is -100
OCbc0014I Cut generator 5 (MixedIntegerRounding2) - 0 row cuts average
0.0 elements, 0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0010I After 0 nodes, 1 on tree, 1e+50 best solution, best possible
-189 (0.02 seconds)
OCbc0012I Integer solution of -189 found by rounding after 2 iterations and 1 nodes (0.02 seconds)
OCbc0001I Search completed - best objective -189, took 2 iterations
and 1 nodes (0.02 seconds)
OCbc0032I Strong branching done 4 times (10
iterations), fathomed 0 nodes and fixed 0 variables OCbc0035I Maximum
depth 0, 0 variables fixed on reduced cost
OCbc0031I 1 added rows had
average density of 20 OCbc0013I At root node, 1 cuts changed objective
from -189 to -189 in 2 passes
This coincides with the fact that the only source of nonlinearity for this problem stems from the objective function and hence the method should not have problems with finding any feasible point - except the initial MILP is difficult to solve. So basically, my questions are as follows.
- Do the problems du-opt as well as instances of the problem squfl have a structure which makes the projection problem of the feasibility pump hard to solve?
- Can anyone point me to a place where I can learn how to read the log-files?
- Is the Bonmin mailing list maybe an appropriate place to ask such a question?
pyomo coin-or-cbc
I want to obtain a feasible point for a MINLP using the feasibility pump implemented in Bonmin which I access via Pyomo (I use the parameter SolutionLimit = 1
).
For some problems, however, the method does not yield such a point within a time limit of 30 minutes and I wish to determine the reason.
Looking at the log-files, it appears that the reason is that the first auxiliary MILP is not being solved with Cbc. In fact, for the problem du-opt from the MINLPLib, after some time there appears to be no more progess in the solution of the MILP(?), and the following lines are repeated in the log:
OCbc0014I Cut generator 0 (Probing) - 0 row cuts average 0.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 1 (Gomory) - 1 row cuts average 20.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 2 (Knapsack) - 0 row cuts average 0.0
elements, 0 column cuts (0 active) in 0.000 seconds - new frequency
is -100
OCbc0014I Cut generator 3 (Clique) - 0 row cuts average 0.0 elements,
0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0014I Cut generator 4 (FlowCover) - 0 row cuts average 0.0
elements, 0 column cuts (0 active) in 0.000 seconds - new frequency
is -100
OCbc0014I Cut generator 5 (MixedIntegerRounding2) - 0 row cuts average
0.0 elements, 0 column cuts (0 active) in 0.000 seconds - new frequency is -100
OCbc0010I After 0 nodes, 1 on tree, 1e+50 best solution, best possible
-189 (0.02 seconds)
OCbc0012I Integer solution of -189 found by rounding after 2 iterations and 1 nodes (0.02 seconds)
OCbc0001I Search completed - best objective -189, took 2 iterations
and 1 nodes (0.02 seconds)
OCbc0032I Strong branching done 4 times (10
iterations), fathomed 0 nodes and fixed 0 variables OCbc0035I Maximum
depth 0, 0 variables fixed on reduced cost
OCbc0031I 1 added rows had
average density of 20 OCbc0013I At root node, 1 cuts changed objective
from -189 to -189 in 2 passes
This coincides with the fact that the only source of nonlinearity for this problem stems from the objective function and hence the method should not have problems with finding any feasible point - except the initial MILP is difficult to solve. So basically, my questions are as follows.
- Do the problems du-opt as well as instances of the problem squfl have a structure which makes the projection problem of the feasibility pump hard to solve?
- Can anyone point me to a place where I can learn how to read the log-files?
- Is the Bonmin mailing list maybe an appropriate place to ask such a question?
pyomo coin-or-cbc
pyomo coin-or-cbc
asked Nov 14 '18 at 10:05
Christoph NeumannChristoph Neumann
587
587
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53297567%2funderstanding-log-files-produced-by-bonmin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53297567%2funderstanding-log-files-produced-by-bonmin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown