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

Returns on each row do not sum up to total #214

Closed
Amy-Xu opened this issue Mar 28, 2016 · 11 comments · Fixed by PSLmodels/Tax-Calculator#1889
Closed

Returns on each row do not sum up to total #214

Amy-Xu opened this issue Mar 28, 2016 · 11 comments · Fixed by PSLmodels/Tax-Calculator#1889
Assignees

Comments

@Amy-Xu
Copy link
Contributor

Amy-Xu commented Mar 28, 2016

http://www.ospc.org/taxbrain/2231/

The first and second column results (returns & AGI) do not sum up to their totals. It seems like for all the tables by expended income bins, we're missing the negative expanded income row. Under current law, we have about 4.9 billion returns in the lower than zero bin.

The count column in this table can be used as a reference:
screen shot 2016-03-28 at 2 57 58 pm

@talumbau
Copy link
Member

@Amy-Xu, dropping the negative expanded income is intentional, but I see that is is confusing that the sum of what is displayed doesn't add up to the total at the bottom. I see two possibilities for a fix:

  1. put a row for negative expanded income
  2. do the summing on what is displayed so the totals match up

do you have an idea on which is the correct one to do? option 2 is much easier for me, so I'm hoping option 2 is good. cc @MattHJensen

@Amy-Xu
Copy link
Contributor Author

Amy-Xu commented Apr 13, 2016

@talumbau Could you remind me why we intentionally dropped the negatives? I want to talk to the researcher who found this issue and see how necessary it is to add the negatives row. Will get back to you soon.

@talumbau
Copy link
Member

hmm.. @MattHJensen would probably have the best answer. My recollection is that when we first did the grouping by income bins, we defined all the bin end points. We defined 0 as the minimum for the lowest bin. This left some records without a bin, so there was a decision to drop them. I don't know of a deeper explanation than that.

@Amy-Xu
Copy link
Contributor Author

Amy-Xu commented Apr 13, 2016

Matt said we should follow how other institutions deal with this issue. An example I found here seems to say what we're doing currently is totally acceptable, but we just need a note like (2) in that example so users won't be confused why all rows do not sum up to the totals. cc @MattHJensen

Is it difficult to add notes like that? @talumbau

@talumbau
Copy link
Member

It wouldn't be too difficult to add as long as it was just some kind of "static" note that appeared at the bottom of the page. So, something in this area:

screen shot 2016-04-13 at 2 11 27 pm

that went underneath the Source link. If that is a good place for the note on the results page and you have some agreed upon text to add, let me know and I can add it. If the note text would be more intricately placed on the results page (some kind of hover over or dynamically appearing based on certain tables) I will still take the text but will need to work with @mistakevin to get it on the page.

@talumbau
Copy link
Member

@Amy-Xu if this issue is still relevant, can you create the note and add to an existing flatblock (or have @MattHJensen do that part), or close if this issue is no longer relevant?

@Amy-Xu
Copy link
Contributor Author

Amy-Xu commented Oct 10, 2016

Not quite sure whether we still need this note. I don't think we have it yet: the note saying total number of returns does not match the sum of all cells. Do we still need it?@MattHJensen

@MattHJensen
Copy link
Contributor

I believe that some additional documentation here would be valuable, in line w Amy's suggestion. Leaving this open.

@hdoupe
Copy link
Collaborator

hdoupe commented Jan 31, 2018

@Amy-Xu do you have a note in mind that we could use?

What do you think about saying: "The totals include the negative expanded income bin which is not shown in the table."

@Amy-Xu
Copy link
Contributor Author

Amy-Xu commented Jan 31, 2018

Depending on the row label. If the label is $0-10K (or something like that), that sounds good. If the row label says 'less than 10k', then probably modify the last part to 'which is excluded from the lowest income bin'. Your judgement call.

@martinholmer
Copy link
Contributor

TaxBrain Issue #214 has been resolved by Tax-Calculator pull request 1889.

In order to use the corrected row label (which, following Amy's suggestion, is now $0-10K rather than <$10K) TaxBrain code will have to be changed so that the WEBBIN_ROW_NAMES list is imported from taxcalc.tbi (rather than from taxcalc.utils).

@Amy-Xu @hdoupe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants