Skip to content

Fix parameter path syntax for non-scale parameters#2

Draft
anth-volk wants to merge 4 commits intomainfrom
feature/initial-implementation
Draft

Fix parameter path syntax for non-scale parameters#2
anth-volk wants to merge 4 commits intomainfrom
feature/initial-implementation

Conversation

@anth-volk
Copy link
Contributor

Fixes #1

Summary

  • Fix bracket notation to dot notation for regular parameter nodes
  • gov.irs.income.bracket.rates[1]rates.1
  • ctc.phase_out.threshold[SINGLE]threshold.SINGLE
  • va.tax.income.deductions.standard[SINGLE]standard.SINGLE

Bracket syntax is only valid for ParameterScale objects (YAML with brackets: key). Regular parameter nodes use dot access.

Test plan

  • Household simulation returns results without ValueError
  • All reform parameters apply correctly (bracket rates, CTC, EITC, VA deduction)

🤖 Generated with Claude Code

anth-volk and others added 4 commits March 11, 2026 20:44
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Virginia tax and benefit reform calculator with household and statewide
impact analysis for CTC, EITC, and income tax rate reforms at federal
and state levels.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Fix federal bracket rates to use 1-indexed keys (range(1,8)) matching YAML
- Add .amount sub-key to EITC max bracket scale paths
- Add .rate sub-key to VA income tax rate bracket scale paths
- Add postcss.config.mjs with @tailwindcss/postcss plugin (required for Tailwind v4)
- Add @tailwindcss/postcss and postcss as devDependencies

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
PolicyEngine parameter nodes (income bracket rates, CTC phase-out
thresholds, VA standard deduction) use dot notation (rates.1,
threshold.SINGLE), not bracket notation (rates[1], threshold[SINGLE]).
Bracket syntax is only for ParameterScale objects.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix parameter path syntax in simulation backend

1 participant