Skip to content
Prev 5510 / 5636 Next

[R-meta] Assessing selection bias / multivariate meta-analysis

Hi Pia,

You can ignore the warning messages that you're getting. (We haven't yet
worked out how to suppress them in the bootstrapping code.)

Your code looks good to me except for one subtle but potentially
consequential issue. Based on the multivariate summary meta-analyses, it
looks like you have a strongly negative average effect size. If the effects
are coded so that negative values represent improvement, then this needs to
be taken into account when fitting the selection models. The models
implemented in metaselection are based on one-side p-values, where the null
is mu <= 0 and the alternative is mu > 0 (i.e., positive effects are
improvements). We have not yet implemented an option to change the
direction of the null and alternative hypotheses (although it's high on my
to-do list). In the mean time, there are a few alternative ways that you
could modify the existing code to fit a more appropriate model. Either:
a) Recode effect sizes so that positive values correspond to improvement
(i.e., take yi = -yi) and interpret the beta estimate accordingly.
or
b) Change the threshold of the step function to steps = .975 and interpret
the lambda (selection parameter) estimate as the relative probability that
a statistically significant (and negative) effect size is reported compared
to the probability that a non-significant or counter-therapeutic effect
size is reported. For instance, if lambda = 4 then this means that a
statistically significant, therapeutic effect is four times more likely to
be reported than a non-significant or non-therapeutic effect.
Again, you only need do (a) or (b) but not both. It's possible that making
this change will shift the results in a meaningful way because the revised
model will be capturing a more plausible form of selective reporting.

James

On Thu, Nov 28, 2024 at 11:24?AM Pia-Magdalena Schmidt <
pia-magdalena.schmidt at uni-bonn.de> wrote: