Add "Analyzing a Non-Parametric Reform" cookbook recipe #2327
Conversation
This file contains 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
martinholmer
changed the title
Codecov Report
@@ Coverage Diff @@
## master #2327 +/- ##
======================================
Coverage 100% 100%
======================================
Files 12 12
Lines 2703 2703
======================================
Hits 2703 2703Continue to review full report at Codecov.
|
martinholmer
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request adds a Python Cookbook recipe that illustrates how to customize the Calculator class so that it can analyze a non-parametric reform (that is, a reform that cannot be characterized using existing policy parameters). It uses standard object-oriented programming techniques to analyze a reform that is similar to (but not exactly like) the Cost-of-Living Refund proposal to replace the EITC, which was discussed recently in issue #2305.