R-exts says
Both install.R and R_PROFILE.R should be viewed as experimental; the
mechanism to execute code before attaching or installing the package may
change in the near future. With the other facilities available as from R
2.0.0 they should be removed if possible.
Every usage of t
Hi,
I'm currently hunting a bug in the akima library, especially in the code
behind the interpp.old function (bi-variate linear interpolation).
It is based on a triangulation algorithm, interpolation at a given point
needs to know the triangle which contains this point, then the
interpolation is a
After reading my own question once again, I think I can answer it
myself:
The code had too _few_ COMMON blocks. It seems the code relied on that,
that several local variables would carry their values after being
initialised in the first subroutine call until the second call. This is
not the case.
This was never intended to work, but can easily be programmed in.
I have done so for R-devel.
On Wed, 1 Feb 2006 [EMAIL PROTECTED] wrote:
> window() does not work correctly when called with extend=TRUE and
> the new time range intersect null with the old time range! Maybe this is
> really a feat
Should be patched in R-devel, will be available shortly
[EMAIL PROTECTED] wrote:
> Full_Name: Stefan Th. Gries
> Version: 2.2.1
> OS: Windows XP (Home and Professional)
> Submission from: (NULL) (68.6.34.104)
>
>
> The problem is this: I have a vector of two character strings.
>
>
>>text<-c("T
I have been experimenting with different possibilities for an
"introduction" page for my packages. That is, a good place to tell users
about the most important things in a package, and where to start.
Recently there was a discussion about this, and a suggestion to use
-package.Rd, and also a f
Suppose X is a data.frame with n obs and k vars, all variables are
factors.
tab <- table(X)
containes a k-dim array
I would like to get a list from tab. This list is such that, each
element contain the indexes corresponding to the observations which
are in the same cell of this k-dim array
Stefano,
Try this
XX <- as.numeric(X[[1]])
for (i in 2:length(X)) XX <- 10*XX + as.numeric(X[[i]])
split(seq(along=XX), XX)
You can read off the cell from the decimal expansion of the label.
And XX goes from observations to cells.
The hard work is done by unique() under the skin (split makes XX
Apologizies, I forgot the subject.
Btw, I found it
stefano
Il giorno 01/feb/06, alle ore 18:25, stefano iacus ha scritto:
> Suppose X is a data.frame with n obs and k vars, all variables are
> factors.
>
> tab <- table(X)
>
> containes a k-dim array
>
> I would like to get a list from tab. This l
Thanks Brian,
stefano
Il giorno 01/feb/06, alle ore 19:00, Prof Brian Ripley ha scritto:
> Stefano,
>
> Try this
>
> XX <- as.numeric(X[[1]])
> for (i in 2:length(X)) XX <- 10*XX + as.numeric(X[[i]])
> split(seq(along=XX), XX)
>
> You can read off the cell from the decimal expansion of the label.
On 1 Feb 2006, [EMAIL PROTECTED] wrote:
> Every usage of these on CRAN is unnecessary. If you want to save the
> image, say so in the SaveImage field in DESCRIPTION (but why not
> LazyLoad instead?). If you require methods, say so in Depends in
> DESCRIPTION.
I've looked over the packages in the
Hi,
With recent versions of R-devel, "R CMD check" complains about
some "Rd files with unknown sections".
[EMAIL PROTECTED]:~> R CMD check multtest_1.9.4.tar.gz
...
...
* checking Rd files ... WARNING
Rd files with unknown sections:
/home/hpages/multtest.Rcheck/00_pkg_src/multtest/man/boot.res
On Wed, 1 Feb 2006, Herve Pages wrote:
> Hi,
>
>
> With recent versions of R-devel, "R CMD check" complains about
> some "Rd files with unknown sections".
>
> [EMAIL PROTECTED]:~> R CMD check multtest_1.9.4.tar.gz
> ...
> ...
> * checking Rd files ... WARNING
> Rd files with unknown sections:
> /
That's a nice improvement. Thanks!
H.
Prof Brian Ripley wrote:
> On Wed, 1 Feb 2006, Herve Pages wrote:
>
>> With recent versions of R-devel, "R CMD check" complains about
>> some "Rd files with unknown sections".
>
>
> It is new test (thanks to Kurt Hornik). Those are all incorrect, and
> wil
I'm trying to retrieve an unevalated argument (a list in particular).
I can do this easily when I call the function directly:
a1 <- function(x) match.call()$x
> a1(list(y=x^2))
list(y = x^2)
But when the function is called by another function, it gets trickier
b <- function(x, f) f(x)
> b(lis
Why isn't substitute(x, parent.frame()) enough? parse(deparse()) seems
redundant...
Andy
From: hadley wickham
>
> I'm trying to retrieve an unevalated argument (a list in particular).
> I can do this easily when I call the function directly:
>
> a1 <- function(x) match.call()$x
>
> > a1(list
Thanks to Andy Liaw, I have realised my problem isn't getting an
unevaluated argument, my problem really is converting an unevaluted
list to list of unevaluted elements. That is, how can I go from
substitute(list(a=x, b=c))
to
list(a=substitute(x), b=substitute(c))
(I am also interested in a
On Wed, 1 Feb 2006, Seth Falcon wrote:
> On 1 Feb 2006, [EMAIL PROTECTED] wrote:
>> Every usage of these on CRAN is unnecessary. If you want to save the
>> image, say so in the SaveImage field in DESCRIPTION (but why not
>> LazyLoad instead?). If you require methods, say so in Depends in
>> DESC
18 matches
Mail list logo
