-
Notifications
You must be signed in to change notification settings - Fork 12
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
clmm + R 4.0 throws warning with long formula #34
Comments
Just echoing stragu with regard to the warning in This model
runs fine but throws a warning message
but if the last predictor is deleted, then it works without problems:
|
Thanks. Will fix soon.
Cheers
Rune
lør. 15. aug. 2020 kl. 18.46 skrev Stefan Th. Gries <
notifications@github.com>:
…
Just echoing stragu with regard to the warning in ordinal::clmm (and the
same setup: R 4.0.2 and ordinal_2019.12-10)
This model
m <- clmm(JUDGMENT ~ 1 + NATIVE_LG * AGREEMENT + EMPHPRON + NEGATION +
(1|SUBJECT), data=x)
runs fine but throws a warning message
Using formula(x) is deprecated when x is a character vector of length > 1.
Consider formula(paste(x, collapse = " ")) instead.`
but if the last predictor is deleted, then it works without problems:
m <- clmm(JUDGMENT ~ 1 + NATIVE_LG * AGREEMENT + EMPHPRON + (1|SUBJECT),
data=x)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHZZLOIKVJWUMVYE3XD4BLSA23XLANCNFSM4PFJQH5Q>
.
|
Now fixed in the version on GitHub dated 2020-08-22. Thanks again for mentioning this! |
Hi Rune, Thanks a lot |
Hi @runehaubo |
Using R 4.0.2 and ordinal 2019.12-10, I get a warning when using a formula with long names (but not changing the underlying data or the formula structure).
See for example this reprex:
Created on 2020-07-23 by the reprex package (v0.3.0)
I believe this might be because of how the
clmm.formulae()
function is defined, and might very well need a fix similar to issue #13 and PR #30, but I have a limited understanding of the functions involved, so I could be completely wrong! 🙂The text was updated successfully, but these errors were encountered: