16.01.2015 Views

GAMS — The Solver Manuals - Available Software

GAMS — The Solver Manuals - Available Software

GAMS — The Solver Manuals - Available Software

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

194 CPLEX 11<br />

Settings of this parallel mode parameter interact with settings of the thread parameter:<br />

threads=0: Cplex uses maximum number of threads (determined by the computing platform and the number<br />

of licensed threads) in deterministic mode unless parallelmode is set to -1 (opportunistic).<br />

threads=1 (default): Cplex runs sequential.<br />

threads> 1: Cplex uses maximum number of threads (determined by the computing platform and the<br />

number of licensed threads) in opportunistic mode unless parallelmode is set to 1 (deterministic).<br />

Here is is list of possible value:<br />

(default = 0)<br />

-1 Enable opportunistic parallel search mode<br />

0 Automatic<br />

1 Enable deterministic parallel search mode<br />

perind (integer)<br />

Perturbation Indicator. If a problem automatically perturbs early in the solution process, consider starting<br />

the solution process with a perturbation by setting perind to 1. Manually perturbing the problem will save<br />

the time of first allowing the optimization to stall before activating the perturbation mechanism, but is<br />

useful only rarely, for extremely degenerate problems.<br />

(default = 0)<br />

0 not automatically perturbed<br />

1 automatically perturbed<br />

perlim (integer)<br />

Perturbation limit. <strong>The</strong> number of stalled iterations before perturbation is invoked. <strong>The</strong> default value of 0<br />

means the number is determined automatically.<br />

(default = 0)<br />

polishtime (real)<br />

This parameter lets you indicate to Cplex how much time in seconds to spend after a normal mixed integer<br />

optimization in polishing a solution. Default is zero, no polishing time.<br />

(default = 0)<br />

populatelim (integer)<br />

Limits the number of solutions generated for the solution pool during each call to the populate procedure.<br />

Populate stops when it has generated PopulateLim solutions. A solution is counted if it is valid for all<br />

filters (see .divflt and consistent with the relative and absolute pool gap parameters (see solnpoolgap and<br />

solnpoolagap), and has not been rejected by the incumbent checking routine (see userincbcall), whether or<br />

not it improves the objective of the model. This parameter does not apply to MIP optimization generally;<br />

it applies only to the populate procedure.<br />

If you are looking for a parameter to control the number of solutions stored in the solution pool, consider<br />

the parameter solnpoolcapacity instead.<br />

Populate will stop before it reaches the limit set by this parameter if it reaches another limit, such as a time<br />

or node limit set by the user.<br />

(default = 20)<br />

ppriind (integer)<br />

Pricing algorithm. Likely to show the biggest impact on performance. Look at overall solution time and the<br />

number of Phase I and total iterations as a guide in selecting alternate pricing algorithms. If you are using<br />

the dual Simplex method use dpriind to select a pricing algorithm. If the number of iterations required to<br />

solve your problem is approximately the same as the number of rows in your problem, then you are doing<br />

well. Iteration counts more than three times greater than the number of rows suggest that improvements<br />

might be possible.<br />

(default = 0)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!