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
Add “Scoring” box. Shows scoring methods, full name, with checkboxes to decide if the column associated with the scoring method is displayed. Like in Orange2, but plain, with no parameters (always use defaults). Content (classification or regression) based on type of input data set (default, when no data, shows for classification). By default, following methods are checked: Classification: Gain Ratio, Gini Index, Regression: Linear regression, RReliefF (there are no others for now).
Scores should have a full name (shown with the checkboxes) and shorter name (column headers).
Scores should compute when the scoring method is enabled (checked). If the user unchecks a method, keep the scoring method in cache.
Selection of attributes is context dependent (applicable only if attributes are selected manually, not with None, All or Best ranked).
Adding scoring methods to the input of the widget only adds a new scoring column (does not alter the content of the box with checkboxes). These columns are always displayed.
Implement progress bar (with fat data sets, feature scoring takes quite some time).
Consider implementing the score in the background, check how this is done in Test & Score (this feature is optional, but may take substantial time if we postpone it after other issues with this widget are fixed).
Actual behavior
Currently the widget displays scores for all the measures. For classification, there are many, and can be quite confusing for the user. Plus computing them all can take substantial time.
The text was updated successfully, but these errors were encountered:
Orange version
3.3
Expected behavior
Actual behavior
Currently the widget displays scores for all the measures. For classification, there are many, and can be quite confusing for the user. Plus computing them all can take substantial time.
The text was updated successfully, but these errors were encountered: