Re: [Rd] cut.Date and cut.POSIXt problem

2008-03-26 Thread Roger D. Peng
I have applied these patches to R-devel and in my limited testing they appear to work as desired. I have to say that I never ran into the problem these patches were meant to solve so I may not be the best person to do the testing. -roger Marc Schwartz wrote: Hi all, Apologies for the

Re: [Rd] cut.Date and cut.POSIXt problem

2008-03-26 Thread Martin Maechler
RDP == Roger D Peng [EMAIL PROTECTED] on Wed, 26 Mar 2008 09:18:19 -0400 writes: RDP I have applied these patches to R-devel and in my limited testing they appear to RDP work as desired. I have to say that I never ran into the problem these patches RDP were meant to solve

Re: [Rd] cut.Date and cut.POSIXt problem

2008-03-26 Thread Marc Schwartz
Martin Maechler wrote: RDP == Roger D Peng [EMAIL PROTECTED] on Wed, 26 Mar 2008 09:18:19 -0400 writes: RDP I have applied these patches to R-devel and in my limited testing they appear to RDP work as desired. I have to say that I never ran into the problem these patches

Re: [Rd] cut.Date and cut.POSIXt problem

2008-03-20 Thread Marc Schwartz
Hi all, Apologies for the delay in my engaging in this thread. I was traveling this week. The problem that Gabor raised was caused by the patch that I submitted to fix a problem with the referenced functions when using 'months' and 'years' as the interval. The prior versions were

[Rd] cut.Date and cut.POSIXt problem

2008-03-18 Thread Gabor Grothendieck
cut.Date and cut.POSIXt indicate that the breaks argument can be an integer followed by a space followed by year, etc. but it seems the integer is ignored. For example, I assume that breaks = 3 months is supposed to cut it into quarters but, in fact, it cuts it into months as if 3 had not been

Re: [Rd] cut.Date and cut.POSIXt problem

2008-03-18 Thread Roger D. Peng
Seems it did work as advertised in R 2.6.0 but is still broken in R-devel. Will take a look. -roger Gabor Grothendieck wrote: cut.Date and cut.POSIXt indicate that the breaks argument can be an integer followed by a space followed by year, etc. but it seems the integer is ignored. For

Re: [Rd] cut.Date and cut.POSIXt problem

2008-03-18 Thread Gabor Grothendieck
I am using [1] R version 2.6.2 alpha (2008-01-26 r44181) and also get the same under: R version 2.7.0 Under development (unstable) (2008-03-13 r44752) On Tue, Mar 18, 2008 at 2:09 PM, Roger D. Peng [EMAIL PROTECTED] wrote: Seems it did work as advertised in R 2.6.0 but is still broken in

Re: [Rd] cut.Date and cut.POSIXt problem

2008-03-18 Thread Gabor Grothendieck
By the way, it would be nice if the breaks argument accepted the word quarter directly since its quite a common break to need when using dates. On Tue, Mar 18, 2008 at 2:29 PM, Gabor Grothendieck [EMAIL PROTECTED] wrote: I am using [1] R version 2.6.2 alpha (2008-01-26 r44181) and also get

Re: [Rd] cut.Date and cut.POSIXt problem

2008-03-18 Thread Roger D. Peng
Seems changes in r44116 force the interval to be single months (or years) instead of whatever the user specified. I think the attached patches correct this. Interestingly, 'cut' and 'seq' allow for the 'breaks' specification to be something like 3 months but the documentation for 'hist' does