how to access Gurobi variable attributes before optimizing model












0















I wanted to check variable name, upper bound and lower bound before calling optimize() method in gurobi. When i tried this its giving me error.But same is working fine if called after optimize method.



In below code:
First "x.get(GRB_StringAttr_VarName)" is not working which i called before optimize().
Where second "x.get(GRB_StringAttr_VarName)" is working fine.
For my work i need to call get name and upper bound before optimize method.
Please help



    GRBEnv env = GRBEnv();

GRBModel model = GRBModel(env);

// Create variables

GRBVar x = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "x");
GRBVar y = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "y");
GRBVar z = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "z");

// Set objective: maximize x + y + 2 z
cout << x.get(GRB_StringAttr_VarName) << " " << endl;

model.setObjective(x + y + 2 * z, GRB_MAXIMIZE);
// Add constraint: x + 2 y + 3 z <= 4
model.addConstr(x + 2 * y + 3 * z <= 4, "c0");
// Add constraint: x + y >= 1
model.addConstr(x + y >= 1, "c1");
// Optimize model
model.optimize();

cout << x.get(GRB_StringAttr_VarName) << " "
<< x.get(GRB_DoubleAttr_X) << endl;
cout << y.get(GRB_StringAttr_VarName) << " "









share|improve this question





























    0















    I wanted to check variable name, upper bound and lower bound before calling optimize() method in gurobi. When i tried this its giving me error.But same is working fine if called after optimize method.



    In below code:
    First "x.get(GRB_StringAttr_VarName)" is not working which i called before optimize().
    Where second "x.get(GRB_StringAttr_VarName)" is working fine.
    For my work i need to call get name and upper bound before optimize method.
    Please help



        GRBEnv env = GRBEnv();

    GRBModel model = GRBModel(env);

    // Create variables

    GRBVar x = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "x");
    GRBVar y = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "y");
    GRBVar z = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "z");

    // Set objective: maximize x + y + 2 z
    cout << x.get(GRB_StringAttr_VarName) << " " << endl;

    model.setObjective(x + y + 2 * z, GRB_MAXIMIZE);
    // Add constraint: x + 2 y + 3 z <= 4
    model.addConstr(x + 2 * y + 3 * z <= 4, "c0");
    // Add constraint: x + y >= 1
    model.addConstr(x + y >= 1, "c1");
    // Optimize model
    model.optimize();

    cout << x.get(GRB_StringAttr_VarName) << " "
    << x.get(GRB_DoubleAttr_X) << endl;
    cout << y.get(GRB_StringAttr_VarName) << " "









    share|improve this question



























      0












      0








      0








      I wanted to check variable name, upper bound and lower bound before calling optimize() method in gurobi. When i tried this its giving me error.But same is working fine if called after optimize method.



      In below code:
      First "x.get(GRB_StringAttr_VarName)" is not working which i called before optimize().
      Where second "x.get(GRB_StringAttr_VarName)" is working fine.
      For my work i need to call get name and upper bound before optimize method.
      Please help



          GRBEnv env = GRBEnv();

      GRBModel model = GRBModel(env);

      // Create variables

      GRBVar x = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "x");
      GRBVar y = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "y");
      GRBVar z = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "z");

      // Set objective: maximize x + y + 2 z
      cout << x.get(GRB_StringAttr_VarName) << " " << endl;

      model.setObjective(x + y + 2 * z, GRB_MAXIMIZE);
      // Add constraint: x + 2 y + 3 z <= 4
      model.addConstr(x + 2 * y + 3 * z <= 4, "c0");
      // Add constraint: x + y >= 1
      model.addConstr(x + y >= 1, "c1");
      // Optimize model
      model.optimize();

      cout << x.get(GRB_StringAttr_VarName) << " "
      << x.get(GRB_DoubleAttr_X) << endl;
      cout << y.get(GRB_StringAttr_VarName) << " "









      share|improve this question
















      I wanted to check variable name, upper bound and lower bound before calling optimize() method in gurobi. When i tried this its giving me error.But same is working fine if called after optimize method.



      In below code:
      First "x.get(GRB_StringAttr_VarName)" is not working which i called before optimize().
      Where second "x.get(GRB_StringAttr_VarName)" is working fine.
      For my work i need to call get name and upper bound before optimize method.
      Please help



          GRBEnv env = GRBEnv();

      GRBModel model = GRBModel(env);

      // Create variables

      GRBVar x = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "x");
      GRBVar y = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "y");
      GRBVar z = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "z");

      // Set objective: maximize x + y + 2 z
      cout << x.get(GRB_StringAttr_VarName) << " " << endl;

      model.setObjective(x + y + 2 * z, GRB_MAXIMIZE);
      // Add constraint: x + 2 y + 3 z <= 4
      model.addConstr(x + 2 * y + 3 * z <= 4, "c0");
      // Add constraint: x + y >= 1
      model.addConstr(x + y >= 1, "c1");
      // Optimize model
      model.optimize();

      cout << x.get(GRB_StringAttr_VarName) << " "
      << x.get(GRB_DoubleAttr_X) << endl;
      cout << y.get(GRB_StringAttr_VarName) << " "






      c++ optimization gurobi mixed-integer-programming






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 27 '18 at 23:17









      joni

      768157




      768157










      asked Nov 27 '18 at 11:51









      gajananbejgamwargajananbejgamwar

      63




      63
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Gurobi has a lazy update approach. After you create your variables, you need to run model.update() to write the changes to your model. Only after that you can use the methods of a variable object:



          #include "gurobi_c++.h"
          using namespace std;

          int main(int argc, char *argv){
          GRBEnv env = GRBEnv();

          GRBModel model = GRBModel(env);

          // Create variables

          GRBVar x = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "x");
          GRBVar y = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "y");
          GRBVar z = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "z");
          model.update();

          // Set objective: maximize x + y + 2 z
          cout << x.get(GRB_StringAttr_VarName) << " " << endl;

          model.setObjective(x + y + 2 * z, GRB_MAXIMIZE);
          // Add constraint: x + 2 y + 3 z <= 4
          model.addConstr(x + 2 * y + 3 * z <= 4, "c0");
          // Add constraint: x + y >= 1
          model.addConstr(x + y >= 1, "c1");
          // Optimize model
          model.optimize();

          cout << x.get(GRB_StringAttr_VarName) << " " << x.get(GRB_DoubleAttr_X) << endl;
          cout << y.get(GRB_StringAttr_VarName) << " ";
          }


          Note that model.write() and model.optimize() both will call model.update() automatically. That's the reason why your second



           cout << x.get(GRB_StringAttr_VarName) << " " << x.get(GRB_DoubleAttr_X) << endl;


          works.






          share|improve this answer























            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
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53499037%2fhow-to-access-gurobi-variable-attributes-before-optimizing-model%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









            0














            Gurobi has a lazy update approach. After you create your variables, you need to run model.update() to write the changes to your model. Only after that you can use the methods of a variable object:



            #include "gurobi_c++.h"
            using namespace std;

            int main(int argc, char *argv){
            GRBEnv env = GRBEnv();

            GRBModel model = GRBModel(env);

            // Create variables

            GRBVar x = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "x");
            GRBVar y = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "y");
            GRBVar z = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "z");
            model.update();

            // Set objective: maximize x + y + 2 z
            cout << x.get(GRB_StringAttr_VarName) << " " << endl;

            model.setObjective(x + y + 2 * z, GRB_MAXIMIZE);
            // Add constraint: x + 2 y + 3 z <= 4
            model.addConstr(x + 2 * y + 3 * z <= 4, "c0");
            // Add constraint: x + y >= 1
            model.addConstr(x + y >= 1, "c1");
            // Optimize model
            model.optimize();

            cout << x.get(GRB_StringAttr_VarName) << " " << x.get(GRB_DoubleAttr_X) << endl;
            cout << y.get(GRB_StringAttr_VarName) << " ";
            }


            Note that model.write() and model.optimize() both will call model.update() automatically. That's the reason why your second



             cout << x.get(GRB_StringAttr_VarName) << " " << x.get(GRB_DoubleAttr_X) << endl;


            works.






            share|improve this answer




























              0














              Gurobi has a lazy update approach. After you create your variables, you need to run model.update() to write the changes to your model. Only after that you can use the methods of a variable object:



              #include "gurobi_c++.h"
              using namespace std;

              int main(int argc, char *argv){
              GRBEnv env = GRBEnv();

              GRBModel model = GRBModel(env);

              // Create variables

              GRBVar x = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "x");
              GRBVar y = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "y");
              GRBVar z = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "z");
              model.update();

              // Set objective: maximize x + y + 2 z
              cout << x.get(GRB_StringAttr_VarName) << " " << endl;

              model.setObjective(x + y + 2 * z, GRB_MAXIMIZE);
              // Add constraint: x + 2 y + 3 z <= 4
              model.addConstr(x + 2 * y + 3 * z <= 4, "c0");
              // Add constraint: x + y >= 1
              model.addConstr(x + y >= 1, "c1");
              // Optimize model
              model.optimize();

              cout << x.get(GRB_StringAttr_VarName) << " " << x.get(GRB_DoubleAttr_X) << endl;
              cout << y.get(GRB_StringAttr_VarName) << " ";
              }


              Note that model.write() and model.optimize() both will call model.update() automatically. That's the reason why your second



               cout << x.get(GRB_StringAttr_VarName) << " " << x.get(GRB_DoubleAttr_X) << endl;


              works.






              share|improve this answer


























                0












                0








                0







                Gurobi has a lazy update approach. After you create your variables, you need to run model.update() to write the changes to your model. Only after that you can use the methods of a variable object:



                #include "gurobi_c++.h"
                using namespace std;

                int main(int argc, char *argv){
                GRBEnv env = GRBEnv();

                GRBModel model = GRBModel(env);

                // Create variables

                GRBVar x = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "x");
                GRBVar y = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "y");
                GRBVar z = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "z");
                model.update();

                // Set objective: maximize x + y + 2 z
                cout << x.get(GRB_StringAttr_VarName) << " " << endl;

                model.setObjective(x + y + 2 * z, GRB_MAXIMIZE);
                // Add constraint: x + 2 y + 3 z <= 4
                model.addConstr(x + 2 * y + 3 * z <= 4, "c0");
                // Add constraint: x + y >= 1
                model.addConstr(x + y >= 1, "c1");
                // Optimize model
                model.optimize();

                cout << x.get(GRB_StringAttr_VarName) << " " << x.get(GRB_DoubleAttr_X) << endl;
                cout << y.get(GRB_StringAttr_VarName) << " ";
                }


                Note that model.write() and model.optimize() both will call model.update() automatically. That's the reason why your second



                 cout << x.get(GRB_StringAttr_VarName) << " " << x.get(GRB_DoubleAttr_X) << endl;


                works.






                share|improve this answer













                Gurobi has a lazy update approach. After you create your variables, you need to run model.update() to write the changes to your model. Only after that you can use the methods of a variable object:



                #include "gurobi_c++.h"
                using namespace std;

                int main(int argc, char *argv){
                GRBEnv env = GRBEnv();

                GRBModel model = GRBModel(env);

                // Create variables

                GRBVar x = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "x");
                GRBVar y = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "y");
                GRBVar z = model.addVar(0.0, 1.0, 0.0, GRB_BINARY, "z");
                model.update();

                // Set objective: maximize x + y + 2 z
                cout << x.get(GRB_StringAttr_VarName) << " " << endl;

                model.setObjective(x + y + 2 * z, GRB_MAXIMIZE);
                // Add constraint: x + 2 y + 3 z <= 4
                model.addConstr(x + 2 * y + 3 * z <= 4, "c0");
                // Add constraint: x + y >= 1
                model.addConstr(x + y >= 1, "c1");
                // Optimize model
                model.optimize();

                cout << x.get(GRB_StringAttr_VarName) << " " << x.get(GRB_DoubleAttr_X) << endl;
                cout << y.get(GRB_StringAttr_VarName) << " ";
                }


                Note that model.write() and model.optimize() both will call model.update() automatically. That's the reason why your second



                 cout << x.get(GRB_StringAttr_VarName) << " " << x.get(GRB_DoubleAttr_X) << endl;


                works.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 27 '18 at 16:53









                jonijoni

                768157




                768157
































                    draft saved

                    draft discarded




















































                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53499037%2fhow-to-access-gurobi-variable-attributes-before-optimizing-model%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

                    Contact image not getting when fetch all contact list from iPhone by CNContact

                    count number of partitions of a set with n elements into k subsets

                    A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks