Relax parameter value warning logic when min or max value is "default" #1578
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 fixes a bug that was revealed in the discussion of PolicyBrain issue 638 beginning with this recent comment. That discussion describes the bug, which arises only when a TaxBrain user implements a reform before 2017 using either the
_STD
and_STD_Dep
parameters.This Tax-Calculator "bug" is caused by the fact that TaxBrain does not allow users to specify the value of either of these two parameters for widow filing units, and then makes a poor guess about what the TaxBrain user would want the reformed widow value to be. TaxBrain's guessing is poor because it guesses that the user wants to leave the widow value unchanged even though the user is changing the parameter values for other filing unit types. A much better guess would be to set the widow value to the joint value, which is the case in most filing-unit-indexed parameters under current-law. There are only a few cases where the widow value is not equal to the joint value, and in all of those case, the widow value is equal to the single value under current law.
Another pull request could add for the 49 filing-unit-indexed parameters in the
current_law_policy.json
file a new field that would look like this in most cases:and look like this in the other cases:
This additional information would allow TaxBrain to make a much better guess than it is now making about what value a TaxBrain user wants for widows.
Of course, the most logical approach would be to add widow boxes to the TaxBrain input GUI so that users could actually specify what parameter value widows should have. And this approach would actually simplify both TaxBrain and Tax-Calculator logic, in comparison to the making-a-better-guess approach outlined above.
@MattHJensen @feenberg @Amy-Xu @andersonfrailey @hdoupe @GoFroggyRun