- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Contrasting slopes: differences between backends #333
Comments
You're a bit out of date with the modelbased version, the first example currently doesn't work. Fixed in #331 |
The question is, how much work do we want to put in maintaining the |
Not sure long term, but short term it'd be good to be able to show that we can reproduce its result as - at least in my mind - emmeans is kind of the baseline / ground truth. |
Ok, and we want: model <- lm(Petal.Width ~ Petal.Length * Species, data = iris)
emmeans::emtrends(model, "Species", "Petal.Length") |>
emmeans::contrast(method = "pairwise")
#> contrast estimate SE df t.ratio p.value
#> setosa - versicolor -0.1298 0.1560 144 -0.835 0.6821
#> setosa - virginica 0.0409 0.1530 144 0.268 0.9613
#> versicolor - virginica 0.1708 0.0708 144 2.412 0.0449
#>
#> P value adjustment: tukey method for comparing a family of 3 estimates Created on 2025-02-13 with reprex v2.1.1 |
emmeans acts up funny:
Created on 2025-01-13 with reprex v2.1.1
The text was updated successfully, but these errors were encountered: