-
Notifications
You must be signed in to change notification settings - Fork 22
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
Error in training #11
Comments
Thank you for sharing @ayush488 ! The code looks fine at a first glance, but devils might be in the details. Do you have unit-test with some sample input so that we can reproduce the error on our side? Also, could you share more of the Trace of the error. This may or may not related, please make sure you have installed libraries in requirements.txt with correct versions. |
|
Hey @ayush488. Based on the trace, I'm guessing the error is caused by an incorrect data type in one of the inputs. Can you confirm that the user features only have numerical float or integer values? And that there are no missing, NaN, None values? |
sample_train.csv |
the data was categorical data.. It may be having NaN values.. |
Correct, only numeric inputs are supported. |
ok .let me correct. |
so is it more efficient to use numerical features or discretize them and then one hot encode them? |
will it work with categorical features if I remove the null values? |
Yes, numerica data should not have null/nan values by definition, it is a standard data pre-processing step. Glad we found the root cause of the issue --thank you for the help @bkleyn! As far as what is more efficient, that depends on your data, application, have many categories are involved etc. You might also benefit from standardizing your numeric user features so that they are in the same scale. Good luck! |
Thank you. |
you are most welcome! |
I am getting the following error while training;
SystemError: <built-in function _abc_instancecheck> returned a result with an error set
my input as follows:
all user and mailer feature are categorical (not one hot encoded)
What could be the reason?
The text was updated successfully, but these errors were encountered: