We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
OPL fails at building very large scale models due to the fact that it uses a "row api" of concert : Variables are created and added then to the range constraints.
Unfortunately, such API can become dramatically slow for very large models, and building a model that runs sometimes in a few seconds can take a very long time (sometimes up to several hours !). Why is the concert generated code that fills cplex model not using the column api instead ? This one is known to be much faster and we can see a huge tradeoffs for such large models
Note that this choice is totally transparent for the OPL developer, so there is here no impact of such change for OPL users
Do not place IBM confidential, company confidential, or personal information into any field.