Repository navigation
Conversation
|
Could you show in the description that the change leaves the US target registry unchanged on a feed built to the packaged scope? Two digests would show it, from the registry compiled at main and at this head on one such feed. The same comparison for the two ACS local-area surface tools would cover the county and district changes. I expect the registries to match, from reading
If the digests differ, Five other open PRs regenerate the same four pin files ( |
|
This one goes after #1676 and re-pins on top of it. Besides the five I listed earlier, these open PRs edit the same four pin files: #1538, #1453, #779, #1085, #1136, #1137, #1156, #1208, #1221, #1275, #1330, #1462, #1564, #1575, #1665 and #1683. If #1610 lands first, please also show the same comparisons on its feed, at Chronicle |
Changes
Compare IRS filing-season measures at the same processing week across tax years, including itemization rates by adjusted gross income. The report records both cutoff dates, the input digest, units, and missing observations. The annual fiscal compiler excludes partial-season controls and lists them in its exclusion receipt. It retains the four existing TY2024 week-47 earned income tax credit series.
Use the latest complete county source year available for each state's control, subject to the target year. Select the annual IRS district file that matches the source boundaries of the supplied crosswalk. The packaged 118th-to-119th Congress crosswalk supports the 2023 file. The previous crosswalk remains available for the 2022 file.
Verification
Built and validated two Chronicle bundles covering weeks 21 and 30 for tax years 2024 and 2025. The combined input contains 7,888 observations. The reproduction guide lists the three input digests and the comparison command. Regression tests cover same-week reporting, partial-season exclusions, historical source fallback, and conservation of district totals.
Candidate annual registries
The experiment includes a small reconstruction recipe for the annual IRS source overlay. It pins the input commits and digests and checks the generated bytes. Under existing target selection and exclusions, the 2025 registry contains 32,381 controls compared with 33,219 in the base. Its 1,484 non-IRS controls match the base. The 2024 candidate has 32,411 controls compared with 33,249 in the base. The additional county surface reconciles 6,286 child controls over 102 state-by-measure blocks.
The experiment compiles target registries without fitting weights or changing the active production pins. The source dependency is Chronicle #444.