30.01.2015 Views

ILOG CPLEX C++ API 9.0 Reference Manual

ILOG CPLEX C++ API 9.0 Reference Manual

ILOG CPLEX C++ API 9.0 Reference Manual

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.

IloCplex::NodeEvaluator<br />

IloCplex::NodeEvaluator<br />

Category<br />

Inner Class<br />

InheritancePath<br />

Definition File<br />

Include Files<br />

ilocplexi.h<br />

ilcplex/ilocplex.h<br />

Constructor Summary<br />

public<br />

NodeEvaluator()<br />

public NodeEvaluator(IloCplex::NodeEvaluatorI *)<br />

public<br />

NodeEvaluator(const NodeEvaluator &)<br />

public<br />

IloCplex::NodeEvaluatorI *<br />

public NodeEvaluator<br />

Method Summary<br />

getImpl()<br />

operator=(const NodeEvaluator &)<br />

Description @proof-read<br />

Node evaluators can be used to control the node selection strategy during goalcontrolled<br />

search, that is, the order in which nodes are processed during branch & cut<br />

search using IloCplex goals. This is the handle class for objects of type<br />

IloCplex::NodeEvaluatorI, which allow you to control the node selection<br />

scheme.<br />

IloCplex::NodeEvaluatorI objects are reference-counted. This means that<br />

every instance of IloCplex::NodeEvaluatorI keeps track of how many handle<br />

objects refer to it. When this number drops to 0, the IloCplex::NodeEvaluatorI<br />

object is automatically deleted. As a consequence, whenever you deal with node<br />

evaluators, you must maintain a handle object rather than just a pointer to the<br />

implementation object. Otherwise, you risk ending up with a pointer to an<br />

implementation object that has already been deleted.<br />

<strong>ILOG</strong> <strong>CPLEX</strong> <strong>C++</strong> <strong>API</strong> <strong>9.0</strong> REFERENCE M ANUAL 192

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

Saved successfully!

Ooh no, something went wrong!