-
Notifications
You must be signed in to change notification settings - Fork 11
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
Classifier identified as regressor #39
Comments
Hello @GemmaTuron,
Otherwise, on my end, the task is correctly identified if the input file contains classification data.
|
Hi @HellenNamulinda |
@GemmaTuron what is the column name of your file? |
|
Thanks. This is surprising and is probably a bug. |
@GemmaTuron |
Hi @GemmaTuron and @miquelduranfrigola,
But for the fit command, if the cut-off value isn’t specified, the first task assigned in During the If the cut-off is specified( say So, before the |
Thanks @HellenNamulinda |
This issue persists, and I have a dataset only with classification data, which I cannot use as I get stuck while ZairaChem tries to do a regression:
@HellenNamulinda what do you mean by that: During the setup step where data preparation is performed, this file will get updated, After all the checks and standardization(once this is logged Descriptor calculation and LSH folding done), the right task is assigned and the parameters.json is updated. Did you successfully pass a classification data (already binarised) and ZairaChem trained a model? |
mmmm I've been doing tests |
It works just fine on my end. |
Describe the bug
If a binary classification file is passed, with the activity column already in binary, and the following command is run:
zairachem fit -i input.csv -m model_folder
ZairaChem interprets it as a regression, not a binary classification, as indicated by the
data/parameters.json
file:Desktop (please complete the following information):
Ubuntu 22.04 LTS
Additional context
this can be confusing so we need to add clear instructions
The text was updated successfully, but these errors were encountered: