Decision Optimization

Decision Optimization

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


#Analytics
#DecisionOptimization
#DecisionOptimization
 View Only
  • 1.  long run time before optimization

    Posted 04/03/18 01:21 AM

    Originally posted by: savant_ning


    I  run my model, and get this display, and about 10hours, the display not changed.

    and I use

    c.parameters.read.datacheck.values.off
    

    and

    c.parameters.read.datacheck.values[0].
    

     

    but it's no use for my model, I also got the display the CPXPARAM_Read_DataCheck   1

     

    my model is a MIP, and  73696 variables and about 40GB constraints

    so what should I solve this problem~


    #CPLEXOptimizers
    #DecisionOptimization


  • 2.  Re: long run time before optimization

    Posted 04/03/18 03:07 AM

    A few things:

    • Your output of top shows that two processes are running at 100% CPU load. It may help to not run other CPU intensive processes while trying to solve a model with CPLEX.
    • Can you check whether the code has already started executing the solve() function (just print something before calling solve())?
    • Can you export the model to a SAV file and see if things go any faster with the interactive optimizer?
    • How exactly did you try to disable data checking? From your post it is not clear whether you did things correctly or not.

    #CPLEXOptimizers
    #DecisionOptimization


  • 3.  Re: long run time before optimization

    Posted 04/03/18 04:11 AM

    Originally posted by: savant_ning


    thx,

    the second  thing: I print (problem.feasopt(problem.feasopt.all_constraint()))  before calling solve(),

     and I used 1/problem.set_result_stream(sys.stdout); 2/problem.set_log_stream(sys.stdout) and  3/call back the Timelimitcallback(MIPinfocallback) to set the timelimit = 10800  before calling solve()

     

    the forth thing: I used problem.parameters.read.datacheck.values.off  and

    
    problem.parameters.read.datacheck.values[0]
    

     before calling solve()

    I don't know the usage is correct or not.

     

    I will export the model to SAV, but I need to break the code...and I can export the model next run, when I fix other possible question like the second thing, the forth thing

     

    very thanks
     


    #CPLEXOptimizers
    #DecisionOptimization


  • 4.  Re: long run time before optimization

    Posted 04/03/18 05:12 AM

    Originally posted by: savant_ning


    about the first thing, I used cplex at our server, it's a 56- kernel server, so I think other processes will not affect the cplex solve my model.

    thanks


    #CPLEXOptimizers
    #DecisionOptimization


  • 5.  Re: long run time before optimization

    Posted 04/04/18 02:12 AM

    Originally posted by: savant_ning


    before calling the solve()

    I just used this function, see the attachment..

     

    So, I don't know how to reduce the run time...

     

    should I need export the model.SAV to check it?


    #CPLEXOptimizers
    #DecisionOptimization


  • 6.  Re: long run time before optimization

    Posted 04/06/18 08:12 AM

    This statement

    problem.parameters.read.datacheck.values.off

    just does nothing. Like I said in the other thread you started, the correct way to set the parameter is this

    problem.parameters.read.datacheck.set(problem.parameters.read.datacheck.values.off)

    It seems you are setting all the other parameters correctly (in the commented code), so why do things differently for this parameter?

    As for the running time, I think you got my question wrong. I was wondering whether all this time was burnt before even calling solve(). If you can export a SAV file then I suggest to try solving this SAV file with the interactive and see what is happening. Or attach the SAV file here and we can take a look.


    #CPLEXOptimizers
    #DecisionOptimization