Decision Optimization

Decision Optimization

Delivers prescriptive analytics capabilities and decision intelligence to improve decision-making.

 View Only
  • 1.  Parameter tuning with nondefault cutoff

    Posted Fri June 03, 2016 04:06 PM

    Originally posted by: bcs1g11


    Hi,

     

    Is there any way to supply a cutoff for parameter tuning?

     

    I have tried the setParam method for a single instance of a model but it doesn't seem to work, and it would be better to supply different cutoff values for different instances. 

     

    Thanks for for your time,

     

    Ben


    #CPLEXOptimizers
    #DecisionOptimization


  • 2.  Re: Parameter tuning with nondefault cutoff

    Posted Tue June 07, 2016 12:50 AM

    How exactly did you specify the cutoff for the tuning run?

    It is not possible to specify per-model parameters in a tuning run, so you can only define a cutoff for all models in the run.


    #CPLEXOptimizers
    #DecisionOptimization


  • 3.  Re: Parameter tuning with nondefault cutoff

    Posted Tue June 07, 2016 03:53 AM

    Originally posted by: bcs1g11


    As I stated in the previous post I used the setParam function to set the cutoff. However, the integer solutions found by the tuner exceeded this cutoff and the print out of the parameters did not show any non-default cutoff. 

     

    Thanks,

    Ben


    #CPLEXOptimizers
    #DecisionOptimization


  • 4.  Re: Parameter tuning with nondefault cutoff

    Posted Tue June 07, 2016 06:00 AM

    Sorry, I missed that setParam() stuff.

    If you look at the reference documentation for IloCplex.tuneParam() then you will see that there is an overload that takes as argument the set of parameters that should be fixed during the tuning run. Parameters not in the set will be reset to defaults for tuning. So you have to put the cutoff into this set.


    #CPLEXOptimizers
    #DecisionOptimization