メインコンテンツへスキップ

Unexpected MIP_SOLCNT value

回答済み

コメント

6件のコメント

  • 正式なコメント
    Simranjit Kaur
    • Gurobi Staff
    This post is more than two years old. Some information may not be up to date. For current information, please check the Gurobi Documentation or Knowledge Base. If you need more help, please create a new post in the community forum, or try Gurobot, our chatbot interface offering instant, expert-level support.
  • Matthias Miltenberger
    • Gurobi Staff

    Hi Lorenzo!

    This is certainly not expected behavior. Could you please share a minimal working example?

    Thanks,
    Matthias

    0
  • Lorenzo Moreschini
    • Gurobi-versary
    • Investigator
    • Conversationalist

    Hi Matthias, I prepared a MWE here:
    https://drive.google.com/file/d/1Nmop5bxuBb9xsKskHhoKEbqpsDj2m9TG/view?usp=sharing

    The link is protected, so when you open it I will receive an access request and I will grant it to you (or anyone from the gurobi.com domain).

    As you can see from the log file I made it on MacOSX 10.13.6 using Gurobi 10.0.0 rc2 and the same behaviour occurred.

    0
  • Matthias Miltenberger
    • Gurobi Staff

    We will handle this in an internal ticket and post the resolution here at a later point in time.

    0
  • Marika Karbstein
    • Gurobi Staff

    Hi Lorenzo,

    If you are in the MIPNODE callback, you also need to call MIPNODE_SOLCNT and not MIP_SOLCNT.
    It should then work.

    Cheers,
    Marika

    0
  • Lorenzo Moreschini
    • Gurobi-versary
    • Investigator
    • Conversationalist

    Thank you all.

    (If I had to make a lucky guess, it seems like the memory area where the MIP_SOLCNT value should be placed is not initialized to 0 at the beginning and, if accessed before the first feasible solution has been found, there is just a random value.)

    0

投稿コメントは受け付けていません。