-
Notifications
You must be signed in to change notification settings - Fork 62
Pass constraint names to CPLEX #225
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
Comments
Yes, these names should be passed to CPLEX. |
This should be possible as CPLEX API has a function called SetName() for such a purpose. We can have a wrapper for this. |
Hi folks, Thanks @odow and @mlubin for looking at this. I'm wondering this is working properly or if I'm not using it correctly? I have named all the constraints and variables in my model and I can see the names when I write an MPS file using Is there something specific I need to do ? Is it possible to relate the CPLEX name above to the MPS names in any way? |
We pass variables names to CPLEX if they are ASCII: https://github.com/JuliaOpt/CPLEX.jl/blob/5ae4628446470fa0a46438cdfe577155dbcfd54c/src/MOI/MOI_wrapper.jl#L599-L603 So either your variable name is non-ascii, or it has an empty name (i.e., If you can provide a minimal working example (using 2 or 3 variables, not 6000), open a new issue. |
Ahhh...
Maybe some sanitisation to be done... |
So that didn't solve it. Here is a minimum example :
Which outputs
And in the MPS file:
Even if I explicitly use the |
What happens if you use |
Ah, interesting :
|
@blegat, isn't this sufficient to have JuMP copy names to the optimizer? |
The names are not passed to the optimizer, they are only stored in the cache. It's not related to CPLEX |
Hi,
All CPLEX solver messages are reported with generic constraint names e.g. c23474
It makes it very difficult to diagnose infeasibilities and such.
Is there a plan to pass the JuMP constraint names on to CPLEX? It seems possible as in GAMS for example I get more helpful names.
The text was updated successfully, but these errors were encountered: