similar to: Advice interfacing to an imaging library

Hi All, I've done some work recently making some of our image analysis library callable from R and Splus. Most of the C image functions use an abstract data type, and R only sees a pointer to this. All memory allocation is done by the library. This leads to some interesting problems. I'm interested in your views about possible solutions. 1) assignment. something like a<-b, where a and

Hi, I've been developing an image analysis package based on R for a while now and I've had problems relating to garbage collection, so it with great interest that I've noticed the work done by Luke Tierney in this area, and I'd like to discuss how best to fit it into my package. I'll start with how my package is structured - an image is represented by an integer with a class

Hello, I think this is a bug, although it is possible that I'm doind something silly. I want to be able to determine the argument name for variables passed to a generic print function suppose we have print.foo <- function(x, ...) { nm<-deparse(substitute(x)) cat("param name is ", nm, "\n") } d<-structure(1, class="foo") Under R-1.2.[2,3] >

Hi, I've found that the default options of gcc and g77 on alpha produce an executable that suffers from floating exceptions. There seems to be a problem with the configure scripts that prevents the --with-f77 option working correctly. The configure script tests that f77 is running by attempting to compile and link a dummy program - the link step seems broken on the alpha (it doesn't like

Hi, I've been using Rprintf from a shared library compiled under various unix flavour for a while now. I get a warning about Rprintf being undefined when constructing the library, but everything works OK after loading. I've also been cross compiling the same library using the mingw32 tools for a while now, but the inclusion of Rprintf seems to be messing up this process. It can't

Hi everyone, I've had no success compiling recent version of R for the Alpha. I know there is a binary distribution, but I don't have root access to my machine. The compiler options mentioned in one of the older distributions dont seem to work anymore. Can anyone provide any guidance. machine details are OSF1 bondi V4.0 878 alpha -- Richard Beare Richard.Beare at cmis.csiro.au

Hi, this relates to my earlier message about external references and finalizers. I was experimenting over the weekend and now suspect that the appropriate solution to my problem will be to have a special case in the code that handles the .C call so that external references are handled appropriately - I guess that a pointer to the reference should be passed to the C code. As I've never

While termplot is under discussion, here's another proposal. I'd like to change the default for partial.resid to TRUE, and for smooth to panel.smooth. I'd be surprised if those changes were to break existing code. John Maindonald email: john.maindonald at anu.edu.au phone : +61 2 (6125)3473 fax : +61 2(6125)5549 Centre for Mathematics & Its Applications, Room

On 7/17/19 8:40 AM, Eric Blake wrote: > > It may be possible in rare situations that the libnbd state machine can > send() the command AND see data ready to recv() (perhaps from a previous > command still in flight), where it ends up read()ing until blocking and > happens to get the server's reply to this command and fire off the > callback, all prior to the

I found writing the following default method the for the generic function "julian" causes R to crash. julian.default <- function(x, ...) { x <- as.Date(x) NextMethod("julian", x, ...) } Here is a test example > m <- as.Date("1972-09-27") + 0:10 > m [1] "1972-09-27" "1972-09-28" "1972-09-29"

I see Peter has just announced the release of 1.0.0, on time, even here in Australia, in accordance with a timetable privately announced about 6 months ago. At that time it seemed optimistic to put it mildly. I am not a member of the core team, but as an ordinary user of R with a more privileged inside view than most I'd like to offer my personal congratulations and thanks. This is the

On Mon, Mar 6, 2017 at 8:21 PM, Richard Beare <richard.beare at gmail.com> wrote: > Yep - simpleITK is available at github.com/SimpleITK/SimpleITK. There's > also github.com/SimpleITK/SimpleITKRInstaller - a devtools based installer > for mac and linux. > > CMake has a range of build environments. I experimented with MSYS2 and > mingw makefiles, but had trouble with

Hi, The following function use to work, but now it doesn't giving the error "> CallSnow(, 100) Using snow package, asking for 2 nodes 2 slaves are spawned successfully. 0 failed. Error in checkForRemoteErrors(val) : 2 nodes produced errors; first error: no applicable method for 'lapply' applied to an object of class "list" ". Where this is the

My apologies for he very short time before things close, but it's not my fault. If necessary get your hat in the ring by Friday and see to the niceties later, may I suggest. This is a vacancy in my group in Cleveland. The work is interesting and the challenges large. Bill Venables. ---------------------------------------------------------------------------- Division of Marine Research

On Mon, Mar 6, 2017 at 6:33 AM, Richard Beare <richard.beare at gmail.com> wrote: > I am working on the SimpleITK package for R. This is an enormous package > that is largely automatically generated via a set of swig/json/lua magic, > and is working well under linux and osx. Is it available somewhere so we can try it? > However we're having a lot of trouble with the

Brian, Thanks for doing this. As the primary author, could I have a desk copy, please? Bill Venables. Bill Venables, CMIS, CSIRO Marine Laboratories, PO Box 120, Cleveland, Qld. 4163 AUSTRALIA Phone: +61 7 3826 7251 Fax: +61 7 3826 7304 Mobile: +61 419 634 642 <mailto: Bill.Venables at csiro.au> http://www.cmis.csiro.au/bill.venables/ -----Original Message----- From: Brian

I seem to have unwittingly stirred up a hornets' nest here, so let me have one more say and leave it. Firstly, congratulations to Renaud Launcelot, who seems to have a better feel for wryness and irony in English than some of my native speaker colleagues. Of course R A Fisher is a seminal writer, indeed close to the founder of modern statistics and every aspiring statistician should read

> I think we should get rid of source attributes completely, > since they are no longer needed, but your comment still > applies to source references. We should strip them when code > gets modified. > > Duncan Murdoch I would be very concerned about losing source attributes-- it would break a lot of my code :(! It's very useful to have a single portable R object that

I recently took "." off my PATH for security reasons and now find that R does not work in my home directory where the .Renviron file resides. The fix is simple. In the R shell startup section replace ". .Renviron" by ". ./.Renviron". The relevant section is: # Startup if ${USE_R_ENVIRON}; then # use the one in current dir, or default if [ -r .Renviron ] then .

If you would like a 10 second R puzzle, you might like to think about this one: > g <- expand.grid(long = 130:140, lat = -(10:25)) > gp <- transform(g, x = long, y = lat) Error in transform(g, x = long, y = lat) : object "long" not found I don't expect this hasn't come up before, but I can't find mention of it. I suggest that to minimise this little