search for: rp140

...;, "by.0")) : attempt to set an attribute on NULL The structure of my table is as follows. > str(no.genot) table [, 1:467] 0.000 0.261 0.315 0.274 0.349 ... - attr(*, "dimnames")=List of 1 ..$ : chr [1:467] "NC" "RP138" "RP139" "RP140" ... Strangely enough > mean(no.genot[1:467]) [1] 0.2426167 That seems to work. -- Farrel Buchinsky Mobile: (412) 779-1073

> On Aug 23, 2017, at 8:08 AM, PIKAL Petr <petr.pikal at precheza.cz> wrote: > > Hi > > Well, yes I tried it about two weeks ago but my post did not get through as it still awaits moderator approval. It got through just fine. It appeared on Aug 15. It just didn't get any replies. As I read your original question in this thread, it was not clear to me that you had

Hi Well, yes I tried it about two weeks ago but my post did not get through as it still awaits moderator approval. I could check which column is offending but actually it is only minor nuisance, I can live with selection of columns before fitting a model. What seems to me strange is that both full dataset and only selected colums gave me identical fit results but only one works within augPred.