-
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
SVD Imputation - Inexact Error #135
Comments
This is likely because Impute.jl is careful not to change your element type for two reasons:
My guess is that Turing.jl is converting your ints to floats for you. With Impute.jl you just need to be explicit about what you want.
|
Hi @rofinn, thanks for responding! Apologies for the late reply, I somehow completely missed being notified about this. Your explanation makes a lot of sense; I tried it again using floats only and it worked:
I also tried using it on a different amount of data that I originally intended to use this for, and it worked on that without a problem - drawing on what you've said, it might be because all of that information was by default read as floats. Thanks for your help, I'll close this issue. |
Hi all,
Apologies for the bother but I was quite curious about the SVD method provided by this package and decided to try it out on a seemingly harmless dataframe:
Where
:b
is intended to be:a.^2
(the square of:a
). After getting a couple of errors trying to use the raw dataframe, I came across #128 and tried using a matrix-converted dataframe, but interestingly ended up with this error:From what I gleaned from a quick Google-Fu (2 separate links), somewhere in the chain of function calls there maybe isn't a round-off check? I think it might be due to the small size of my test dataframe, but I can't be sure because I also tried using it with
Turing.jl
's Bayesian Linear Regression for imputation purposes and it worked (to some degree of accuracy). Is there anything wrong here or have I overlooked something?Thanks for your time!
The text was updated successfully, but these errors were encountered: