-
Notifications
You must be signed in to change notification settings - Fork 3
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
Allow non-numeric data as input #81
Comments
We will eventually support non-numeric data (#81) but for now we error.
One of the key questions here is how we would label the returned the parameters with the non-numeric input |
Just an amateur suggestion, sorry if I'm way off, but would the function |
@Agasax Did you find the need to convert everything to numeric a big limitation in your use of {rater}? Implementing non-numeric input is feasible but it would be a lot of work so I'm considering whether it is worth it atm. I'd love to hear your thoughts! |
Sorry for slow response here. |
All good! Yes, that's what I meant really 😄 |
Unfortunately this isn't going to make it into the 1.1 release, but I'm going to add it into the 1.2 milestone so that I remember to work on it soon. |
Currently, we demand that all data be numeric - we should relax this to allow for, factors and character vectors etc. The key difficulty of this is how to present the input data in the output.
See discussion in #75 and compare with #70
The text was updated successfully, but these errors were encountered: