Optimality gap in a mathematical model solver












0












$begingroup$


How is optimality gap obtained from a solver like CPLEX related to the objective function. Is a higher optimality gap desirable?










share|cite|improve this question











$endgroup$

















    0












    $begingroup$


    How is optimality gap obtained from a solver like CPLEX related to the objective function. Is a higher optimality gap desirable?










    share|cite|improve this question











    $endgroup$















      0












      0








      0





      $begingroup$


      How is optimality gap obtained from a solver like CPLEX related to the objective function. Is a higher optimality gap desirable?










      share|cite|improve this question











      $endgroup$




      How is optimality gap obtained from a solver like CPLEX related to the objective function. Is a higher optimality gap desirable?







      optimization mathematical-modeling integer-programming






      share|cite|improve this question















      share|cite|improve this question













      share|cite|improve this question




      share|cite|improve this question








      edited Oct 9 '17 at 3:07









      Erwin Kalvelagen

      3,2342512




      3,2342512










      asked Oct 8 '17 at 4:09









      SanerSaner

      62




      62






















          1 Answer
          1






          active

          oldest

          votes


















          1












          $begingroup$

          The gap between best possible objective and best found objective is obtained by keeping track of the best relaxation currently in the pool of nodes waiting for further processing. (For details see any book on Integer Programming).



          This is a very unique property of a MIP solver that practitioners (like me) use a lot: instead of looking for proven optimal solutions that take a long time to compute we are happy with a solution guaranteed not worse than x% from the optimal solution. This can often speed up solution times by a lot.



          Most other solution techniques (like meta-heuristics) do not have this capability and we don't know really how good their solutions are (except maybe using some probabilistic argument).



          A big advantage is that often most of the gap is reduced quite early (in other words we find good solutions quickly). It is not unusual to actually find the optimal solution quite quickly but that proving global optimality (that is when the gap becomes zero) takes a very long time.






          share|cite|improve this answer









          $endgroup$













            Your Answer





            StackExchange.ifUsing("editor", function () {
            return StackExchange.using("mathjaxEditing", function () {
            StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
            StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
            });
            });
            }, "mathjax-editing");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "69"
            };
            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
            },
            noCode: true, onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmath.stackexchange.com%2fquestions%2f2462438%2foptimality-gap-in-a-mathematical-model-solver%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1












            $begingroup$

            The gap between best possible objective and best found objective is obtained by keeping track of the best relaxation currently in the pool of nodes waiting for further processing. (For details see any book on Integer Programming).



            This is a very unique property of a MIP solver that practitioners (like me) use a lot: instead of looking for proven optimal solutions that take a long time to compute we are happy with a solution guaranteed not worse than x% from the optimal solution. This can often speed up solution times by a lot.



            Most other solution techniques (like meta-heuristics) do not have this capability and we don't know really how good their solutions are (except maybe using some probabilistic argument).



            A big advantage is that often most of the gap is reduced quite early (in other words we find good solutions quickly). It is not unusual to actually find the optimal solution quite quickly but that proving global optimality (that is when the gap becomes zero) takes a very long time.






            share|cite|improve this answer









            $endgroup$


















              1












              $begingroup$

              The gap between best possible objective and best found objective is obtained by keeping track of the best relaxation currently in the pool of nodes waiting for further processing. (For details see any book on Integer Programming).



              This is a very unique property of a MIP solver that practitioners (like me) use a lot: instead of looking for proven optimal solutions that take a long time to compute we are happy with a solution guaranteed not worse than x% from the optimal solution. This can often speed up solution times by a lot.



              Most other solution techniques (like meta-heuristics) do not have this capability and we don't know really how good their solutions are (except maybe using some probabilistic argument).



              A big advantage is that often most of the gap is reduced quite early (in other words we find good solutions quickly). It is not unusual to actually find the optimal solution quite quickly but that proving global optimality (that is when the gap becomes zero) takes a very long time.






              share|cite|improve this answer









              $endgroup$
















                1












                1








                1





                $begingroup$

                The gap between best possible objective and best found objective is obtained by keeping track of the best relaxation currently in the pool of nodes waiting for further processing. (For details see any book on Integer Programming).



                This is a very unique property of a MIP solver that practitioners (like me) use a lot: instead of looking for proven optimal solutions that take a long time to compute we are happy with a solution guaranteed not worse than x% from the optimal solution. This can often speed up solution times by a lot.



                Most other solution techniques (like meta-heuristics) do not have this capability and we don't know really how good their solutions are (except maybe using some probabilistic argument).



                A big advantage is that often most of the gap is reduced quite early (in other words we find good solutions quickly). It is not unusual to actually find the optimal solution quite quickly but that proving global optimality (that is when the gap becomes zero) takes a very long time.






                share|cite|improve this answer









                $endgroup$



                The gap between best possible objective and best found objective is obtained by keeping track of the best relaxation currently in the pool of nodes waiting for further processing. (For details see any book on Integer Programming).



                This is a very unique property of a MIP solver that practitioners (like me) use a lot: instead of looking for proven optimal solutions that take a long time to compute we are happy with a solution guaranteed not worse than x% from the optimal solution. This can often speed up solution times by a lot.



                Most other solution techniques (like meta-heuristics) do not have this capability and we don't know really how good their solutions are (except maybe using some probabilistic argument).



                A big advantage is that often most of the gap is reduced quite early (in other words we find good solutions quickly). It is not unusual to actually find the optimal solution quite quickly but that proving global optimality (that is when the gap becomes zero) takes a very long time.







                share|cite|improve this answer












                share|cite|improve this answer



                share|cite|improve this answer










                answered Oct 8 '17 at 8:25









                Erwin KalvelagenErwin Kalvelagen

                3,2342512




                3,2342512






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Mathematics Stack Exchange!


                    • 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.


                    Use MathJax to format equations. MathJax reference.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmath.stackexchange.com%2fquestions%2f2462438%2foptimality-gap-in-a-mathematical-model-solver%23new-answer', 'question_page');
                    }
                    );

                    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







                    Popular posts from this blog

                    android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

                    SQL update select statement

                    'app-layout' is not a known element: how to share Component with different Modules