You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating a histogram of a variable that only contains 1 unique value, the axis of that histogram gets labeled with that value multiple times, but this histogram remains empty because there are no well defined bins to put the data in. To make matters worse, when creating this histogram, all other histograms in the same screen are flushed and get emptied as well. Removing the newly created histogram solves the issue.
Although it is clear to me that this has to do with the min/max values of the variable that is being plotted, it took me some time (and help) to realize this. Is there a way to solve this in an automated fashion? I bet that if i have trouble finding the source of this problem, a generic user would have this problem as well.
The text was updated successfully, but these errors were encountered:
I cannot reproduce it on current dev branch. Can you give a bit more detail?
version you are using, sql or crossfilter backend, facet type that has only one value?
The version I am using is version 0.1.0 and the facet that I am using is the M3 facet in the ewkinos dataset that is added on the Spot instance installed on http://54.93.247.80/. I don't know how I check which backend is running.
When generating a histogram of a variable that only contains 1 unique value, the axis of that histogram gets labeled with that value multiple times, but this histogram remains empty because there are no well defined bins to put the data in. To make matters worse, when creating this histogram, all other histograms in the same screen are flushed and get emptied as well. Removing the newly created histogram solves the issue.
Although it is clear to me that this has to do with the min/max values of the variable that is being plotted, it took me some time (and help) to realize this. Is there a way to solve this in an automated fashion? I bet that if i have trouble finding the source of this problem, a generic user would have this problem as well.
The text was updated successfully, but these errors were encountered: