Adapt metafor's reporter() to work with our use of rma.mv() about metalab HOT 5 OPEN

It's fairly stright forward to add this to our current system. What kind of output do you want? Here's a simple example for rma.uni but I can do the same for rma.mv as well. http://kylehamilton.com/old-old/corr_basic.html

from metalab.

@erikriverson here is the Issue @christinabergmann mentioned in Slack. Documentation for the existing report function for rma.uni() is here: https://rdrr.io/cran/metafor/man/reporter.html, and we would want the same/similar for rma.mv()
Christina, any changes to the report you would suggest, or just exactly the same as the existing report function for rma.uni()

from metalab.

Hi, just alerting everyone to Wolfgang Viechtbauer's presentation as ESMAR2021 on the reporter() function here https://youtu.be/2o4PBUBbWAE?t=541

Also that a question someone asked whether it would be extended to be able to generate reports for rma.mv() objects and Wolfgang's reply was "rma.mv objects can be extremely complex. It would be very difficult to create automated reports based on such objects." - so that means 1) it isn't already in the pipeline for the metafor package, but 2) might turn out to be a challenge, let's see! :)

from metalab.

Ha yes, he had the same answer at ResSyn2019. But that's because rma.mv in principle is super general. Since we use it in a rather specific way, for a subset of possible effect sizes, random effects, etc, it will be much easier, since the space of possibilities is much more limited. I.e. the report would be based on the same models we use in the visualizations.

So much less daunting, right?

Ch

from metalab.

Yes true! :D

from metalab.