gnopik
gnopik
NaNs in bins - what do you mean, like this?  This is the way to communicate that we want particular boundaries between states (==bins), and this case, just for...
> For the NaNs I don't remember why we have them, need to check as well. Easier to discuss over a call.
Yes, sounds excellent.
Yes, I'm getting the same experience
Yep, sounds like a good idea.
Some are already ok after the categorical fix, but some are still wrong: hype.csv - first two variables are outputs, no NaNs [hype.csv](https://github.com/user-attachments/files/16904187/hype.csv) # How the dashboard shows it ...
Another example where the dashboard defines states for the categorical variable wrong, misclassifying portions of data resulting in NaN scenarios (but no NaNs in the data). [converting [1 2 3...
[data.csv](https://github.com/user-attachments/files/17867263/data.csv) Another example, where the most influential categorical variable with five unique values gets misclassified into 4 states, the 5th remaining empty.
can't it just check min and max values of the output and scale the graph accordingly when data is loaded first time?
If automatic re-initialization is too hard to get, how about another button "Reset" there?