CALLBACKCHECKTIMEWORKDELAY
Description
|
Minimum delay in work units between two consecutive executions of the CHECKTIME callback in the same solution process
|
||||
Type
|
Double
|
||||
Topic areas
|
|||||
Values
|
|
||||
Default value
|
0
|
||||
Note
|
The CHECKTIME callback may be invoked very often and can lead to an overhead. This control enables users to specify a minimum delay between two consecutive calls, such that the overhead becomes controllable. Note that WORK is accumulated deterministically during the search in contrast to TIME. Therefore, the callback invocation sequence with a positive CALLBACKCHECKTIMEWORKDELAY is reproducible across multiple invocations of the same search (same user controls, same problem) even on different machines. Note that the internal counter is reset at every invocation of a solution process via XPRSlpoptimize, XPRSmipoptimize, etc. |
||||
Note
|
The disadvantage of setting a delay in work units is that work increases less uniformly than time.
|
||||
Note
|
While the related control
CALLBACKCHECKTIMEDELAY specifies a delay in milliseconds, this double control allows delay specification of an arbitrary fraction of a work unit.
|
||||
Affects routines
|
|||||
See also
|
|||||
Category
|
Control
|
© 2001-2025 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.