Originally posted by: SystemAdmin

[UDOPS said:]

Has anyone noticed any sensitivity in OPL to repeated runs after model edits? Do you sometimes generate errors even when reverting back to a known good file or commenting out the suspect code? If I am making many experimental changes, sometimes the change does not "take" even though I have saved the model, and I have to run the model twice. Just now, I had to close and restart OPL to clear an error.

I am using a flow control set of models with a main file and "main" program. I also dynamically write a .dat file and pass it to the next model. Is it possible cplex is not discarding all of its objects and memory when the configuration run finishes?
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[UDOPS said:]

Update: I am continuing to see behaviour where a solve might fail, but if I wait a minute and run the model again, without changing anything, the model will solve. Right now, these are really small test models with a handful of variables. When they do solve, the solve code is 1, which I believe means solved in pre-processing?
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[alain.chabrier said:]

Hi,

which OPL version do you refer to ?
Could you share a model reproducing this ?

Thanks,

Alain
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[UDOPS said:]

Note to reader: I am discussing a file sample with Alain offline.

I should also mention that I am working at home, and not on our network license server, so Opl is running in trial license mode. I wonder if this would affect cplex performance?
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[UDOPS said:]

Update: this is a long post, as it includes my whole model code. I did not include the .dat files, they are just odbc database calls. Note that one .dat file is dynamically written to file by the flow control script. I have attached the model codes as 4 file attachments.

I modified my model to repeat the same model continously 100 times. However, it did not complete 100 iterations. It quit in the high 60's with what appears to be an odbc driver memory error (perhaps too much activity in a short time?). The error in OPL Studio (6.0.1) is:

Database error (state=IM003 code=160): Specified driver could not be loaded due to system error  8 (DataDirect 32-BIT SequeLink 5.5).

My model logged each problem replication's outcome. Note how some solver calls are successful, and some are not. The data is NOT changing at each replication. Here is the log:


Iteration 1
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 2
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 3
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 4
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 5
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 6
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 7
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 8
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 9
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 10
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 11
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 12
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 13
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 14
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 15
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 16
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 17
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 18
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 19
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 20
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 21
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 22
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 23
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 24
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 25
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 26
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 27
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 28
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 29
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 30
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 31
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 32
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 33
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 34
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 35
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 36
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 37
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 38
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 39
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 40
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 41
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 42
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 43
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 44
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 45
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 46
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 47
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 48
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 49
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 50
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 51
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 52
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 53
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 54
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 55
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 56
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 57
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 58
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 59
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 60
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 61
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 62
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 0 1417>}

Iteration 63
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 1 1417>}

Iteration 64
Successful feasible network specification, arc count; set dimension:112; 112
Solution obtained: {<1 1.08 1.08 168 134 1 1417>}

Iteration 65
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.

Iteration 66
Successful feasible network specification, arc count; set dimension:112; 112
Master Problem Error: Schedule infeasible! Check data.


#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[UDOPS said:]

Update: I have modified the code to track the actual status code, and it is consistently 11. I do not have a reference to identify this code.
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[UDOPS said:]

Update: I am in the office, and testing this on a faster machine with an active license for OPL 6.0.0. I am still getting frequent cplex status 11's on a continuous run of 100 repetitions.
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[alain.chabrier said:]

Status 11 from CPLEX is :

* Stopped due to a time limit
#define CPX_STAT_ABORT_TIME_LIM          11

aren't you using some time limit somewhere ?
This would clearly explain from run to run, the result can change...


Alain
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[UDOPS said:]

That did it!

In my database, where the time limit is set, I had opted for an empty field to signify no time limit, but I had neglected to create code to respond to that condition. Interesting, when essentially given a time limit of zero, some problems still solved!

I am still looking for a comprehensive reference to these result codes. Can you help me with that?
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[alain.chabrier said:]

You might look for example in the CPLEX callable library reference manual in the part optim.cplex.solutionstatus

You can see :
CPX_STAT_ABORT_TIME_LIM 11 (Simplex or Barrier) enum: AbortTimeLim.

and all others (many)

Alain
#DecisionOptimization
#OPLusingCPLEXOptimizer

Originally posted by: SystemAdmin

[UDOPS said:]

Can you arrange with the powers that be to make this reference available to license holders for OPL Studio? It is not available in the current list of documents.
#DecisionOptimization
#OPLusingCPLEXOptimizer