Open sebastiansauer opened 7 years ago
Yes, a number of people have noted that BayesFactor does unexpected things with tibbles. I have not added support for tibbles because I'm not sure about their (intended) behaviour in all cases. Your suggested fix appears neutral, so I'll push that out.
ttestBF
appears to have issues when a tibble is given as input. Consider this tibble:And, in contrast, this data.frame version of the same data:
To check:
In
checking.R
this evaluation is performed (line 42):leading to a wrong conclusion for df, and to a right conclusion for df2. So, that's the problem.
Seen from a different perspective, tibble subsetting does not yield a vector, but a tibble, which is an unexpected behavior, see:
I suggest replacing the code in
checking.R
by something like this (see line 42):That should solve the issue.
For reference, line 42: