Aki Vehtari

Now that we have posterior package, we have chain and iteration info often, and could compute r_eff based on those, and maybe then for the arrays/matrices without that info assume...

Bumping this as I'm now in favor of reducing the need to enter `r_eff`. I would be fine with that `r_eff=1` unless we do get chain and iteration information via...

#235 reduced the need to provide `r_eff`. @bgoodri does that solve your problem?

For the record, I'm adding links to two relevant discussion threads - https://discourse.mc-stan.org/t/issue-with-dual-averaging/5995 - https://discourse.mc-stan.org/t/comparing-stans-adaptation-phase-to-that-of-nuts-rs/32259/13

I'm curious about the status of this

Given that metadata, how do I call cmdstan with those options in command line?

It would be nice to have `cmdstanr_verbose=TRUE` as documented argument for `$sampler()`, `$pathfinder()`, etc It could be useful to include that call to cmdstan to the returned object, too

Would it be possible to add an option to choose the output format, and keep the current format as the default?

I've started to think that maybe we should drop the relative efficiency adjustment of tail size. It is causing problems in edge cases. Anyway, for constant or almost constant such...

Inconsistent return type ``` > str(pareto_smooth(rnorm(1000), tail='right', return_k=FALSE)) num [1:1000] -0.136 -2.086 -1.33 -0.801 -0.612 ... ``` but ``` > str(pareto_smooth(rep(1,1000), tail='right', return_k=FALSE)) List of 2 $ x : num...