Closed onyb closed 5 years ago
The user is shown a spinner during loading of the point data table. This is useful especially when the point data table is huge. Screenshot below:
Below is screenshot of how the user inputs the bins for FER / FE.
In case of FER, the value for bins is auto-filled with what you see in the screenshot. These values are editable, and the color coding for the histogram bars are adjusted accordingly (green for negative bins, white for the bin crossing origin, yellow for the 5 bins after the white bin, and red for the rest).
In case of FE, the user starts with a blank field. The color coding (blue, white, red) is adjusted according to the bins input by the user.
We're also displaying some stats about the point data table to help the user come up with meaningful bin values.
Leaf nodes in the decision tree are now color coded with a gradient of R-G-B from top to bottom, automatically adjusted depending upon the number of predictors.
The root node initially has a "black" stroke with "white" fill.
If a user tries to load a huge breakpoints CSV file, the generation and rendering of the decision tree could take several seconds. A dimmer and loader is displayed to prevent the user from triggering additional actions until the rendering is complete. Screenshot below:
User can now enter the number of columns to use while saving the mapping functions as CSV. Screenshot below:
NTH: Nice To Have HP: High Priority MP: Medium Priority LP: Low Priority
cc: @FatimaPillosu
Checklist:
1000
.yLim
value to be an integer and between0
and100
.YYYYMMDD
format.N
for errors.csv file (currently hard-coded to100
).