Thank you very much to both of you for answering me.
I will consider this extra time on the jobs I'm running then.
Taking the opportunity :D
If I use staticlex to solve multiobjective problems, it seems that WML is not considering the TimeLimit, but trying to solve until it finds the optimal solution.
An example, the start of the job:
[2020-10-07T01:02:23Z, INFO] ! -------------------------------------------------- CP Optimizer 12.10.0.0 --
[2020-10-07T01:02:23Z, INFO] ! Maximization problem - 4,818 variables, 22,833 constraints
[2020-10-07T01:02:23Z, INFO] ! Presolve : 8,758 extractables eliminated
[2020-10-07T01:02:23Z, INFO] ! TimeLimit = 300[2020-10-07T01:02:23Z, INFO] ! Workers = 1
[2020-10-07T01:02:23Z, INFO] ! Initial process time : 1.41s (1.41s extraction + 0.00s propagation)
[2020-10-07T01:02:23Z, INFO] ! . Log search space : 10,389.8 (before), 10,389.8 (after)
[2020-10-07T01:02:23Z, INFO] ! . Memory usage : 13.9 MB (before), 13.9 MB (after)
[2020-10-07T01:02:23Z, INFO] ! Using sequential search.
[2020-10-07T01:02:23Z, INFO] ! ----------------------------------------------------------------------------
36 minutes later :
[2020-10-07T01:38:23Z, INFO] 1832.500 2,608k 3 F !presenceOf(_itv1,965)
[2020-10-07T01:38:23Z, INFO] * 1832.500 2,608k 131.21s (gap is 0.64% @ crit. 1 of 4)
[2020-10-07T01:38:23Z, INFO] New objective is 1832.500; -7,994; 0; 2.675705e+12
then I cancel the job
Am I doing something wrong? It works perfectly before WML.
Thanks for your support.
------------------------------
Jorge Rojas Pizarro
------------------------------
Original Message:
Sent: Tue October 06, 2020 09:06 AM
From: Alain Chabrier
Subject: opl configs in WML
Hi Jorge,
as Alex exaplined you should continue to put settings in the beginning of the OPl file.
But we have some issue with
execute {
settings.oaas_processFeasible = 0;
}
which is not fully taken into accoutn in WML.
This is being fixed.
The impact currently is that while not all postprocessing is done on each intermediate solution, some time is spent which shoudl not.
As said, we are fixing this.
Thanks
Alain
------------------------------
Alain Chabrier
------------------------------