the*_*ide 3 r plyr dplyr data.table
我有一个样本数据集,可以跟踪自行车到不同站点的轨迹.我的目标是找到自行车在特定车站的间隔difftime(),在这种情况下是车站B.
> test
bikeid start_station starttime end_station endtime
1 1 A 2017-09-25 01:00:00 B 2017-09-25 01:30:00
2 1 B 2017-09-25 07:30:00 C 2017-09-25 08:00:00
3 1 C 2017-09-25 10:00:00 A 2017-09-25 10:30:00
4 1 A 2017-09-25 13:00:00 C 2017-09-25 13:30:00
5 1 C 2017-09-25 15:30:00 B 2017-09-25 16:00:00
6 1 B 2017-09-25 18:00:00 B 2017-09-25 18:30:00
7 1 B 2017-09-25 19:00:00 A 2017-09-25 19:30:00
8 1 ? 2017-09-25 20:00:00 B 2017-09-25 20:30:00
9 1 C 2017-09-25 22:00:00 C 2017-09-25 22:30:00
10 1 B 2017-09-25 23:00:00 C 2017-09-25 23:30:00
Run Code Online (Sandbox Code Playgroud)
有时,自行车不会在他们结束的同一站点开始,这些情况应该被忽略.在上面的数据集,我们可以看到,之间流逝360分钟01:30:00和07:30:00,即120分钟失效之间16:00:00和18:00:00之间失效,那30分钟18:30:00和19:00:00.第8行和第10行被忽略,因为自行车不会在它结束的同一站点启动.因此,输出向量应为:
[1] 360 120 30
Run Code Online (Sandbox Code Playgroud)
以下代码使用不会产生所需的输出:
sapply(test$starttime[test$end_station == "B"], function(x, et) difftime(et[x < et][1], x, units = "mins"), et = test$endtime[test$start_station == "B"])
Run Code Online (Sandbox Code Playgroud)
一个人怎么会考虑到下一行,并计算difftime()只有当end_station和start_station以下行是平等的吗?用lead()在dplyr?任何建议将不胜感激
以下是示例数据:
> dput(test)
structure(list(bikeid = c(1, 1, 1, 1, 1, 1, 1, 1, 1, 1), start_station = c("A",
"B", "C", "A", "C", "B", "B", "?", "C", "B"), starttime = structure(c(1506315600,
1506339000, 1506348000, 1506358800, 1506367800, 1506376800, 1506380400,
1506384000, 1506391200, 1506394800), class = c("POSIXct", "POSIXt"
), tzone = ""), end_station = c("B", "C", "A", "C", "B", "B",
"A", "B", "C", "C"), endtime = structure(c(1506317400, 1506340800,
1506349800, 1506360600, 1506369600, 1506378600, 1506382200, 1506385800,
1506393000, 1506396600), class = c("POSIXct", "POSIXt"), tzone = "")), .Names = c("bikeid",
"start_station", "starttime", "end_station", "endtime"), row.names = c(NA,
-10L), class = "data.frame")
Run Code Online (Sandbox Code Playgroud)
library(data.table)
mtest = melt(setDT(test), id="bikeid",
meas = patterns("_station", "time"),
variable.name = "event",
value.name = c("station", "time"))
mtest[.(factor(1:2), c("start", "end")), on=.(event), event := i.V2]
setkey(mtest, bikeid, time)
Run Code Online (Sandbox Code Playgroud)
然后在自行车闲置的时候回到广阔的地方......
idleDT = dcast(mtest[-c(1,.N)][, g := rep(1:.N, each=2, length.out=.N)],
g ~ rowid(g), value.var=c("station", "time"))
g station_1 station_2 time_1 time_2
1: 1 B B 2017-09-25 01:30:00 2017-09-25 07:30:00
2: 2 C C 2017-09-25 08:00:00 2017-09-25 10:00:00
3: 3 A A 2017-09-25 10:30:00 2017-09-25 13:00:00
4: 4 C C 2017-09-25 13:30:00 2017-09-25 15:30:00
5: 5 B B 2017-09-25 16:00:00 2017-09-25 18:00:00
6: 6 B B 2017-09-25 18:30:00 2017-09-25 19:00:00
7: 7 A <U+0410> 2017-09-25 19:30:00 2017-09-25 20:00:00
8: 8 B C 2017-09-25 20:30:00 2017-09-25 22:00:00
9: 9 C B 2017-09-25 22:30:00 2017-09-25 23:00:00
Run Code Online (Sandbox Code Playgroud)
然后加入或过滤并计算......
idleDT[.("B", "B"), on=.(station_1, station_2), time_2 - time_1 ]
Time differences in mins
[1] 360 120 30
Run Code Online (Sandbox Code Playgroud)
评论
我应该解释为什么我喜欢长格式mtest而不是OP test,即使我回到宽格式进行分析(感谢@Henrik)......
endtime,end_station那么逻辑上应该丢失,但在我看来,这更容易以长格式跟踪.一般来说,我只是应用我(可能是过分热心或错误的)对整洁数据的理解,在关于数据布局的链接中重复哈德利的抱怨,其中"[c] olumn header是值,而不是变量名".