StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16776848
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
5
CommunityOwnedDate
2013-05-28T06:27:19.053
CreationDate
2013-05-27T16:01:05.753
FavoriteCount
0
LastActivityDate
2013-05-28T12:18:05.863
LastEditDate
2013-05-28T12:18:05.863
LastEditorUserId
516548
OwnerUserId
516548
ParentId
16776218
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Try this for zoo classic graphics, zoo lattice graphics and zoo ggplot2 graphics: <pre><code>library(zoo) z <- read.zoo(DT, split = 1, index = 2, FUN = identity) Names <- read.table(text = names(z), sep = ".", col.names = c("screen", "col")) plot(z, screen = Names$screen, col = Names$col) # also see note 3 below library(lattice) xyplot(z, screen = Names$screen, col = Names$col) # also see note 3 below library(ggplot2) # also see note 4 below m <- fortify(z, melt = TRUE) m2 <- transform(m, screen = sub("\\..*", "", Series), col = sub(".*\\.", "", Series)) qplot(Index, Value, data = m2, col = col, geom = "line") + facet_wrap(~ screen) </code></pre> Notes 1) If we just wanted separate panels it would just be <code>plot(z)</code>, <code>xyplot(z)</code> and <code>autoplot(z)</code>. 2) <code>names(z)</code> and <code>Names</code> are: <pre><code>> names(z) [1] "V1.a" "V2.a" "V1.b" "V2.b" "V1.c" "V2.c" > Names screen col 1 V1 a 2 V2 a 3 V1 b 4 V2 b 5 V1 c 6 V2 c </code></pre> 3) We could have just hard coded it as this (in which case we would not need <code>Names</code>): <pre><code>plot(z, screen = 1:2, col = c(1, 1, 2, 2, 3, 3)) xyplot(z, screen = 1:2, col = c(1, 1, 2, 2, 3, 3)) </code></pre> 4) Here is a ggplot2 alternative not involving <code>z</code>. It converts <code>DT</code> to long form with data.table package and then performs the <code>qplot</code>: <pre><code>long <- DT[, list(Series = names(.SD), Value = unlist(.SD)), by = list(type, time)] qplot(time, Value, data = long, col = type, geom = "line") + facet_wrap(~ Series) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPlotting multiple time series data ( long format ) into one plot?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USG. Grothendieck
UserOwnerUserId
1. USG. Grothendieck
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPlotting multiple time series data ( long format ) into one plot?
 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
 VTAcceptedByOriginator
CommentsPostId

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.