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

fix integer bins closed left #40

Merged
merged 2 commits into from
Mar 18, 2024
Merged

fix integer bins closed left #40

merged 2 commits into from
Mar 18, 2024

Conversation

d-callan
Copy link
Member

extends #37 to work for bins closed left as well


test_that("cut_width splits the last inclusive bin for integers where bin width is 1", {
ints <- c(0,1,2,2,3,3,3,4,4,4,4)
expectedBins <- c("[0,1)","[1,2)","[2,3)","[2,3)","[3,4)","[3,4)","[3,4)","[4,5]","[4,5]","[4,5]","[4,5]")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since they're integers, can we have the last bin simply say "[4, 5)"? It makes sense that the last bin end is 5, but we know we added "5" to make the bin.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thats default behavior of cut, for good reasons, and im not inclined to digging into that.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you explain what the reasons are? It doesn't make sense to me.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for every other case, except the one where we have integers or dates w one value per bin, then either the first or last bin needs to be inclusive on both sides. and in fairness, bins w one discrete value per bin, arent really bins at all. i think what cut does is perfectly reasonable, for the vast majority of cases, and trying to run our own impl of a base r fxn feels like a bad idea.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

id rather contribute to base r for this edge case, and get the fix a year from now when it finally works its way through, than run our own impl of cut for that label.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i did not mean to suggest we make our own version of cut or anything, i just didn't understand why having bins like "[4, 5]" were a good idea

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not necessarily arguing they're a good idea, so much as they're not worth the effort to change. They're not very likely to actually confuse anyone, may not even be actually seen by anyone, but do cost me time to change, don't have a super clean way to change and do risk introducing bugs elsewhere by changing. I'd rather just keep relying on cut as-is to do its thing.

@d-callan d-callan merged commit 4f2e488 into main Mar 18, 2024
5 checks passed
@d-callan d-callan deleted the bins-closed-left branch March 18, 2024 16:33
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

Successfully merging this pull request may close these issues.

2 participants