Decision Optimization

Decision Optimization

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


#Analytics
#DecisionOptimization
#DecisionOptimization
 View Only
  • 1.  IloEnv unique identifier

    Posted 05/24/16 02:35 AM

    Originally posted by: ZoharFeldman


    Hi,

     

    I have some internal classes that I store with respect to a particilar IloEnv. I may have several IloEnv's, so I actually have a map between the IloEnv and the list of classes.

    In particular, I use the impl pointer (iloEnv->getImpl()) as the key of this map.

    This seems to create a problem when running the refineConflict method (I guess conflict refiner builds a different env?).

    If this is true, does IloEnv have some unique identifier that is carried to the IloEnv used by the conflict refiner?

     

    Thanks,

    Zohar 


    #CPOptimizer
    #DecisionOptimization


  • 2.  Re: IloEnv unique identifier

    Posted 05/24/16 05:28 AM

    Originally posted by: PhilippeLaborie


    Hi Zohar,

    The conflict refiner may indeed create some IloEnv for managing its own memory but this should be completely transparent to the user. In general you have no way to access this IloEnv so I do not understand how it can interfere with your map between "your" IloEnvs and "your" classes. I'm probably missing something.

    Philippe

     


    #CPOptimizer
    #DecisionOptimization


  • 3.  Re: IloEnv unique identifier

    Posted 05/24/16 09:56 AM

    Originally posted by: ZoharFeldman


    Thanks for your reply, Philippe.

     

    This map is global and is populated during model construction.

    More crucially to my story is the fact that it is accessed during extraction of some custom constraint, and during conflict refiner it is queried with a different iloEnvI (extracted from IloCP) than during the model construction. 

    I realize that the use of  global map is not an ideal practice in terms of software engineering, but this is kind of legacy that I prefer not to touch unless necessary.

     

    Thanks,

    Zohar


    #CPOptimizer
    #DecisionOptimization