Displaying 20 results from an estimated 10000 matches similar to: "(PR#8654) failure to read the help carefully!"
2006 Mar 03
1
[as.POSIXlt]: Incorrect conversion only for some specific date/time (PR#8654)
Full_Name: Aziz Chaouch
Version: 2.2.1
OS: XP/2000
Submission from: (NULL) (132.156.89.240)
Hi,
I'm not sure this is a "bug" but here is the problem:
I'm using the function as.POSIXlt to convert character strings into time
objects. I'm using date format as "YYYY/M/D HH:MM" such as as.POSIXlt("1999/6/7
13:30"). Most of the time, this works fine. However
2006 May 12
3
Maximum likelihood estimate of bivariate vonmises-weibulldistribution
Thanks Dimitris!!! That's much clearer now. Still have a lot of work to
do this weekend to understand every bit but your code will prove very
useful.
Cheers,
Aziz
-----Original Message-----
From: Dimitrios Rizopoulos [mailto:Dimitris.Rizopoulos at med.kuleuven.be]
Sent: May 12, 2006 4:35 PM
To: Chaouch, Aziz
Subject: RE: [R] Maximum likelihood estimate of bivariate
2016 Dec 15
2
print.POSIXct doesn't seem to use tz argument, as per its example
On the documentation page for DateTimeClasses, in the Examples section,
there are the following two lines:
format(.leap.seconds) # the leap seconds in your time zone
print(.leap.seconds, tz = "PST8PDT") # and in Seattle's
The second line (using print) seems to ignore the tz argument, and prints
the dates in my time zone, while:
format(.leap.seconds, tz =
2005 Jul 11
0
Sys.timzone() returns NA - problem caused by as.POSIXlt? (PR#8003)
This is not a bug in R: the documentation does say the result is
OS-specific.
`GMT' is a not a proper timezone on Windows, so NA is a valid answer.
(Windows seems to use GMT to refer to the timezone of the UK, e.g.
> Sys.time()
[1] "2005-07-11 07:49:56 GMT Daylight Time"
> Sys.timezone()
[1] "GMT Daylight Time"
although I am in British Summer Time not GMT.)
2016 Dec 16
0
print.POSIXct doesn't seem to use tz argument, as per its example
>>>>> Jennifer Lyon <jennifer.s.lyon at gmail.com>
>>>>> on Thu, 15 Dec 2016 09:33:30 -0700 writes:
> On the documentation page for DateTimeClasses, in the Examples section,
> there are the following two lines:
>
> format(.leap.seconds) # the leap seconds in your time zone
> print(.leap.seconds, tz = "PST8PDT") # and in
2005 Aug 31
1
So-called 'bug' reports PR#8102 and PR#8103
Neither of these have reached me on R-devel (and only PR#8103 is on the
archive), and they seem to be the same error although neither mentions the
other. That's 'odd', to quote one of them.
"EDT" is not a valid POSIX timezone (but, say, EST5EDT is). R's docs are
quite clear that what happens with invalid inputs is system-specific.
(Windows seems often to run home
2003 Aug 04
0
as.POSIXct Bug when used with POSIXlt arg and tz= arg (PR#3646)
Tracking down this bug was joint work with Jermoe Asselin (jerome at
hivnet.ubc.ca) and Patrick Connolly (p.connolly at hortresearch.co.nz). We
collectively were able to determine that this is a problem in both Windows 2000
and in Linux and by testing it in our three time zones that it seems to be
daylight savings time related.
Conversion of POSIXlt datetimes to POSIXct appears to have problems.
2010 Jun 09
0
Fixed sill in variogram fitting (geoR)
Dear all,
I'm trying to fit a variogram model using variofit function in geoR
package. There is an option to fix the nugget but is there anyway to force
the variogram sill to equal some defined value? I'm working with
standardized longitudinal data so the process variance is 1 and I'd like
to force the sill of the variogram to reach this value (and prevent it
from going
2011 Mar 08
0
nlme: Computing REML likelihood value from ML likelihood value
Dear All,
I have a question concerning the computation of the value of the Restricted Maximum Likelihood (REML) function evaluated at a given set of parameter estimates from the Maximum likelihood (ML) value. Following the book of Fitzmaurice, Laird and Ware (2004) "Applied Longitudinal Analysis" pp101, the REML likelihood can be computed by multiplying the ML likleihood by the square
2024 Oct 11
1
Time zones in POSIClt objects
?s 15:13 de 10/10/2024, Jeff Newmiller via R-help escreveu:
> POSIXt vectors do not support different time zones element-to-element.
>
> If you want to keep track of timezones per element, you have to create a vector of timestamps (I would recommend POSIXct using UTC) and a parallel vector of timezone strings. How you manipulate these depends on your use cases, but from R's
2024 Oct 10
1
Time zones in POSIClt objects
Sys.setenv(TZ = "GMT") will set the local time zone to GMT so there
would only be one time
zone regardless of whether local or GMT were used.
On Thu, Oct 10, 2024 at 11:17?AM Jan van der Laan <rhelp at eoos.dds.nl> wrote:
>
> Thanks.
>
> On 10/10/24 16:13, Jeff Newmiller wrote:
> > POSIXt vectors do not support different time zones element-to-element.
>
>
2017 Oct 16
0
Another issue with Sys.timezone
>>>>> Stephen Berman <stephen.berman at gmx.net>
>>>>> on Sun, 15 Oct 2017 01:53:12 +0200 writes:
> (I reported the test failure mentioned below to R-help but was advised
> that this list is the right one to address the issue; in the meantime I
> investigated the matter somewhat more closely, including searching
> recent R-devel
2002 May 03
1
Daylight savings time and conversion to POSIXt (arghh!)
I have asked this question before, and received some suggestions for
work-arounds that get the job done--and they are much appreciated.
But I would still like to find out if I'm missing something, and
whether there is a direct way using POSIXt functions (as.POSIXct,
as.POSIXlt, strptime, in particular).
I have environmental data collected once per minute. Here is a subset
of 3 input
2024 Oct 10
2
Time zones in POSIClt objects
Thanks.
On 10/10/24 16:13, Jeff Newmiller wrote:
> POSIXt vectors do not support different time zones element-to-element.
> I complained about this on this list a couple of decades ago, and was
chastised for it. Evidently handling timezones per element was
considered to be too impractically slow to be a standard feature.
This is where it is unclear to me what the purpose is of the
2017 Oct 19
0
Another issue with Sys.timezone
On Wed, 18 Oct 2017 18:09:41 +0200 Martin Maechler <maechler at stat.math.ethz.ch> wrote:
>>>>>> Martin Maechler <maechler at stat.math.ethz.ch>
>>>>>> on Mon, 16 Oct 2017 19:13:31 +0200 writes:
(I also included a reply to part of this response of yours below.)
>>>>>> Stephen Berman <stephen.berman at gmx.net>
2006 May 11
2
Maximum likelihood estimate of bivariate vonmises-weibull distribution
Hi,
I'm dealing with wind data and I'd like to model their distribution in
order to simulate data to fill-in missing values. Wind direction are
typically following a vonmises distribution and wind speeds follow a
weibull distribution. I'd like to build a joint distribution of
directions and speeds as a VonMises-Weibull bivariate distribution.
First is this a stupid question? I'm
2004 Apr 23
3
time zones in POSIXt
Hi,
I have two data sources. One records time in PST time zone, the other in
GMT. I want to compute the difference between the two, but don't see
how. Here is an example where I compute time difference between
identical times each (meant to be) relative to its time zone.
> as.POSIXlt("2000-05-10 10:15:00", "PST") - as.POSIXlt("2000-05-10
10:15:00",
2024 Oct 10
2
Time zones in POSIClt objects
POSIXt vectors do not support different time zones element-to-element.
If you want to keep track of timezones per element, you have to create a vector of timestamps (I would recommend POSIXct using UTC) and a parallel vector of timezone strings. How you manipulate these depends on your use cases, but from R's perspective you will have to manipulate them element-by-element.
I complained about
2017 May 18
0
[R] R-3.4.0 fails test
> On 18 May 2017, at 14:51, peter dalgaard <pdalgd at gmail.com> wrote:
>
>
>> On 18 May 2017, at 13:47 , Joris Meys <jorismeys at gmail.com> wrote:
>>
>> Correction: Also dlt uses the default timezone, but POSIXlt is not recalculated whereas POSIXct is. Reason for that is the different way values are stored (hours, minutes, seconds as opposed to minutes
2017 May 18
2
[R] R-3.4.0 fails test
> On 18 May 2017, at 14:58 , Martyn Plummer <plummerM at iarc.fr> wrote:
>
>
>
>> On 18 May 2017, at 14:51, peter dalgaard <pdalgd at gmail.com> wrote:
>>
>>
>>> On 18 May 2017, at 13:47 , Joris Meys <jorismeys at gmail.com> wrote:
>>>
>>> Correction: Also dlt uses the default timezone, but POSIXlt is not recalculated