-
Notifications
You must be signed in to change notification settings - Fork 346
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
How to disable mutual exclusivity? #15
Comments
Hi, yes, it's would not be enabled as long as you don't use --subtyping. |
Thank you for your answer!
Does it mean the --subtyping flag must be used? However, in line 95:
We can see |
Hi, sorry for the confusion, first of all: the assertion statement is just for my own book-keeping i.e. i wanted to use subtyping for that specific task I defined and wanted to make sure that when I was training with that task, i would not forget to enable it. So no, you do not have to use the subtyping flag for any specific task depending on your needs. second of all: 'clam' is just something i forgot to update in the code ('clam_sb' and 'clam_mb' used to be a single option called 'clam') - i will correct that shortly, thanks for pointing out. |
Thank you so much for your detailed explanation!! |
Remove reference to model_type 'clam', which is no longer functional, as explained in mahmoodlab#15.
Remove reference to model_type 'clam', which is no longer functional, as explained in mahmoodlab#15.
Hi, I am trying to apply CLAM to a multi-class problem. For my data, the label classes are more like predicting cancer grades. Is it possible to remove the mutual exclusivity? Thank you!
The text was updated successfully, but these errors were encountered: