Fed FRB/US, rebuilt
FRB/US
How the Board’s model file is parsed, solved and shocked.
Parse, add-factor, solve by Newton
From the Board's published artefacts to an impulse response. Full derivations are in the working paper.
Parse the Board's model file
The Federal Reserve Board publishes FRB/US whole: the equation system as model.xml, the LONGBASE historical and projection database, the documentation, and a reference Python solver, pyfrbus — all in the public domain.
ParseOne source of truth · Residual form
One source of truth
The parse stage reads model.xml directly.
- It reads variables, equations, per-equation coefficients and the endogenous / exogenous classification for the VAR-expectations ("standard") equation set, the only set this pipeline reads.
- Nothing in the file is re-typed or re-specified: the XML file is the single source of truth for the model's semantics.
- That yields 284 endogenous variables and their equations, with behavioural and identity blocks classified exactly as the Board's file declares them.
Residual form
Each equation is normalised — EViews lag and difference notation rewritten, coefficient references substituted by their published values — flipped to residual form _aerr) and a tracking residual (_trac), so each equation solves
Load LONGBASE, then add-factor
The load stage brings LONGBASE.TXT, the October 2026 vintage, into a pandas frame on a quarterly PeriodIndex. Every simulation is read as a deviation from this baseline.
LONGBASE conditioningTracking residuals (init_trac)
Tracking residuals (init_trac)
init_trac makes the solve reproduce the database identically, for any input.
- It sets each equation's add-factor to minus that equation's residual at the input data.
- It is the Fed's own device, and the direct analogue of the OBR emulator's anchoring.
- That is why a baseline match is not evidence.
- Shocks are imposed on top of the add-factored baseline, where the solver does real work.
Solve by damped Newton
Under VAR expectations every expectations term depends only on current and lagged observables, so the model is simultaneous within each quarter but recursive across quarters.
Newton iterationAnalytic sparse Jacobian · One block, not many
The solver therefore works period by period, starting each quarter from the previous quarter's solution.
Analytic sparse Jacobian
Each quarter, a damped Newton iteration solves the full simultaneous system.
- It uses an analytic sparse Jacobian for every step, differentiated symbolically with sympy and factorised with
scipy.sparse.linalg.splu. - Damping backtracks the step only to stay inside the domain of definition: no logs of non-positive arguments and no NaNs.
- The solver's default tolerances are
, .
One block, not many
- The reference implementation decomposes each period into recursive and simultaneous blocks; this one solves the whole period at once.
- Both approaches solve the same
. - So the two agree to solver tolerance, not to some negotiated threshold.
- See how far to trust it.
Policy rules
Monetary policy is modular: exogenous 0/1 switches in the model file select which rule sets the funds rate.
Policy rulesA modular funds rate · The rule choice is the exercise
A modular funds rate
Three are exposed through frbus_shock: inertial_taylor (the default, the LONGBASE rule and the one the validation numbers use), taylor, and fixed_funds_rate, which holds the funds rate on its baseline path so there is no endogenous monetary offset.
The rule choice is the exercise
The choice is usually the economic point of the exercise: the same government-purchases shock gives a larger output response with the funds rate fixed, and a larger price-level response without the monetary offset. The multipliers under each rule, against published ranges, are on Validation.
Each rule reads its own error term
Each policy rule reads its own add-error. The shock term rffintay_aerr; taylor applies the same reaction bracket without the inertia term and reads rfftay_aerr instead.
Shock and compare
A shock is an addition to an equation's error term (rffintay_aerr for the policy rule, for instance).
Impulse responsesWhat comes out · What stays out of scope
Solve shocked and baseline paths over the same window and read the difference. Units differ by lever, each rule reads its own error term, and a shock held for several quarters stacks: see the three traps.
What comes out
The difference is an impulse response for every one of the 284 variables. The headline 100bp tightening, and how it compares with the Board's documented simulation properties, is the worked shock on Validation.
What stays out of scope
The hosted pipeline runs the VAR-expectations model only.
- The package supports opt-in model-consistent expectations from Python, but no hosted tool exposes them, so forward guidance is out of scope here.
- The reference implementation's
mcontroltrajectory-targeting routine is not implemented. - No bridge links a PolicyEngine reform to model variables; see the known limits.
Notation 11 symbols
| Symbol | Meaning | Step |
|---|---|---|
| residual form of endogenous equation i; the endogenous variables | 1 | |
| additive shock term (add-error) of equation i | 1 | |
| tracking residual of equation i | 1 | |
| the Board's historical and projection database | 2 | |
| Jacobian of the system, Newton step, iteration | 3 | |
| step and residual convergence tolerances | 3 | |
| policy rate from the inertial Taylor rule; equilibrium real rate | 4 | |
| inflation, inflation target, output gap in the rule | 4 | |
| shock term of the policy rule | 4 | |
| effective funds rate, rule rate, floor | 4 | |
| impulse response: simulated minus baseline path | 5 |