StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12664447
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-09-30T19:42:02.800
FavoriteCount
0
LastActivityDate
2012-09-30T19:42:02.800
LastEditDate
LastEditorUserId
0
OwnerUserId
143305
ParentId
12658555
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
good to see fellow Debian old-timers here :) Your answer is already pretty nice. As I happen to work a lot with time series, I thought I'd throw in a variant using the excellent <a href="http://cran.r-project.org/package=zoo" rel="nofollow noreferrer">zoo</a> and <a href="http://cran.r-project.org/package=xts" rel="nofollow noreferrer">xts</a> packages. The latter builds on top of the former and has, among other things, the <code>period.apply()</code> function we can use here along with the <code>endpoints()</code> function to get you two-hourly aggregates. So at the top I'd use <pre><code>library(zoo) # for zoo objects library(xts) # for period.apply gcdata <- read.table("http://bernd.eckenfels.net/view/gc1001.ygc.csv", header=TRUE, sep=",", dec=".") timestamps <- gcdata$Timestamp + as.POSIXct(strptime("2012-01-01 00:00:00", format="%Y-%m-%d %H:%M:%S")) gcdatazoo <- zoo(gcdata[-1], order.by=timestamps) # as zoo object </code></pre> to create a <code>zoo</code> object. Your function remains: <pre><code>plotAreaCorridor <- function(x, y, col.poly1="lightgray", col.poly2="gray",...) { x.pol <- c(x, rev(x), x[1]) y.pol <- c(y[,1], rev(y[,5]),y[,1][1]) plot(x, y[,6]+1, type="n", ...) polygon(x.pol, y.pol, col=col.poly1, lty=0) x.pol <- c(x, rev(x), x[1]) y.pol <- c(y[,2], rev(y[,4]), y[,1][1]) polygon(x.pol, y.pol, col=col.poly2, lty=0) lines(x, y[,3], col="blue") # median lines(x, y[,6], col="red") # max invisible(NULL) } </code></pre> And we can then simplify a little: <pre><code>agg <- period.apply(gcdatazoo[,"Pause.s."], # to which data INDEX=endpoints(gcdatazoo, "hours", k=2), # every 2 hours FUN=function(x) quantile(x, # what fun. probs=c(5,20,50,80,95,100)/100)) #v99 = q99(gcdata$Pause.s.) # what is q99 ? v99 <- mean(agg[,5]) # mean of 95-th percentile? plotAreaCorridor(index(agg), # use time index as x axis coredata(agg), # and matrix part of zoo object as data ylim=c(0,max(agg[,5])*1.5), ylab="Quantiles of GC events", main="NewPar Collection Activity") abline(h=median(gcdatazoo[,"Pause.s."]), col="lightblue") abline(h=v99, col="grey") labeltxt <- paste("99%=",round(v99,digits=3),"s n=", nrow(gcdatazoo),sep="") text(x=index(agg)[20], y=1.5*v99, labeltxt, col="grey", pos=3) # or legend() </code></pre> which gives <img src="https://i.stack.imgur.com/Qo1Ph.png" alt="enter image description here"> The axis is now automatic and shows weekdays only as the span is less than week; this can be override as needed.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to plot quantil band (in R)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDirk Eddelbuettel
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to plot quantil band (in R)
 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
 VTAcceptedByOriginator
CommentsPostId
1. COCool, danke Dirk (q99 was the 99th percentile)
 singulars
 PostPostId
 PO
 UserUserId
 USeckes

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.