similar to: month increment for chron dates

I'm not too familiar with chron, but I don't think it should drop the month and day in the second example following example: > chron(20000, format="y/m/d") [1] 124/10/04 > chron(20000, format="yy/m/d") [1] 2024 Paul Gilbert -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read

Hi all, my question: how is the exact formula to calculate bandwidth needed to upstream at given bitrate to a certain number of simultaneous listeners ? is it simply BANDWIDTH (bps) = BITRATE (bps) X LISTENERS ? tnx in advance, carlo. -------------- next part -------------- An HTML attachment was scrubbed... URL:

I was just looking for an easy way to convert between COM datetime and chron datetime (both ways.) I found examples on the list, but they involved origin. Does anyone have functions for converting COM datetime <-> chron datetimethat work "safely"? David L. Reiner > -----Original Message----- > From: Gabor Grothendieck [mailto:ggrothendieck@gmail.com] >

I built R 2.2.0 from source on my debian machine yesterday and updated all packages. My problem is that "dates" function from its, that my code heavely uses is now masked by "dates" from chron. How can I specify tehat I want to use dates from its or how can I prevent it from being masked? > library(its) Loading required package: Hmisc Hmisc library by Frank E Harrell Jr

> > > Dear All, > > > > I am currently using R for windows. > > > > I am wondering why the dates command in chron package does not work in the > > following situation: > > > > cut(dates(c(23,45,67),origin=c(1,1,2004)),"months") > > > > but will work for: > > > >

Full_Name: Kem Phillips Version: 2.7.1 (2008-06-23) OS: Windows Xp professional Submission from: (NULL) (98.221.200.108) The Hmisc function describe fails, giving the error message: Error in formatDateTime(dd, atx, !timeUsed) : could not find function "format.dates" Loading the chron package, where function dates apparently resides, does not fix the problem. Note

Dear R People: Here is an interesting question: >library(chron) >xt <- seq.dates(from="01/01/2004",by="days",length=5) >xt [1] 01/01/04 01/02/04 01/03/04 01/04/04 01/05/04 > #Fine so far >as.POSIXct(xt) [1] "2003-12-31 18:00:00 Central Standard Time" [2] "2004-01-01 18:00:00 Central Standard Time" [3] "2004-01-02 18:00:00 Central

Dear all, In RW0901 I could > dates("01/01/2000") [1] 01/01/100 where only the printing was wrong, but the double numeric representation of the chron object was calculated correctly but now in RW0990 > dates("01/01/2000") Error in fun(yy, ...) : must be 2-digit (numeric) year specification and also the followig doesn't help > dates("01/01/2000",

Hello r-help, I'm trying to split a character vector of dates of the form "dd-mmm-yy" into component days, months and years. But > library(chron) > testdate<-as.POSIXlt(strptime("17-Sep-98","%d-%b-%y")) > testdate [1] "1998-09-17" > months(testdate) [1] "September" # which is fine, but for days and years I get >

I get faulty output from seq.dates() if I specify a length that is too long. For example, I ask for 129 months in the following call to the function, but it returns 131: > R.version.string [1] "R version 1.9.1, 2004-06-21" > startdatetime <- chron(dates="01/01/1995", times="00:00:00") > beg.month.datetimes <- seq.dates(from=startdatetime,

Hello, I have a dataset which has fields giving both calendar date and weekday. I know better functions are now available, but I am still using chron because of the is.holiday() function and a homemade (even Heath Robinson would be ashamed) is.daylight() function. As a check for typos in the data input, I checked that the dates matched the weekdays. I'm getting some confusing results

Hello, I've encountered the need to cut some chron objects of the form: R> mychron <- chron(sort(runif(10, 0, 10))) R> mychron [1] (01/01/70 16:36:20) (01/02/70 00:08:46) (01/03/70 16:54:49) [4] (01/04/70 06:45:00) (01/07/70 06:21:24) (01/07/70 18:28:44) [7] (01/08/70 00:47:05) (01/08/70 05:11:44) (01/10/70 01:07:53) [10] (01/10/70 17:46:53) into arbitrary (e.g. a given number

Hello All: I am trying to generate a sequence of dates using library(chron). Using the following code, I got most of what I want, dts <- seq.dates("01/02/1998", "01/10/2001", by="day") dts <- dts[!is.weekend(dts)] a sequence of weekdays only (no weekend dates), with first observation appearing as 01/02/98 and the last 01/10/01. But I would

Hello, today I've updated on the newest R-Version. But sadly a function I needed didnt want to work: The input is e.g. days(as.Date("21-07-2005","%d-%m-%y")) the error is: Fehler in Math.Date(dts): floor nicht definiert f??r Date Objekte (Error in Math.Date(dts): floor not defined for date objects) Same for year. Only months gives me the correct output. In Version

Hi, I've been using the chron package to convert excel time into month/day/year and h:m:s formats, specifically for use as axis labels. I've come across something I don't quite understand. ### Here are some excel times: dat = c(39083, 39083.00694, 39083.01389, 39083.02083, 39083.02778, 39083.03472, 39083.04167, 39083.04861, 39083.05556, 39083.0625 ) ### I create

the date were created with chron with this argument format=c(dates="Y/m/d", times="H:M:S")) so I have the dates being displayed as (10/06/22 12:00:00) I would like to have them displayed as "2010-06-22 12:00:00" or "%Y-%m-%d %H:%M:%S" and then I can convert these for mergeing with another data frame x <- (structure(c(14464, 14464.0104166667,

The problem with POSIXt is that you must consider timezones and daylight vs. standard time issues even if you don't want to. This violates modularity (viz. your routines becomes coupled to unrelated information) and leads to subtle errors where different routines are assuming different time zones. The problem is that the time, date, day of the week, month, etc. of a date depend on its

This is not specifically on-topic for Asterisk, but I have found on many occasions while working with Asterisk that it would have been very handy to be able to measure, with some precision, the bandwidth being used by a particular host, port, or combination of the two. So, I went searching for various tools, none of which were what I wanted. They either were too clever, or too limited in

2003-06-28 Bandwidth Study - John Todd (jtodd @loligo.com) Purpose: ------------- To obtain a better chart of actual bandwidth usage per codec as seen "on-the-wire" when using IAX2 trunking between two Asterisk telephony servers. Discussion: ------------- Past threads on the asterisk-dev and asterisk-users lists have indicated that the optimal way to save bandwidth on

In the precompute_partition_info_sums_ function, instead of selecting 64-bit accumulator when the signal bps is larger than 16, revert to the original approach based on partition size, but make room for few extra bits to not overflow with unusual signals where the average residual magnitude may be larger than bps. It slightly improves the performance with standard encoding levels and 16-bit files