Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alter uprating functionality to prevent the need to manually declare each uprated variable in data/datasets/cps/cps.py #169

Open
anth-volk opened this issue Mar 1, 2024 · 0 comments

Comments

@anth-volk
Copy link
Contributor

At present, in order to successfully allow a value to be uprated, it must be defined as something (at minimum, a zeroed-out array) within data/datasets/cps/cps.py; otherwise, it's returned as a series of NaNs, breaking any derivative formulas in the process. This came up recently with uprating applied to social security within policyengine-us, whereby social_security_retirement had been defined, and thus evaluated correctly, but social_security_survivors was not, and thus NaNed out.

Could also be valuable to add a ValueError throw at the same time to ensure that we can adequately trace these in the future, if necessary.

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

No branches or pull requests

1 participant