Wolfgang Viechtbauer

Also 1. is done now. Will eventually tackle 3.

Hi Guido, Indeed, this info is not currently stored inside the returned object. The same applies to various other inputs (e.g., `rma.uni(ri=0.5, ni=50, measure="COR")$ri` is `NULL`). Is there a specific...

In principle, I could add the input variables to the returned object. This actually happens for a few measures (such as `"RD"`, `"RR"`, and `"OR"`) to make things like `labbe()`...

I will have to find time to figure out how exactly thin plate splines are incorporated into the model. An alternative might be to use restricted cubic splines, as illustrated...

I would have to really study the details, but I suspect that this will not currently be possible with the way things work in metafor.

I happened to have taken Gavin Simpson's excellent course on GAMs in the meantime. So, in principle, one can do the same thing as in the example linked to above...

To begin, definitely interested in thinking about these enhancements. With respect to 1: Would have to think about how to make this work, but I think the idea is nice....

Could you please be more specific what exactly you would like to see in the output? `escalc()` and `rma.mv()` are really fundamentally different functions, so it's not clear to me...

Actually, `escalc()` does store sample size information, as an attribute of the `yi` element. See: dat

Not sure what kind of binding operations you are doing, but there are methods for `escalc` objects that handle the `ni` attribute properly. For example: dat