lsmeans not estimable, but lsmean differences are? [R for BE/BA]

posted by ElMaestro  – Belgium?, 2019-02-26 12:40 (601 d 14:12 ago) – Posting: # 19975
Views: 1,824

Hi all,

I have a funny situation with one of my datasets:

In a semireplicated trial I am using the lsmeans package and syntax like
lnCI=confint(pairs(lsmeans(M, "Trt"), reverse =F), level=0.9)


to extract CIs from my model M where treatment is coded as "Trt" having two levels and it works just fine.

However, if I do something like
lsmeans(M, "Trt")


then I am getting "nonEst" of both rows in the column for the derived lsmeans.

So, R is telling me that it can derive a difference of lsmeans but it can't derive the lsmeans individually. I find this quite annoying, possibly hard to believe. On processing the same data with WNL, it (WNL) seems to be able to derive LSmeans, and it is getting the same difference in LSmeans as R.

Did anyone encounter this situation? I am quite baffled myself :confused:. Google isn't my friend. My own understanding of the LSmean derivation is a bit lacking, otherwise I'd much prefer to just write code myself and not rely on the package.

I really wish I could publish the dataset for someone to reproduce the situation, but I can't offer to do so at present.

Many thanks.:-)

I could be wrong, but...

Best regards,
ElMaestro

R's base package has 274 reserved words and operators, along with 1761 functions. I can use 18 of them (about 14 of them properly). I believe this makes me the Donald Trump of programming.

Complete thread:

Activity
 Admin contact
21,162 posts in 4,410 threads, 1,476 registered users;
online 2 (0 registered, 2 guests [including 2 identified bots]).
Forum time: Tuesday 02:53 UTC (Europe/Vienna)

In theory, there is no difference between theory and practice.
But, in practice, there is.    Jan L.A. van de Snepscheut

The Bioequivalence and Bioavailability Forum is hosted by
BEBAC Ing. Helmut Schütz
HTML5