-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Drop interpretation of std slopes / parameters #97
Comments
@DominiqueMakowski That's your issue :-) |
I'm not sure how psychos name it, but I'm used to use "b" for refer to unstandardized, and "beta" to standardized coefficients. |
Same (: |
So we might think of changing:
into
? |
though that's a very confusing distinction I never understood where it came from, "b" is literally the poorman's ascii way of representing the beta symbol which stands for "beta" which stands for the coefficient of the equation. And standardized betas are, well, So I'd agree to change beta for |
I'm not sure if there's a general agreement on this. Maybe "b" and "std. beta"? |
That seems like a good compromise that leaves no ambiguity |
To reiterate: This is not an issue with Funder's rules, it is a problem with interpretation of std slopes / parameters in general - there are no rules of thumb because the value of std beta depends not only on the partial correlation between xi and y, but also on the multicolinearity between the Xs, the relationship between the other predictors and Y, etc. However... if we want we can look at the partial effect sizes, e.g., |
Regardign the text, I very strongly vote for either "b" and "std. b" or "beta" and "std. beta". Again, both refer to the beta symbol which is the convention for regression coefficients. Or we could go with "coefficient" and "std. coefficient" but that's long and APA suggests to replace by beta symbols anyway which b or beta would refer to. Now regarding the automatic interpretation of these coefs............... Well, it's been my secret desire and goal for a long time, hence the effectsize "standardization of standardized indices" monstrosity. But I agree that currently there is no clean solution, so we might want to drop the interpretation for now altogether. Or, we could only add the interpretation for non-interaction terms (i.e., interpret the coefs as either partial correlation for continuous predictors or as standardized difference for level difference), where it is more straightforward. As for the conversion to partial effect sizes, it did seem as a good avenue but what with Bayesian models... |
We do have |
My personal strong preferences is to use "β" and "std. β" for the coefficients. The "b" versus "β" distinction seems in my experience to mostly only occur in Gaussian linear regression (e.g., most presentations of GLMs using β throughout), and many classic regression texts using different notation (e.g., Cohen et al. used "b" and "B"). It's inconsistent enough that folks really shouldn't rely on a "b = unstandardized, β = standardized" heuristic. |
From the README:
However, Funder's (2019), with r guidelines, should not be used for interpreting Beta values (see discussion here: easystats/effectsize#127).
The text was updated successfully, but these errors were encountered: