Skip to Main Content
IBM Data and AI Ideas Portal for Customers


Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Created by Guest
Created on Oct 23, 2020

Improve constraint priority attachment in OPL

Actually we have to use OPL script to attach a relaxation priority to a constraint. It will be easier to attach this priority at the creation of the constraint. Reason is that a constraint tupleset can easily include a priority field:

tuple rvConstraint{
key int Ctn;
float Value;
int Priority;
};
setof(rvConstraint) relProMin = ...;

If I attach the priority at the generation, code would look like this:

forall ( ctn in relProMin )
ctProMin [ctn]:
varPro[< ctn.Ctn >] <= ctn.Valeur : Priority<-ctn.Priority;

Actually we have to create the constraint in OPL:

forall ( ctn in relProMin )
ctProMin [ctn]:
varPro[< ctn.Ctn >] <= ctn.Valeur

Then we attach a priority using OPL script:

var relProMin=OPDSubModel.relPROmin;
for (ctn in relProMin)
{
relaxIterator.attach(ctProMin[ctn],Opl.maxl(ctn.Priorite,0.1));
}

This may seem easy in OPL Script but when I try to do that with the .NET Interface, it's almost impossible due to the difficulty to manipulate dataElement in .NET. Note also that the feasopt call with the interface is not obvious in OPL script but it is worst with the .NET interface. Maybe a major revamp need to be done to this functionality interface in .NET.