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.

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

Improve constraint priority attachment in OPL