Controller Reset State Residual Tool

Description

Apply supplied state resets and return target residuals.

Controller calculations combine state, gain, error and reset conventions. A one-step update or output-balance target describes one part of a controller and does not implement, tune or establish the stability of a complete plant-control loop.

Apply supplied state resets and return target residuals.

When to use this tool

Use Controller Reset State Residual when checking one explicit controller-state or term update.

How to use the tool and how it works

Enter stateBefore, suppliedReset, desiredState, resetIsIncrement. Keep parallel arrays aligned. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read stateAfter, residual. Use the output convention below.

Apply supplied state resets and return target residuals. Require aligned arrays; resetIsIncrement adds each reset to prior state, otherwise replaces it; residual = stateAfter-desiredState.^[1]

Input field	Meaning and units	Accepted input
stateBefore	State Before	Required. Array of finite number; maximum items 256.
suppliedReset	Supplied Reset	Required. Array of finite number; maximum items 256.
desiredState	Desired State	Required. Array of finite number; maximum items 256.
resetIsIncrement	Reset Is Increment	Required. Boolean.

Output field	Interpretation	Returned shape
stateAfter	State After	Required. Array of finite number; maximum items 256.
residual	Signed difference in the direction defined above, using the same units as its compared quantities.	Required. Array of finite number; maximum items 256.

json

{
  "input": {
    "stateBefore": [
      1,
      2
    ],
    "suppliedReset": [
      2,
      -1
    ],
    "desiredState": [
      3,
      0
    ],
    "resetIsIncrement": true
  },
  "output": {
    "stateAfter": [
      3,
      1
    ],
    "residual": [
      0,
      1
    ]
  }
}

Limitations and assumptions

No actual controller state is changed and reset adequacy or safe transition is not assessed.
Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use the full controller and plant model, numerical implementation and qualified verification for actual operation or transitions.

References

Calculation and input contract: cybernetics/controller-reset-state-residual — tool.io

Similar or alternative tools

Controller Reset Bias Gap
Return the bias needed to preserve a supplied controller output.
Controller Bumpless Transfer Integral Offset
Return the integral term needed for a supplied bumpless output balance.