APM.BAD_CYCLES - APMonitor Option
Main.OptionApmBadCycles History
Show minor edits - Show changes to markup
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.
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.
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.
(: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.