🕹️ Controllers
This section is the registry of controller policies used by 🚂ENABOL experiments. Controllers modify the update magnitude, feasibility, or safety behavior after the optimizer proposes a raw update.
Optimizer vs Controller
The optimizer computes a raw update direction:
The controller modifies that update before it is applied:
For global-throttle controllers:
This preserves the raw optimizer direction before fixed-point quantization effects.
Controller Table
| Controller ID | Name | Dynamics | Quantization-aware | Direction-preserving | Status |
|---|---|---|---|---|---|---|
| CTRL-NONE | No controller | none | no | yes | Valid |
| CTRL-GT-ORDER-0 | Algebraic global throttle | order 0 | no | yes | Valid |
| CTRL-GT-ORDER-1 | First-order global throttle | order 1 | no | yes | Planned |
| CTRL-GT-ORDER-2 | Second-order damped global throttle | order 2 | no | yes | Planned |
| CTRL-GT-ORDER-2-QA | Quantization-aware second-order global throttle | order 2 | yes | yes | Planned |
ID Convention
Use:
CTRL-<FAMILY>-<DYNAMICS>[-<FEATURE>]
Examples:
CTRL-NONE
CTRL-GT-ORDER-0
CTRL-BINARY-THROTTLE
CTRL-GT-ORDER-1
CTRL-GT-ORDER-2
CTRL-GT-ORDER-2-QA
ORDER-0 means zero controller state, not zeroth-order gradient-free optimization.
Controller Record Checklist
Each controller page should define:
- ID and short name,
- inputs,
- outputs,
- state variables,
- update equations,
- required diagnostics,
- expected behavior,
- known failure modes,
- implementation status.