Displaying 20 results from an estimated 3000 matches similar to: "strptime mysteriously adds a day - 0S-specific: Linux and (PR#1468)"
2002 Apr 18
1
strptime mysteriously adds a day - 0S-specific: Linux and (PR#1467)
On Thu, 18 Apr 2002, Martin Maechler wrote:
> >>>>> "Jason" == Jason Turner <jasont@indigoindustrial.co.nz> writes:
>
> Jason> strptime() mysteriously adds a day to a date, unless the year
> Jason> is specified. Tested on:
> Jason> Linux (RedHat 6.0) - R version 1.4.1 and R-devel.
> Jason> Windows - R version 1.4.1
>
2003 Mar 12
1
'summary' with logicals (PR#2629)
Consider
> oj <- data.frame(x = c(TRUE, FALSE, NA))
> oj
x
1 TRUE
2 FALSE
3 NA
> summary(oj)
x
Mode :logical
FALSE:1
TRUE :1
But
> oj$x <- factor(oj$x)
> summary(oj)
x
FALSE:1
TRUE :1
NA's :1
My point is that NA's should be reported for logicals like they are for
other data types.
Göran
---
Göran
2002 Feb 20
3
Pointer to covariates?
In the first line, use the dist function, found in library mva,
to get the distance between each pair of rows. From this
calculate an incidence matrix for which element i,j is true if
row i in dat equals row j in dat (and false elsewhere).
In the second line, for each row calculate the indices of
the matching rows and take the minimum of those as the key.
incid <-
2002 Apr 18
1
strptime mysteriously adds a day - 0S-specific: Linux and Windows (so far) (PR#1466)
strptime() mysteriously adds a day to a date, unless the year
is specified. Tested on:
Linux (RedHat 6.0) - R version 1.4.1 and R-devel.
Windows - R version 1.4.1
Bug isn't found on OpenBSD, R version 1.4.1.
Transcript:
R : Copyright 2002, The R Development Core Team
Version 1.4.1 (2002-01-30)
...
> ## BUG:
> ## strptime seems to add a day to the request, unless the year
> ##
1999 Apr 02
4
PLATFORMS Update
NAME Douglas Bates
EMAIL bates@stat.wisc.edu
VERSION 0.63.3
PLATFORM i386-unknown-linux
SYSTEM Debian 2.1
CC/FC/MAKE egcs/g77/make
NAME Martyn Plummer
EMAIL plummer@iarc.fr
VERSION 0.63.3
PLATFORM i386-unknown-linux
SYSTEM Redhat 5.1
CC/FC/MAKE gcc/egcs-g77/make
NAME Göran Broström
EMAIL gb@stat.umu.se
VERSION 0.63.3
PLATFORM
2002 Oct 17
2
'text' can't find "x"
I wanted to add some text to a plot and got (R-1.6.0, Linux):
> text(x = c(1, 4), y = 5, labels = x)
Error in text.default(x = c(1766, 1895), y = 5, labels = x) :
Object "x" not found
With the default value of 'labels':
> text(x = c(1, 2), y = 5, labels = seq(along = x))
Error in seq(along = x) : Object "x" not found
A scoping bug? :)
But
>
2012 Sep 04
0
AFTREG weights
On Wed, Aug 1, 2012 at 3:08 PM, <fra.meucci@hotmail.it> wrote:
> Dear Göran Broström,
> I am trying to use AFTREG function for R to estimate a loglogistic
> survival function, including time dependent covariates.
> Actually, my Subset includes some partial events; the idea is to model
> this kind of events using something similar to “weights” in the SURVREG
> function.
2004 Sep 20
0
[Old '.so' file
I noticed the same thing as I reported below, when I upgraded from
R-2.0.0-alpha-20040918 to today's beta version:
'R CMD check' failed as before; but after cleaning 'src' from .o and .so
files, it worked again. So the two-day-old '.so' file is obviously different
from today's. Has compiler directives changed in the two last days? Or what
is happening?
G?ran
On
2002 Oct 08
1
Numeric to factor
I find 'How do I convert factors to numeric?' in the FAQ (7.12), but not
the other way around. Trivial maybe, but
> codes(factor(c(2, 10))
[1] 2 1
> codes(factor(c(2, 9)))
[1] 1 2
How do I get the levels attached to the codes in numeric order?
G?ran
---
G?ran Brostr?m tel: +46 90 786 5223
Department of Statistics fax: +46 90 786 6614
Ume? University
2003 Jun 07
2
Ordering long vectors
I need to order a long vector of integers with rather few unique values.
This is very slow:
> x <- sample(rep(c(1:10), 50000))
> system.time(ord <- order(x))
[1] 189.18 0.09 190.48 0.00 0.00
But with no ties
> y <- sample(500000)
> system.time(ord1 <- order(y))
[1] 1.18 0.00 1.18 0.00 0.00
it is very fast!
This gave me the following idea: Since I don't care
2007 Mar 21
1
bug and patch: strptime first-of-month error in (possibly unsupported use of) "%j" format (PR#9577)
Full_Name: John Brzustowski
Version: R-devel-trunk
OS: linux (problem under Windows too)
Submission from: (NULL) (74.101.124.238)
(This bug was discovered by Phil Taylor, Acadia University.)
I'm not sure from reading the documentation whether strptime(x, "%j") is meant
to be supported, but if so, there is a bug which prevents it from working on the
first day of months after
2009 Feb 27
0
POSIXlt, POSIXct, strptime, GMT and 1969-12-31 23:59:59
R-devel:
Some very inconsistent behavior, that I can't seem to find documented.
Sys.setenv(TZ="GMT")
str(unclass(strptime("1969-12-31 23:59:59","%Y-%m-%d %H:%M:%S")))
List of 9
$ sec : num 59
$ min : int 59
$ hour : int 23
$ mday : int 31
$ mon : int 11
$ year : int 69
$ wday : int 3
$ yday : int 364
$ isdst: int 0
- attr(*, "tzone")= chr
2003 Feb 02
1
Observations about the floating point data in vorbisfile
Hello.
I noticed that when reading data with ov_read_float(), you can get
values outside [-1..1] when the stream is encoded at lower quality, but
with higher quality, the values trim down to inside [-1..1].
Looking at the plot from -q10, the data from ov_read_float seems
clipped.
I've made some plots of encoding the start of Rammsteins Feuer from the
xXx soundtrack (it's a pretty loud
2009 Jul 21
1
Problem with INTERNALDATE when the year in localtime and GMT different
In my thought utc_offset function in src/lib/utc-offset.c returns wrong
offset value when the year in localtime and GMT different.
/* max offset of 24 hours */
if (ltm.tm_yday < gtm.tm_yday)
offset = -24 * 60;
else if (ltm.tm_yday > gtm.tm_yday)
offset = 24 * 60;
else
offset = 0;
I think this code should be modified as followings.
/* max offset of 24 hours */
if ((ltm.tm_year ==
2000 Mar 22
0
dyn.load and rw1000
Guido,
> thanks for signaling this. The --mno-cygwin was a my typos error
> but I have to correct the readme.packages (--no-cygwin is a survival
> from the about two year ago version of cygwin).
The flag is set correctly in MkRules, though.
> Anyway, note that in readme.packages we suggest to edit 'MkRules'
> not MakeDll and to set at the beginning of that file
2005 Mar 27
0
RE: [Rd] F90
G?ran, thanks.
Happy easter!
-----Original Message-----
From: G?ran Brostr?m [mailto:gb at stat.umu.se]
Sent: ned 2005-03-27 07:38
To: Gorjanc Gregor
Cc: r-help at stat.math.ethz.ch
Subject: Re: [Rd] F90
On Sun, Mar 27, 2005 at 03:26:39AM +0200, Gorjanc Gregor wrote:
> Hello!
>
> Has anyone successfully compiled F90 sources in R-package? I found the
> same question on r-devel list
2012 Feb 20
10
[PATCH] hvm: Correct RTC time offset update error due to tm->tm_year
Hi
In rtc_set_time, mktime is called to calculate seconds since 1970/01/01,
input parameters of mktime are required to be in normal date format.
Such as: year=1980, mon=12, day=31, hour=23, min=59, sec=59. However,
the current input parameter of mktime is tm->tm_year, and it is the
number of years since 1900. (For example, if current time is 2012/12/31,
and tm->tm_year is 112). This is
1999 Dec 07
4
Finding indices with a certain property
I want the indices i for which x[i] < 0 (say):
> x <- c(1, -1, 3, 3, -2)
> where.negative(x)
[1] 2 5
Surely where.negative is something simple, but how?
G?ran
--------------------------------------------------------------
G?ran Brostr?m
Department of Statistics tel: +46 90 786-5223
Ume? University fax: +46 90 786-6614
S-90187 Ume?, Sweden
2003 Dec 18
1
Manova
Dear R-helpers,
In a data set I got from a medical doctor there are six treatment groups
and (about) 5 bivariate responses in each group. Using 'manova', it is
easy to see significant differences in treatment effects, but the doctor
is more interested in the correlation between the two responses (within
groups). I'm willing to assume a common value over groups, and one way
of
2003 Jun 16
0
new package: eha
A few days ago I uploaded to CRAN a new package called 'eha', which
stands for 'Event History Analysis'. Its main focus is on proportional
hazards modeling in survival analysis, and in that respect eha can
be regarded as a complement and an extension to the 'survival'
package. In fact eha requires survival. Eha contains three functions
for proportional hazards