This section describes utility routines in the CONOPT DLL.
These methods are called to start the solver and retrieve information about the solver.
◆ solve()
| conopt.Conopt.solve |
( |
| self | ) |
|
method for starting the solving process of CONOPT.
Definition at line 1402 of file conopt.py.
◆ controlVector()
| conopt.Conopt.controlVector |
( |
| self | ) |
|
returns the control vector pointer.
This is for use in the C-interface methods
Definition at line 1415 of file conopt.py.
◆ printStatus()
| conopt.Conopt.printStatus |
( |
| self | ) |
|
prints the status of the optimisation
Definition at line 1426 of file conopt.py.
◆ getName()
| conopt.Conopt.getName |
( |
| self | ) |
|
returns the model name
Definition at line 1435 of file conopt.py.
◆ version()
| conopt.Conopt.version |
( |
| ) |
|
|
static |
returns the version number.
It can be used to ensure that the modeler is linked to the correct version of the CONOPT DLL.
Definition at line 1607 of file conopt.py.
◆ getMaxThreads()
| conopt.Conopt.getMaxThreads |
( |
| self | ) |
|
returns the maximum number of threads that can be used by CONOPT.
If you are using multiple threads it may be necessary to know in advance how many threads CONOPT can use. If called inside a parallel loop, this method will return one—indicating that CONOPT cannot use multiple threads when CONOPT itself is called in parallel. Therefore, this method should be called in some sequential initialization code and not inside a function evaluation routine, that could be called in parallel.
Definition at line 1789 of file conopt.py.
◆ getMaxHeapUsed()
| conopt.Conopt.getMaxHeapUsed |
( |
| self | ) |
|
After a model has been solved this method will return the amount of heap memory used.
Definition at line 1803 of file conopt.py.
◆ getRangeErrors()
| conopt.Conopt.getRangeErrors |
( |
| self | ) |
|
returns the range errors that were encountered.
Definition at line 1812 of file conopt.py.
1.13.2