On Tue, 11 Apr 2006, John Chambers wrote:
> (diverted to r-devel)
>
> The problem seems to be rather that loading of the saved image takes place
> _after_ the packages are attached. So nothing that the methods package does
> in its initialization will see the relevant type converters or other m
On Wed, 12 Apr 2006, Prof Brian Ripley wrote:
> On Tue, 11 Apr 2006, Simon Urbanek wrote:
>
>> On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
>>
>>> I've been experiencing some interesting stack warnings recently
>>> when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
>>> series. In
On Tue, 11 Apr 2006, Jeffrey Horner wrote:
> Simon Urbanek wrote:
>> On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
>>
>>> I've been experiencing some interesting stack warnings recently
>>> when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
>>> series. In particular, I'm getting wa
On Tue, 11 Apr 2006, Simon Urbanek wrote:
> On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
>
>> I've been experiencing some interesting stack warnings recently
>> when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
>> series. In particular, I'm getting warnings of "Error: C stack
>>
On 4/12/06, Simon Urbanek <[EMAIL PROTECTED]> wrote:
> On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
>
> > I've been experiencing some interesting stack warnings recently
> > when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
> > series. In particular, I'm getting warnings of "Error
Simon Urbanek wrote:
> On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
>
>> I've been experiencing some interesting stack warnings recently
>> when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
>> series. In particular, I'm getting warnings of "Error: C stack
>> usage is too cl
On 4/11/2006 7:45 PM, Dirk Eddelbuettel wrote:
> R-devel'ers,
>
> On 11 April 2006 at 10:24, Dirk Eddelbuettel wrote:
> |
> | Kanru,
> |
> | Thanks for the bugreport.
> |
> | On 11 April 2006 at 22:03, Kanru Chen wrote:
> | | Package: r-base-core
> | | Version: 2.2.1.svn37668-1
> | | Severity:
On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
> I've been experiencing some interesting stack warnings recently
> when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
> series. In particular, I'm getting warnings of "Error: C stack
> usage is too close to the limit" before segf
R-devel'ers,
On 11 April 2006 at 10:24, Dirk Eddelbuettel wrote:
|
| Kanru,
|
| Thanks for the bugreport.
|
| On 11 April 2006 at 22:03, Kanru Chen wrote:
| | Package: r-base-core
| | Version: 2.2.1.svn37668-1
| | Severity: minor
| |
| | In manpage of /usr/bin/R, the first, fourth and last l
Dear Duncan,
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Duncan Murdoch
> Sent: Tuesday, April 11, 2006 3:35 PM
> To: John Fox
> Cc: r-devel@stat.math.ethz.ch
> Subject: Re: [Rd] Setting --sdi in R 2.3.0 beta for Windows
>
> On 4/11/2006 4:02 P
On 4/11/2006 4:02 PM, John Fox wrote:
> Dear r-devel list members,
>
> I find that adding --sdi to the Target field in the short-cut for R is
> ineffective in R 2.3.0 beta for Windows (version/platform details below).
> Setting MDI = no in the Rconsole file works, however.
Thanks, I'll fix that.
On Tue, 11 Apr 2006, A.J. Rossini wrote:
> On 4/11/06, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
>> On Tue, 11 Apr 2006, A.J. Rossini wrote:
>>
>>> I will say this first -- I can't copy/paste the error message from the
>>> screen, so it's being retyped. Errors might occur. SORRY.
>>>
>>> I've
(diverted to r-devel)
The problem seems to be rather that loading of the saved image takes
place _after_ the packages are attached. So nothing that the methods
package does in its initialization will see the relevant type converters
or other methods objects.
More generally, loading into .Glob
On 4/11/06, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Apr 2006, A.J. Rossini wrote:
>
> > I will say this first -- I can't copy/paste the error message from the
> > screen, so it's being retyped. Errors might occur. SORRY.
> >
> > I've been experiencing some interesting stack warn
Dear r-devel list members,
I find that adding --sdi to the Target field in the short-cut for R is
ineffective in R 2.3.0 beta for Windows (version/platform details below).
Setting MDI = no in the Rconsole file works, however.
It's probably a bit late to request this for version 2.3.0, but it wou
Yep, bingo. That's what I'm thinking, too. Except that it's supposed
to be protected at my end.
"Supposed to".
On 4/11/06, Duncan Temple Lang <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> Hi Tony.
> Just to eliminate things, is the host application
> in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tony.
Just to eliminate things, is the host application
in which R is being embedded doing anything with
the stack, e.g. some lisp system playing with threads
via manipulating the stack?
D.
A.J. Rossini wrote:
> I will say this first -- I can
> >>> Currently the `gaussian' family's initialization code signals an error if
> >>> any response data are zero or negative and a log link is used. Given that
> >>> zero or negative response data are perfectly legitimate under the GLM
> >>> fitted using `gaussian("log")', this seems a bit unsatisf
On Apr 8, 2006, at 2:27 PM, Prof Brian Ripley wrote:
> On Sat, 8 Apr 2006, roger koenker wrote:
>
>> For what it is worth, I've just installed R-alpha Version 2.3.0 alpha
>> (2006-04-07 r37668)
>> on my G5 and encountered the same problem reported below. The same
>> treatment
>> got things goin
Kanru,
Thanks for the bugreport.
On 11 April 2006 at 22:03, Kanru Chen wrote:
| Package: r-base-core
| Version: 2.2.1.svn37668-1
| Severity: minor
|
| In manpage of /usr/bin/R, the first, fourth and last line shows `VERSION'
| instead of `R'.
|
| I believe it is a typo.
More likely something i
> > Currently the `gaussian' family's initialization code signals an error if
> > any response data are zero or negative and a log link is used. Given that
> > zero or negative response data are perfectly legitimate under the GLM
> > fitted using `gaussian("log")', this seems a bit unsatisfactory.
On Tue, 11 Apr 2006, Simon Wood wrote:
>>> Currently the `gaussian' family's initialization code signals an error if
>>> any response data are zero or negative and a log link is used. Given that
>>> zero or negative response data are perfectly legitimate under the GLM
>>> fitted using `gaussian("l
On Tue, 11 Apr 2006, Prof Brian Ripley wrote:
> On Tue, 11 Apr 2006, Simon Wood wrote:
>
>> Hi,
>>
>> Currently the `gaussian' family's initialization code signals an error if
>> any response data are zero or negative and a log link is used. Given that
>> zero or negative response data are perfect
On Mon, 10 Apr 2006, Duncan Murdoch wrote:
>
> If it's not dataframes, it will be something else. I think it's highly
> desirable that any(is.na(x)) == anyNA(x) within base packages, and we
> should make it straightforward to maintain this identity in contributed
> packages.
>
> By the way, I thin
On Tue, 11 Apr 2006, Simon Wood wrote:
> Hi,
>
> Currently the `gaussian' family's initialization code signals an error if
> any response data are zero or negative and a log link is used. Given that
> zero or negative response data are perfectly legitimate under the GLM
> fitted using `gaussian("l
Hi,
Currently the `gaussian' family's initialization code signals an error if
any response data are zero or negative and a log link is used. Given that
zero or negative response data are perfectly legitimate under the GLM
fitted using `gaussian("log")', this seems a bit unsatisfactory. Might
it be
This is because baseenv() is special and has neither HASHTAB nor FRAME.
R_lsInternal shows how to treat it, and I will commit a fix shortly.
On Tue, 11 Apr 2006, [EMAIL PROTECTED] wrote:
> eapply() works on most environments, but not on baseenv(). For example,
>
> > x <- 1
> > eapply(globalenv()
On Windows
> Tab
quantile kuantile quantile kuantile qsort
100 0.0030.0030.0000.001 0.000
1000 0.0000.0000.0020.000 0.000
10.0020.0040.0010.004 0.000
1e+050.0080.0060.0160.010 0.018
1e+060.0920.1130.1370.14
On Tue, 11 Apr 2006, Romain Francois wrote:
Le 11.04.2006 14:12, Prof Brian Ripley a écrit :
That's an interesting suggestion, but
1) it is not a good idea to change the order of arguments in a function.
Yes, my mystake. It's because i like to call 'history(something)' directly
and not 'histo
I've recently folded a new version of the Floyd-Rivest quantile
algorithm
for quantiles into my quantreg package. So it is easily available for
comparative testing. On my G5 running last friday's R-devel, I get:
Median Only 5 Quantiles
n quantile kuantile qu
Le 11.04.2006 14:12, Prof Brian Ripley a écrit :
> That's an interesting suggestion, but
>
> 1) it is not a good idea to change the order of arguments in a function.
Yes, my mystake. It's because i like to call 'history(something)'
directly and not 'history(pattern=something)'.
I hadn't in mind th
That's an interesting suggestion, but
1) it is not a good idea to change the order of arguments in a function.
2) is the 'unique' argument useful? I cannot see it being used if
there is no pattern search, nor I do see the merit in showing repeated
lines if I have subselected.
3) like ls(), tes
On 4/11/06, Thomas Lumley <[EMAIL PROTECTED]> wrote:
> On Mon, 10 Apr 2006, Duncan Murdoch wrote:
>
> > On 4/10/2006 7:22 PM, Thomas Lumley wrote:
> >> On Mon, 10 Apr 2006, Henrik Bengtsson wrote:
> >>
> >>> Suggestion 2:
> >>> Create a has.na(x) function to replace any(is.na(x)) that returns TRUE
On 4/11/06, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Apr 2006, A.J. Rossini wrote:
>
> > I will say this first -- I can't copy/paste the error message from the
> > screen, so it's being retyped. Errors might occur. SORRY.
> >
> > I've been experiencing some interesting stack warn
On Tue, 11 Apr 2006, A.J. Rossini wrote:
> I will say this first -- I can't copy/paste the error message from the
> screen, so it's being retyped. Errors might occur. SORRY.
>
> I've been experiencing some interesting stack warnings recently when
> moving from R 2.2.x to the R 2.3.0 series and t
I will say this first -- I can't copy/paste the error message from the
screen, so it's being retyped. Errors might occur. SORRY.
I've been experiencing some interesting stack warnings recently when
moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0 series. In
particular, I'm getting warn
Hi,
Sometimes I need to consult the history of commands that are matching a
regex, so I modified the utils::history function for that purpose. I
found it useful.
I append the code ( I only added the two lines with #**)
Romain.
history2 <-
function (pattern="", max.show = 25, reverse = FALSE,
Hi,
Is there a way to use kcachegrind on R code ?
I mean the R function written in R (not the C, etc ... functions). Has
someone tried to generate "Callgrind profile format" from ouputs of Rprof ?
Romain
--
visit the R Graph Gallery : http://addictedtor.free.fr/graphiques
mixmod 1.7 is release
38 matches
Mail list logo
