Skip to content

Bug in verbose information when working with mixed-integer constraint problem #553

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
udicaprio opened this issue Mar 10, 2025 · 3 comments · Fixed by #554
Closed

Bug in verbose information when working with mixed-integer constraint problem #553

udicaprio opened this issue Mar 10, 2025 · 3 comments · Fixed by #554

Comments

@udicaprio
Copy link
Contributor

Hi,

I am working with mixed-integer constrained problem with verbose active. When display information about the iteration, the integer parameters appear with the prefix np.float making impossible to read what is the sample point (see image below for further information.

Image

@till-m
Copy link
Member

till-m commented Mar 12, 2025

Apologies @udicaprio, I somehow missed this.

The conversion to print happens here. I guess, for some reason, calling str on the number doesn't output the actual value (though why it does for the float numbers, I don't know -- the printing should work the same way).

Do you have some short example that reproduces the problem? In e.g. the notebook it doesn't happen.

@udicaprio
Copy link
Contributor Author

Hello @till-m, this happens only when the problem is discrete and constrained. The examples in the notebook do not take into account this scenario.

@till-m
Copy link
Member

till-m commented Mar 13, 2025

Should be fixed, let me know if it still happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants