Displaying 20 results from an estimated 3000 matches similar to: "length of POSIXlt object (PR#13482)"
2009 Dec 24
1
bug in princomp example (PR#14167)
When I run
example(princomp)
I get the following error message:
prncmp> ## The variances of the variables in the
prncmp> ## USArrests data vary by orders of magnitude, so scaling is
appropriate
prncmp> (pc.cr <- princomp(USArrests)) # inappropriate
Error in cov.wt(z) : 'x' must contain finite values only
Seth Roberts
--
blog.sethroberts.net
www.shangriladiet.com
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
2011 Feb 04
2
terribly annoying bug with POSIXlt : one o'clock is midnight?
Apparently, as.POSIXlt takes one o'clock as the start of the day :
> as.POSIXlt(0,origin="1970-01-01")
[1] "1970-01-01 01:00:00 CET"
> as.POSIXlt(0,origin="1970-01-01 00:00:00")
[1] "1970-01-01 01:00:00 CET"
> as.POSIXlt(0,origin="1970-01-01 23:59:59")
[1] "1970-01-02 00:59:59 CET"
Cheers
--
Joris Meys
Statistical
2016 Dec 06
1
segfault with POSIXlt zone=NULL zone=""
Hi Joshua,
Thank you for minimizing my test case.
> > Hope I'm not doing something illegal...
> >
> You are. You're changing the internal structure of a POSIXlt object
> by re-ordering the list elements. You should not expect a malformed
> POSIXlt object to behave as if it's correctly formed. You can see
> it's malformed by comparing it's
2012 Sep 05
2
POSIXlt and daylight savings time
I have a data frame that contains dates, but when I use as.POSIXlt() I lose
the hours on all records. I traced this down to a particuar hour which
causes the issue...
> as.POSIXlt('2004-10-31 02:00:00')
[1] "2004-10-31"
> as.POSIXlt('2004-10-31 03:00:00')
[1] "2004-10-31 03:00:00"
How do I tell as.POSIXlt() to ignore daylight savings and just convert to
2018 Aug 31
2
Segfault when performing match on POSIXlt object
Hi All,
I found a possible unexpected behavior when performing match/%in% on
POSIXlt objects, e.g. :
d <- as.POSIXlt('2018-01-01')
# match(<anything>,<POSIXlt>) --> segfault
match(0,d)
# consequently also this fails :
0 %in% d
REPORTED ERROR ON LINUX:
*** caught segfault ***
address 0x16dc2, cause 'memory not mapped'
Verified on 3.5.0 on linux,
2011 Jan 30
4
Extract time only from POSIXlt object
How can I extract only the time component from an POSIXlt object?
For example if I try the following it still returns both the date and
time...
>as.POSIXlt(tr.date[1])
[1] "2010-10-18 21:46:53"
>as.POSIXlt(tr.date[1],"%H:%M:%S")
[1] "2010-10-18 21:46:53"
round and trunc don't help... is there an "as.Time" equivalent to as.Date
?
Thanks,
2010 Oct 05
2
Subset POSIXlt Field
Hello All
I, for the life of me, can't figure out to subset my dataframe by my Date
field. The field has been formatted as POSIXlt.
str(wild)
......
$ Date : POSIXlt, format: "2010-05-28" "2010-05-28" "2010-05-28" ...
This doesn't work:
test <-subset(wild,ID=="2830" & Date=="2010-08-17")
which returns:
<0 rows> (or
2010 Jul 14
1
POSIXlt error for 1982-01-01
Hi, I am encountering a strange error in POSIXlt... anyone got a clue?
> as.POSIXlt("1982-01-01")
Error in as.POSIXlt.character("1982-01-01") :
character string is not in a standard unambiguous format
> as.POSIXlt("1992-01-01")
[1] "1992-01-01"
> as.POSIXlt("1972-01-01")
[1] "1972-01-01"
> as.POSIXlt("1962-01-01")
2006 Sep 01
3
Date conversion with as.POSIXct and as.POSIXlt (PR#9196)
Full_Name: Erich Neuwirth
Version: 2.3.1
OS: Windows XP, Linux
Submission from: (NULL) (131.130.135.167)
Converting Sys.Date() to a POSIX compliant time type in different ways
produces inconsistent results:
> Sys.date()
[1] "2006-09-01"
> as.POSIXct(Sys.Date())
[1] "2006-09-01 02:00:00 CEST"
> as.POSIXlt(Sys.Date())
[1] "2006-09-01"
>
2016 Dec 06
1
segfault with POSIXlt zone=NULL zone=""
>>>>> Joshua Ulrich <josh.m.ulrich at gmail.com>
>>>>> on Tue, 6 Dec 2016 09:51:16 -0600 writes:
> On Tue, Dec 6, 2016 at 6:37 AM, <frederik at ofb.net> wrote:
>> Hi all,
>>
>> I ran into a segfault while playing with dates.
>>
>> $ R --no-init-file
>> ...
>> >
2010 Jul 14
1
POSIXlt error
Hi, I'm encountering a strange error in POSIXlt... anyone got a clue on
this?
> as.POSIXlt("1982-01-01")
Error in as.POSIXlt.character("1982-01-01") :
character string is not in a standard unambiguous format
> as.POSIXlt("1992-01-01")
[1] "1992-01-01"
> as.POSIXlt("1972-01-01")
[1] "1972-01-01"
>
2008 Feb 17
1
How to make a vector/list/array of POSIXlt object?
Hi Guys,
I'm cooking up my time series code. I want a data frame with first column as timestamp in POSIXlt format.
I hit on this the problem of how to create an array/list/vector of POSIXlt objects. Code is as follows
> dtt=array(dim = 2)
> t=as.POSIXlt( strptime("07/12/07 13:20:01", "%m/%d/%Y %H:%M:%S",tz="GMT"))
> dtt
[1] NA NA
> t
[1]
2004 Oct 05
2
correct my method of estimating mean of two POSIXlt data frames
Hello, I searched the archives but could not come to a solution. I
have to two columns of information
t_start_cdt looks like:
> t_start_cdt[1:4]
[1] "2003-07-09 11:02:25" "2003-07-09 11:10:25" "2003-07-09 11:30:25"
[4] "2003-07-09 12:00:25"
> class(t_start_cdt)
[1] "POSIXt" "POSIXlt"
t_end_cdt looks like:
> t_end_cdt[1:4]
2011 Aug 07
1
all.equal doesn't work for POSIXlt objects
Hi all,
following sample code illustrates the problem :
Date1 <- Date2 <-
as.POSIXlt(seq.Date(as.Date("2010-04-01"),as.Date("2011-04-01"),by='day'))
identical(Date1,Date2)
all.equal(Date1,Date2)
identical() gives the correct answer. As there is no all.equal method
for POSIXlt objects, all.equal.list is used instead. Subsetting using
[[]] doesn't work
2004 Mar 08
5
years from as.POSIXlt
Hi,
how it's possible to extract the year and the number
of days from Julian date. i'm little confused about the last two
functions and ?years .
EDATE comes from sqlQuery with as.is=T
EDATE <- as.POSIXlt(datvears$ENROLLDAY)
Many thanks, Christian
> EDATE[1:5]
[1] "2000-06-30 11:25:01" "2000-06-30 11:39:55" "2000-06-30 12:11:11"
[4]
2011 Mar 08
1
Date arithmetic coerces POSIXlt to POSIXct?
Hi. This feels like a bug to me, or at least an undocumented feature,
but I thought I'd see what people here thought of it. Consider a POSIXlt
object like this one:
> a <- as.POSIXlt ("2011-01-23 12:45:45")
> class (a)
[1] "POSIXlt" "POSIXt"
Fine. Now, if I do some arithmetic on that object, the result is
converted to POSIXct.
> class (a
2012 Jun 15
2
POSIXlt and trunc
Hi,
I'm having trouble understanding how trunc is operating on vectors of
POSIXlt objects. Why does dates[1:4] in the last line return a bunch of NAs
even though dates look like it has all the right elements? This worries me
that something is off with my use of trunc. Is trunc not suppose to be
vectorized with POSIXlt? If not, then how should I truncate a bunch of
POSIXlt objects? I'm
2013 Apr 24
1
Floating point precision causing undesireable behaviour when printing as.POSIXlt times with microseconds?
Dear list,
When using as.POSIXlt with times measured down to microseconds the default format.POSIXlt seems to cause some possibly undesirable behaviour:
According to the code in format.POSIXlt the maximum accuracy of printing fractional seconds is 1 microsecond, but if I do;
options( digits.secs = 6 )
as.POSIXlt( 1.000002 , tz="", origin="1970-01-01")
as.POSIXlt( 1.999998 ,
2010 Jun 15
3
Problem with as.POSIXlt$hour
Hello,
In one of my functions, I need to extract the hour from a date.
For example:
as.POSIXlt("2010-03-27 02:00:00")$hour gives 2 as expected.
It works for all the dates I've tested except the following one which is in
my list of dates:
as.POSIXlt("2010-03-28 02:00:00")$hour which gives 0.
I don't understand why it doesn't work with this particular date.
Any