-
Notifications
You must be signed in to change notification settings - Fork 27
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
Imputed value not missing (Nan) #3
Comments
Hi, |
Are you saying that you are learning through complete data and imputation missing data afterwards? |
Not exactly. The task here is to learn from the incomplete data the values that most likely should fill the gaps in the dataset. After this imputation step, you have a new dataset with the predicted values instead of NaNs or whatever you use as a placeholder. |
How do you evaluate your imputation algorithm? So In my opinion, I have
full dataset then missing value by missingness 10%,20%... then evaluate
classification in them
Vào 20:27, Th 4, 13 thg 1, 2021 Indro Spinelli <[email protected]>
đã viết:
… Not exactly. The task here is to learn from the incomplete data the values
that most likely should fill the gaps in the dataset. After this imputation
step, you have a new dataset with the predicted values instead of NaNs or
whatever you use as a placeholder.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALL7NSYI4ZXNOLLMHECVVZTSZWNVLANCNFSM4SBG3YIA>
.
|
In my opinion, you should generate random missing values with complete data and compare and evaluate them with MSE, RMSE, MAE, etc. |
@Hu-nie But how to evaluate MSE, ...and other matrices? we don't have the missing values, or the ground truth. You are saying this model is filling your missing data and that's it, but how to access the performance measures? |
I run code in examples so I think GINN imputed value not missing (Nan value). Can you explain problems to me?
The text was updated successfully, but these errors were encountered: