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

bug: edge case for histogram #2221

Closed
lixun910 opened this issue Sep 26, 2020 · 0 comments
Closed

bug: edge case for histogram #2221

lixun910 opened this issue Sep 26, 2020 · 0 comments

Comments

@lixun910
Copy link
Member

using the NYC data, I created a custom break with six categories for kids2000. That’s illustrated in the updated mapping chapter. When I use this category in a histogram for kids2000, all is well. However, when I use
it in a histogram for kids2009, it gives a very weird result on the axes and the statistics.
As it happens, kids2009 does not have any observations over 50, which is the highest
breakpoint in custom1, the custom category. The histogram drawing code doesn’t seem
to know how to deal with that. See also, the strange values for the range in the last bin
in the statistics part, going from 50 to 48.1!

edge_case

lixun910 added a commit to lixun910/geoda that referenced this issue Sep 26, 2020
lixun910 added a commit to lixun910/geoda that referenced this issue Sep 26, 2020
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