Originally posted by: Hosssein

 

 

 

Hi,

I get this Error from CP optimizer:

Error: IloNum is not integer

 

By debugging, I found out that this error is related to an IloElement Expression in my Objective Function:

 

IloIntVarArray W(env, 5, 0, 9);

PP45= IloNumArray(env, 10);

IloNumExpr OBJECTIVE = IloNumExpr(env,0);

for(i = 0; i < 5; i++)          

{

OBJECTIVE += -IloElement(PP45,W[i]);

}

 

This error happens only when array PP45 contains some fractional values. I also test the following code to build the objective function but got the same error.

for(i = 0; i < 5; i++)          

{

OBJECTIVE += -PP45[W[i]];

}

 

IloElement constraint does not work when PP45 contain float values. Right? Is there any way to handle it?

Thank you

 

 

 

#CPOptimizer
#DecisionOptimization

Originally posted by: GGR

Hi Hossein

 

The first argument in the element expression is the index, that is an integer data. So, The behavior of CPO (in fact concert in this case) is correct.

 

You have to use an IloIntArray or an IloIntVarArray as first argument of the element expression

 

Hope that helps

#CPOptimizer
#DecisionOptimization

Originally posted by: Hosssein

well, what if my data matrix (here PP45) contains float values? Actually this matrix contain pricing values of a column generation method and cannot be replaced by IloIntArray.

#CPOptimizer
#DecisionOptimization

Originally posted by: GGR

Hi Hossein

I think i made a mistake in the IloElement syntax. The first array is the values and the second array is the index. So the first array can contains floating point values (beside the intention is clearly having an numerical objective term). As well the operator [ ] should work. I see in the documentation:

public IloNumExprArg IloElement(IloNumArray a, IloIntExprArg x)

Which version of CPO do you use?

 

Thanks

 

#CPOptimizer
#DecisionOptimization

Originally posted by: Hosssein

It is IBM ILOG CPLEX Optimization Studio V12.3.

#CPOptimizer
#DecisionOptimization

Originally posted by: GGR

Hi Hossein

 

I think floating point element constraint had problem in this and sooner version

I suggest you upgrade your system in the last V12.5 version

 

Hope that helps

 

 

#CPOptimizer
#DecisionOptimization