similar to: Millisecond TimeStamps

Is there a easy way to create the time index for a zoo/xts object for every 100 milliseconds. eg. time Index would be: 10:00:00:100 10:00:00:200 10:00:00:300 10:00:00:400 I am looking to build an empty zoo/xts object with time index from 10am to 3pm, index jumps by 100ms each row. Thanks, Chris -- View this message in context:

Hi, I''m new to programming and ruby and ROR, but I''m hoping to learn ruby to create custom scientific software. Mainly it involves measuring people''s reaction time to a series of words. I''m positive that this is possible using plain ruby on a computer (cause this is BASIC territory right?). But I want to create a ROR app that can do the same thing. My

I have this script which I use to get an epoch with accuracy of 1 second (based on R's inability to calculate millisecond-accurate timestamps -- at least I have not seen a straightforward solution :) ): nowInSeconds <- as.numeric(Sys.time()) nowInMS <- nowInSeconds * 1000 print(nowInSeconds) print(as.character(nowInMS)) when running this I get the following: > nowInSeconds <-

Dear all, I just have identified the following issue which I believe could be a bug in R: Let me illustrate: First, enable the display of fractional seconds and check that it works: > options(digits.secs = 6, digits = 6) > as.character(as.POSIXct("2018-08-31 14:15:16.123456")) [1] "2018-08-31 14:15:16.123456" Now create a sequence of POSIXct with stepwidth 0.1sec:

what package should I include to use timeDate? I want to convert a double (num of millis) into date object.

A sample of the data I have is: > head(sensor) logged_on accx accy accz compassx compassy compassz gyrox gyroy gyroz 1 1326561428000 -0.4602 0.8346 0.0936 0.145508 -0.350586 0.259766 59.617390 28.521740 59.617390 2 1326561428050 -0.4212 1.0452 0.1326 0.219727 -0.321289 0.241211 88.695656 27.478260 88.695656 3 1326561428100 -0.2496 1.3416 0.2886 0.214844 -0.326172

Full_Name: Bo Zhou Version: 2.6.1 (2007-11-26) OS: Windows XP Submission from: (NULL) (207.237.54.242) Hi, I found an arithmetic problem when I'm doing something with POSIXct The code to reproduce it is as follows (This is the recommended way of finding out time zone difference on R News 2004-1 Page 32 URL http://cran.r-project.org/doc/Rnews/Rnews_2004-1.pdf) a=Sys.time()

Hi, I was trying to generate RcppDatetime from a string. The main problem for me is that my string contains millisecond. I saw that RcppDatetime takes in double of seconds since epoch. I try to generate a double using boost but has no success. I'm wondering if you have any sample snippet? The string looks like: "2010-03-18 15:50:51.232" Secondly, what time zone RcppDatetime is

Hi, at the moment we can not use our permanent rds user CALs, because of Bug 9810 - validate_ldb of String(Generalized-Time) does not accept millisecond format ".000Z" Setup: - Two samba4-DCs with Debian Wheezy (7.7) - Samba Version: 4.1.14-9 - package distributor: Sernet As mentioned in the bug report, a patch is available at https://attachments.samba.org/attachment.cgi?id=8784 and

Hello all, my question for today is the following : I have 1. a date (in a string but straightforward to convert to any format) 2. the time as the number of milliseconds elapsed since hour 00:00:00.000 of this date. My question is : 1. Is there a in built function that can give me the date+time (as POSIX object for instance) from what I have ? -- View this message in context:

Hi there I'm loking for a time-measurement to measure time-differences in milliseconds. On my search, I only found the following: - package "base": Sys.time() -> only second-accuracy - package "R.utils": System$currentTimeMillis() -> returns integer of milliseconds, but accuracy is only whole seconds too. At the moment I run every bit of code to measure

Dear all, I would like to ask your help regarding handling time stamps in R. I think first I need a reference to read about their logic and how I should handle them. For example, this is a struct I have str(MyStruct$TimeStamps)  num [1:100, 1:6] 2011 2011 2011 2011 2011 ... MyStruct$TimeStamps[1,] [1] 2011.000   10.000    6.000   16.000   23.000   30.539 the last field contains

Hello, we are receiving some data, sample below - with a weird time/date stamp format, we need some help with R on converting this time date stamp to a useable field in R, date and time in a data-frame. The developer says its the number of milliseconds since midnight, January 1, 1970. sample: *1232558018624* --------------------- How do I interpret the time stamp? Is there a date, i need

On 5/10/23 08:50, Lucas Holt wrote: > On 5/10/23 4:36 AM, Antonio Larrosa wrote: >> Hello, >> >> This is probably a long email, but please bear with me. I plan to >> submit a patch and would like to explain what I will do before doing >> it so I don't lose time if there's some flaw in my plan. >> >> I currently use sshfs to mount directories

using "synchronized" subsecond timestamps imho only makes sense with synchronized time (ntp) through that ssh tunnel, too. and with this assumption a "full VPN ssh usage" instead of "only filesystem timestamps" [maybe trying with target systems without subsecond timestamps?] seems impractical to me. or at least "... [sry, didnt have internet to send, incomplete

R-users, I have two vectors (of timestamps) d1 <- as.POSIXct(strptime("2.2.2002 07:00", format="%d.%m.%Y %H:%M")) d2 <- as.POSIXct(strptime("4.2.2002 07:00", format="%d.%m.%Y %H:%M")) seq1 <- seq(d1, d2, "hours") seq1 d3 <- as.POSIXct(strptime("2.2.2002 15:22", format="%d.%m.%Y %H:%M")) d4 <-

Greetings Supreme Council of R Masters, Like toddler, I have gotten my head stuck in the banisters of R ... again. Let it be know I am still a neophyte in the R-community forum world, so please don't flame me too bad. I have two sets of data, each with a set of timestamps. I would like to somehow merge the datasets based on the timestamps and an individual identifier. That is there are

First, the reproducable example, showing how converting from character to POSIXct to character changes the milliseconds in the first time stamp though not in the second: > as.POSIXct('2010-06-03 9:03:58.324') [1] "2010-06-03 09:03:58.323 PDT" > as.POSIXct('2010-06-03 9:03:58.325') [1] "2010-06-03 09:03:58.325 PDT" This seems to be due to truncation of

I believe the performance of isUnsorted() in sort.c could be improved by calling REAL() once (outside of the for loop), rather than calling it twice inside the loop. As an aside, it is implemented in the faster way in doSort() (sort.c line 401). The example below shows the performance improvement for a vectors of double of moving REAL() outside the for loop. # example as implemented in

Hi Marc, yes, the patch worked for me! But for our production system I'm not really keen on building samba from scratch. So anything I could do to support you? Regards, Carsten Original Message processed by david? Re: [Samba] Bug 9810 - validate_ldb of String(Generalized-Time) does not accept millisecond for (14-Jan-2015 15:51) From: Marc Muehlfeld To (2):Carsten, samba at