You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After working at it for a bit, I realized the problem is because the input focus and background data frames contained a few mars_age values that were non-numeric. I fixed this with the following line run before the Qupid lines:
Even though this resolves the non-numeric values, the error persists (with identical output) until the type of the dataframe column is updated (from object to numeric):
After including this line, Qupid works as expected.
The error messages do not seem to reflect the root cause of the issue: that the type within the dataframe column is invalid. It would be preferable if Qupid could catch such type incompatibilities and report them to user in a more meaningful way.
The text was updated successfully, but these errors were encountered:
I recently an into an issue with Qupid that stumped me for half an hour. Basically, I ran Qupid using data from Qiita as follows:
Qupid outputted the following error:
After working at it for a bit, I realized the problem is because the input focus and background data frames contained a few
mars_age
values that were non-numeric. I fixed this with the following line run before the Qupid lines:Even though this resolves the non-numeric values, the error persists (with identical output) until the type of the dataframe column is updated (from object to numeric):
After including this line, Qupid works as expected.
The error messages do not seem to reflect the root cause of the issue: that the type within the dataframe column is invalid. It would be preferable if Qupid could catch such type incompatibilities and report them to user in a more meaningful way.
The text was updated successfully, but these errors were encountered: