Closed dmaxgomez closed 5 years ago
Thanks for the report. I did reproduce it, so I'll look into what might be causing it.
This seems to be associated with code that @jonathon-love added a while back; tagging him to see if he has any insight.
hmm, surprised we haven't encountered this sooner.
so the issue is here:
i encode the names of the columns as base 64 to prevent R functions from munging them, however, the model.Matrix
function here simply pastes the level together with the column name, which can break the base 64 encoding.
does anything actually use these labels? the column names of the matrix? does the user ever see them?
if not, i don't need to worry about decoding them (or i could replace the names with sequential integers?).
jonathon
The user can see them, because they can request the matrix itself (it is used for various purposes).
oh righto. i'll come up with a fix then.
Hi, I had problems with anovaBF apparently caused by the names of the levels of the random factor.
I managed to work out the following minimal example:
In this case, calling
anovaBF(x ~ t+s, whichRandom="s", data=toy)
leads to NAs in the output and to the following error:But if the random factor in the toy data is modified as follows:
then
anovaBF(x ~ t+s, whichRandom="s", data=toy)
works smoothly.I am using BayesFactor 0.9.12-4.2 on R 3.5.2.