Add eCPS difficulty_* disability export columns (final Gate-1 gap)#135
Merged
Conversation
Re-measuring Gate-1 coverage after the seven gap-fill PRs surfaced six contract-required columns no PR had built: difficulty_seeing, difficulty_hearing, difficulty_walking_or_climbing_stairs, difficulty_dressing_or_bathing, difficulty_doing_errands, difficulty_remembering_or_making_decisions. They were missed because the original 47-column gap report ran against the first, under-specified contract that had dropped them; PR #120 re-added them to the contract but the imputation lane plan was never regenerated. These are eCPS final-H5 contract columns present in the newest eCPS builds (policyengine-us-data PR #1151 and the clone-correct baseline) and absent only from the older published HF baseline. They recode from the ASEC PEDIS* fields (PEDIS{X} == 1 -> True; verified difficulty_seeing is byte-identical to is_blind, both PEDISEYE == 1, in the PR #1151 eCPS export). They are not PolicyEngine-US variables, so they export as person-level dataset columns via the legacy-contract entity map (the scf_* pattern). Microplex already ingested the six PEDIS* fields into _disability_* staging columns (used to compute is_disabled); this produces the difficulty_* leaves from that staging before it is dropped, and wires the SAFE export set, the export defaults (False), and the legacy-entity map. Static config coverage is now 246/246 contract-required columns. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add eCPS difficulty_* disability export columns (final Gate-1 gap)
Re-measuring Gate-1 coverage after the seven gap-fill PRs surfaced six
contract-required columns no PR had built: difficulty_seeing, difficulty_hearing,
difficulty_walking_or_climbing_stairs, difficulty_dressing_or_bathing,
difficulty_doing_errands, difficulty_remembering_or_making_decisions. They were
missed because the original 47-column gap report ran against the first,
under-specified contract that had dropped them; PR #120 re-added them to the
contract but the imputation lane plan was never regenerated.
These are eCPS final-H5 contract columns present in the newest eCPS builds
(policyengine-us-data PR #1151 and the clone-correct baseline) and absent only
from the older published HF baseline. They recode from the ASEC PEDIS* fields
(PEDIS{X} == 1 -> True; verified difficulty_seeing is byte-identical to is_blind,
both PEDISEYE == 1, in the PR #1151 eCPS export). They are not PolicyEngine-US
variables, so they export as person-level dataset columns via the
legacy-contract entity map (the scf_* pattern).
Microplex already ingested the six PEDIS* fields into disability* staging
columns (used to compute is_disabled); this produces the difficulty_* leaves
from that staging before it is dropped, and wires the SAFE export set, the
export defaults (False), and the legacy-entity map. Static config coverage is
now 246/246 contract-required columns.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com