-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Continuize: multiple attributes with the same name #6877
Comments
ZanMervic
added
the
bug report
Bug is reported by user, not yet confirmed by the core team
label
Aug 21, 2024
2 tasks
Code may assume that values of categorical variables are unique. The bug is thus in discretization. Adding I nevertheless made #6878 to prevent construction of variables with duplicated values, so any future bugs that result in duplicated values will be reported earlier, at the appropriate place. |
janezd
removed
the
bug report
Bug is reported by user, not yet confirmed by the core team
label
Aug 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What's wrong?
This issue is related to the issue with Discretization #6876.
If the input to the Continuize widget has attributes with multiple values with the same "name"/"value" (see Issue #6876 for a better explanation), the One-hot encoding will create multiple attributes with the same name which results in an exception.
Workflow I used (an extension of the workflow from issue #6876):
Exception:
Screenshot of the raised exception and the two attributes with the same name:
Note
Because of this issue, a test was failing for the ScoringSheet widget. I have temporarily excluded the widget from the test, but it should be included again when the issue is resolved.
Test:
Orange.tests.test_classification.LearnerAccessibility.test_all_models_work_after_unpickling_pca
How can we reproduce the problem?
Zip of the workflow: continuize_bug.zip
To reproduce the problem, set the PCA components to 8 in the provided workflow.
What's your environment?
The text was updated successfully, but these errors were encountered: