Main

June 08, 2017, at 11:14 PM by 10.5.113.159 -
Changed line 5 from:
to:
June 08, 2017, at 11:14 PM by 10.5.113.159 -
Changed lines 14-16 from:

BAD_CYCLES is a counter that increments when the application fails to produce a successful solution. When BAD_CYCLES reaches the AUTO_COLD limit, a COLDSTART is initiated. Once a successful solution is found, COLDSTART and BAD_CYCLES are set to zero.

to:

BAD_CYCLES is a counter that increments when the application fails to produce a successful solution. When BAD_CYCLES reaches the AUTO_COLD limit, a COLDSTART is initiated. Once a successful solution is found, COLDSTART and BAD_CYCLES are set to zero.

June 04, 2017, at 05:33 AM by 45.56.3.173 -
Changed line 14 from:

BAD_CYCLES is a counter that increments when the application fails to produce a successful solution. When BAD_CYCLES reaches the AUTOCOLD limit, a COLDSTART is initiated. Once a successful solution is found, COLDSTART and BAD_CYCLES are set to zero.

to:

BAD_CYCLES is a counter that increments when the application fails to produce a successful solution. When BAD_CYCLES reaches the AUTO_COLD limit, a COLDSTART is initiated. Once a successful solution is found, COLDSTART and BAD_CYCLES are set to zero.

June 04, 2017, at 05:33 AM by 45.56.3.173 -

(:title APM.BAD_CYCLES - APMonitor Option:) (:keywords APM.BAD_CYCLES, Optimization, Estimation, Option, Configure, Default, Description:) (:description Automatically cold start model after this specified number of bad cycles:)

 Type: Integer, Input/Output
Default Value: 0
Description: Counter on number of bad cycles
0  = initial value
1+ = number of consecutive unsuccessful
solution attempts


BAD_CYCLES is a counter that increments when the application fails to produce a successful solution. When BAD_CYCLES reaches the AUTOCOLD limit, a COLDSTART is initiated. Once a successful solution is found, COLDSTART and BAD_CYCLES are set to zero.