As the posting guide asked of you, try R-patched or R-devel before
posting, and check the bug repository.
• smooth.spline() used DUP = FALSE which allowed its compiled C
code to change the function: this was masked by the default
byte-compilation. (PR#14965.)
On 19/09/2012 21:4
Hi Brian --
On 9/19/2012 1:06 PM, brian avants wrote:
hello
we are developing an R package called ANTsR for which we have some special
types.
one of these types is an " antsMatrix " type.
we implemented a "as.data.frame" function that casts an antsMatrix to a
data.frame
this works fine in a
hello
we are developing an R package called ANTsR for which we have some special
types.
one of these types is an " antsMatrix " type.
we implemented a "as.data.frame" function that casts an antsMatrix to a
data.frame
this works fine in a basic shell script. for instance:
# install
R CMD INST
Hi,
example(smooth.spline) fails with the non byte-compiled version of the
smooth.spline function:
> example(smooth.spline)
smth.s> require(graphics)
smth.s> attach(cars)
smth.s> plot(speed, dist, main = "data(cars) & smoothing splines")
[... more output deleted...]
smth.s> li
On 9/19/2012 11:51 AM, Hadley Wickham wrote:
The question becomes: how does information get passed along to indicate
things that may take a long time to run. The discussion so far has focused
on developers setting, or using, some flags to indicate tests and examples
that take a long time. Another
> The question becomes: how does information get passed along to indicate
> things that may take a long time to run. The discussion so far has focused
> on developers setting, or using, some flags to indicate tests and examples
> that take a long time. Another option would be to have the check/buil
On 09/19/2012 09:22 AM, Duncan Murdoch wrote:
I understand the issue with time constraints on checks, and I think there are
discussions
in progress about that. My suggestion has been to put in place a way for a
tester to say
that checks need to be run within a tight time limit, and CRAN as t
( subject changed from Re: [Rd] R-devel Digest, Vol 115, Issue 18 )
I have the impression from this, and previous discussions on the
subject, that package developers and CRAN maintainers are talking at
cross-purposes. Many package maintainers are thinking that they should
be responsible for ch
On 19/09/2012 10:08 AM, Terry Therneau wrote:
> In general, as a package user, I don't want people to be able to
> suppress checks on CRAN. I want things fixed.
>
> So I am pretty sure there won't ever be a reliable "CRAN-detector" put
> into R. It would devalue the brand.
>
> Duncan Murdoch
M
In general, as a package user, I don't want people to be able to
suppress checks on CRAN. I want things fixed.
So I am pretty sure there won't ever be a reliable "CRAN-detector" put
into R. It would devalue the brand.
Duncan Murdoch
My problem is that CRAN demands that I suppress a large fra
Sorry about out of date trip, I appreciate the detailed discussion here and
will fix it soon once I catch up
On Wednesday, September 19, 2012, Roger Bivand wrote:
> On Tue, 18 Sep 2012, Paul Gilbert wrote:
>
>
>> ( A similar problem is also reported by Sebastian P. Luque with
>> library(maptools
On 19.09.2012 02:55, Qi Zhang wrote:
Hi, all.
I was trying to build my R package with R 2.15.1 32bit and win7.
I basically follow the routine in Steven Mosher's blog
http://stevemosher.wordpress.com/step-10-build/
After I fixed the path, and built the skeleton of the package, I started
comma
On 18/09/2012 8:55 PM, Qi Zhang wrote:
Hi, all.
I was trying to build my R package with R 2.15.1 32bit and win7.
I basically follow the routine in Steven Mosher's blog
http://stevemosher.wordpress.com/step-10-build/
After I fixed the path, and built the skeleton of the package, I started
comma
Hi, all.
I was trying to build my R package with R 2.15.1 32bit and win7.
I basically follow the routine in Steven Mosher's blog
http://stevemosher.wordpress.com/step-10-build/
After I fixed the path, and built the skeleton of the package, I started
command prompt and used the following commands
On Tue, 18 Sep 2012, Paul Gilbert wrote:
( A similar problem is also reported by Sebastian P. Luque with
library(maptools)
library(trip)
in the vignette as below ).
Thanks for bringing this up. This is caused by maptools avoiding: Depends:
spatstat, which might create circularities. maptoo
15 matches
Mail list logo