yes it shows , more interesting :> a["2016-01-18 15:31:54.0"]value 2016-01-18 15:31:54 2> a["2016-01-18 15:31:54.07"]value> a["2016-01-18 15:31:54.079"]value 2016-01-18 15:31:54 2 why it doesn't work with .07 milisecond but work with .079 and .0 ?? -----Original Message----- From: "Huzefa Khalil" [huzefa.khalil at umich.edu] Date: 01/18/2016 09:26 PM To: "ce" <zadig_1 at excite.com> CC: r-help at r-project.org Subject: Re: [R] xts/zoo index problem? Try a["2016-01-18 15:31:54.079"] The question though is why R displays the milliseconds as "078", when it is clearly "079"... -h On Mon, Jan 18, 2016 at 8:55 PM, ce <zadig_1 at excite.com> wrote:> Dear all, > > I have this code : > > library(xts) > a <- structure(c(1,2), class = c("xts", "zoo"), .indexCLASS = c("POSIXct", > "POSIXt"), .indexTZ = "", tclass = c("POSIXct", "POSIXt"), tzone = "", index = structure(c(1453137885.23, > 1453149114.079), tzone = "", tclass = c("POSIXct", "POSIXt")), .Dim = c(2L, > 1L), .Dimnames = list(NULL, "value")) > > a > > a["2016-01-18 12:24:45.230"] > # value > #2016-01-18 12:24:45 1 > > a["2016-01-18 15:31:54.078"] > # value > > Why second line doesn't show the value? Something to do with miliseconds ? > Thanks > CE > > ______________________________________________ > R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see > stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code.
Well it works when you don't put the milliseconds because it is matching that part of the date which is provided. Hence, the following all work: a["2016-01-18 15:31:54.0"] a["2016-01-18 15:31:54"] a["2016-01-18 15:31"] a["2016-01-18 15"] However, what I don't get is why it is showing 1453149114.079 as "2016-01-18 15:31:54.078". It should be showing it as "2016-01-18 15:31:54.079". Anybody? On Mon, Jan 18, 2016 at 9:31 PM, ce <zadig_1 at excite.com> wrote:> > yes it shows , more interesting : > >> a["2016-01-18 15:31:54.0"] > value > 2016-01-18 15:31:54 2 > >> a["2016-01-18 15:31:54.07"] > value > >> a["2016-01-18 15:31:54.079"] > value > 2016-01-18 15:31:54 2 > > > why it doesn't work with .07 milisecond but work with .079 and .0 ?? > > > -----Original Message----- > From: "Huzefa Khalil" [huzefa.khalil at umich.edu] > Date: 01/18/2016 09:26 PM > To: "ce" <zadig_1 at excite.com> > CC: r-help at r-project.org > Subject: Re: [R] xts/zoo index problem? > > Try > > a["2016-01-18 15:31:54.079"] > > The question though is why R displays the milliseconds as "078", when > it is clearly "079"... > > -h > > > > On Mon, Jan 18, 2016 at 8:55 PM, ce <zadig_1 at excite.com> wrote: >> Dear all, >> >> I have this code : >> >> library(xts) >> a <- structure(c(1,2), class = c("xts", "zoo"), .indexCLASS = c("POSIXct", >> "POSIXt"), .indexTZ = "", tclass = c("POSIXct", "POSIXt"), tzone = "", index = structure(c(1453137885.23, >> 1453149114.079), tzone = "", tclass = c("POSIXct", "POSIXt")), .Dim = c(2L, >> 1L), .Dimnames = list(NULL, "value")) >> >> a >> >> a["2016-01-18 12:24:45.230"] >> # value >> #2016-01-18 12:24:45 1 >> >> a["2016-01-18 15:31:54.078"] >> # value >> >> Why second line doesn't show the value? Something to do with miliseconds ? >> Thanks >> CE >> >> ______________________________________________ >> R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see >> stat.ethz.ch/mailman/listinfo/r-help >> PLEASE do read the posting guide R-project.org/posting-guide.html >> and provide commented, minimal, self-contained, reproducible code. > >
On Mon, Jan 18, 2016 at 8:31 PM, ce <zadig_1 at excite.com> wrote:> > yes it shows , more interesting : > >> a["2016-01-18 15:31:54.0"] > value > 2016-01-18 15:31:54 2 > >> a["2016-01-18 15:31:54.07"] > value > >> a["2016-01-18 15:31:54.079"] > value > 2016-01-18 15:31:54 2 > > > why it doesn't work with .07 milisecond but work with .079 and .0 ?? >It's not surprising why it doesn't work with 0.070. It doesn't work because that's not what the milliseconds component is. It's also not surprising why it works with 0.079, because that's what the milliseconds component is (how something prints is not what it is equal to). It is a bit surprising that a value is returned when the milliseconds component is zero.> > -----Original Message----- > From: "Huzefa Khalil" [huzefa.khalil at umich.edu] > Date: 01/18/2016 09:26 PM > To: "ce" <zadig_1 at excite.com> > CC: r-help at r-project.org > Subject: Re: [R] xts/zoo index problem? > > Try > > a["2016-01-18 15:31:54.079"] > > The question though is why R displays the milliseconds as "078", when > it is clearly "079"... >See this StackOverflow question for discussion around why R prints fractional seconds the way it does: stackoverflow.com/q/7726034/271616> -h > > > > On Mon, Jan 18, 2016 at 8:55 PM, ce <zadig_1 at excite.com> wrote: >> Dear all, >> >> I have this code : >> >> library(xts) >> a <- structure(c(1,2), class = c("xts", "zoo"), .indexCLASS = c("POSIXct", >> "POSIXt"), .indexTZ = "", tclass = c("POSIXct", "POSIXt"), tzone = "", index = structure(c(1453137885.23, >> 1453149114.079), tzone = "", tclass = c("POSIXct", "POSIXt")), .Dim = c(2L, >> 1L), .Dimnames = list(NULL, "value")) >>Use a specific timezone. Everyone does not share your local timezone, and you don't say what it is. library(xts) # don't warn about object TZ vs local TZ differences options(xts_check_TZ=FALSE, digits.secs=6) a <- structure(1:2, class = c("xts", "zoo"), .indexCLASS=c("POSIXct", "POSIXt"), .indexTZ = "UTC", tclass = c("POSIXct", "POSIXt"), tzone = "UTC", index = structure(c(1453137885.23, 1453149114.079), tzone = "UTC", tclass = c("POSIXct", "POSIXt")), .Dim = c(2L, 1L), .Dimnames = list(NULL, "value"))>> a >> >> a["2016-01-18 12:24:45.230"] >> # value >> #2016-01-18 12:24:45 1 >> >> a["2016-01-18 15:31:54.078"] >> # value >> >> Why second line doesn't show the value? Something to do with miliseconds ? >> Thanks >> CE >> >> ______________________________________________ >> R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see >> stat.ethz.ch/mailman/listinfo/r-help >> PLEASE do read the posting guide R-project.org/posting-guide.html >> and provide commented, minimal, self-contained, reproducible code. > > ______________________________________________ > R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see > stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code.-- Joshua Ulrich | about.me/joshuaulrich FOSS Trading | fosstrading.com