StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8353127
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-02T07:37:20.340
FavoriteCount
0
LastActivityDate
2011-12-02T07:37:20.340
LastEditDate
LastEditorUserId
0
OwnerUserId
1030648
ParentId
8351985
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
lme and nlme fit through maximum likelihood or restricted maximum likelihood (the latter is the default), so your results will be based on either of those methods <code>summary(fm1Machine)</code> will provide you with the output that includes the means and standard errors: <pre><code>....irrelevant output deleted Fixed effects: score ~ Machine Value Std.Error DF t-value p-value (Intercept) 52.35556 2.229312 46 23.48507 0 MachineB 7.96667 1.053883 46 7.55935 0 MachineC 13.91667 1.053883 46 13.20514 0 Correlation: ....irrelevant output deleted </code></pre> Because you have fitted the fixed effects with an intercept, you get an intercept term in the fixed effects result instead of a result for MachineA. The results for MachineB and MachineC are contrasts with the intercept, so to get the means for MachineB and MachineC, add the value of each to the intercept mean. But the standard errors are not the ones you would like. To get the information you are after, fit the model so it doesn't have an intercept term in the fixed effects (see the <code>-1</code> at the end of the fixed effects: <pre><code>fm1Machine <- lme(score ~ Machine-1, data = Machines, random = ~ 1 | Worker ) </code></pre> This will then give you the means and standard error output you want: <pre><code>....irrelevant output deleted Fixed effects: score ~ Machine - 1 Value Std.Error DF t-value p-value MachineA 52.35556 2.229312 46 23.48507 0 MachineB 60.32222 2.229312 46 27.05867 0 MachineC 66.27222 2.229312 46 29.72765 0 ....irrelevant output deleted </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGetting Generalized Least Squares Means for fixed effects in nlme or lme4
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMichelle
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGetting Generalized Least Squares Means for fixed effects in nlme or lme4
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.