similar to: R package with C code on Windows

Is there any way to store the value of warnings but avoid printing them? A simplified example: > out <- c(0.2,0.3,0.4) > var <- c(2,3,4) > outcome <- glm(out ~ var, family=binomial()) Warning message: non-integer #successes in a binomial glm! in: eval(expr, envir, enclos) I don't like the warning printed, but I would like to be able to check it's value after the

Hi, I'm new to calling C++/C programs from R and am having some trouble getting started. Following Sigal Blay (Simon Fraser University)'s instructions, I have a .c file called "useC1.c": /* useC1.c */ void useC(int *i) { i[0] = 11; } This produces a .o file : "useC1.o" in a specified directory. I then open R, set the proper directory and:

Need way to resize an existing graphics window. This should be applicable across platforms (as part of a package). Context: function1() draws main plot (I'm using grid), function2() adds smaller plot above main plot, but this one can sometimes overflow the original graphics window area. Thanks, Sigal

Dear R-helpers, I am developing a package named LDehatmap. It depends on the "genetics" package and includes two data files and a demo file. When I'm trying to install it, I get the following messages: * Installing *source* package 'LDheatmap' ... ** R ** data ** demo ** help >>> Building/Updating help pages for package 'LDheatmap' Formats: text html

I'm having a very hard time making R CMD check produce a clean check on examples because of the timings inserted into examples by R CMD check. I am getting a difference on every example output caused by timing information being inserted by 'R CMD check'. The current 'Writing R Extensions' manual[1] states on p. 14: If directory tests has a subdirectory Examples

I'm writing a package that successfully calls Java from R using rJava. When R sends my Java function bad data (through .jcall()), I get the error message details (when I run it on a console) and then: Java requested System.exit(1), closing R. Is there a way to call .jcall so that when Java receives bad data, the Java function will exit, but won't take down R with it? Thanks, Sigal

Hi R Gurus! I'm trying to create a test package using the package.skeleton function. I wanted to add some compiled code too. In the src library, I put together a baby subroutine, compiled it and created a test.dll When I use the R cmd build, it works fine. But I get into trouble with the R CMD check section. /home/Desktop/R-2.5.1/bin # ./R CMD check mypkg * checking for working latex ...

Full_Name: David O. Nelson Version: 1.4.1 OS: solaris 2.7 Submission from: (NULL) (128.115.150.74) Putting patterns in .Rbuildignore has no effect when the tar being used is gnu tar (1.13) on solaris 2.7, whilst /usr/sbin/tar works perfectly. TO REPRODUCE: The current directory contains a source package directory ./mypkg... bimini.jgi-psf.org% echo >mypkg/foo bimini.jgi-psf.org% echo

Hi, my name is Paula. Im trying to learn how to build an R package in Windows XP using a simple example which includes a C source code. The foo.c file is located in mypkg/src/foo.c. I used the command Rcmd build --force --binary [pkgpath]. The problem is when I install the zip file in R the function foo doesn?t exist. The result a recieved during the building process is copied below. I really

Dear R-devel, I've noticed that when I place a `NEWS' file in the top-level directory for a package, then do R CMD build mypkg, the file gets included in the .tar.gz file. However, if I do R CMD build --binary mypkg, the `NEWS' file does not get included in the .zip file. Is this intentional? Is there a way I can get such a file included in the pre-compiled package automatically?

Hello, for my small project I would like to organize the data, functions and documentation as a package. I have already created a skeleton directory structure with DESCRIPTION file and put some files in the R, man and data subdirectories. Now I would like to work on the package without calling R CMD build/install after each change. In fact, I do not have the build tools installed yet (I am on

Hello useRs I am trying to build a package for personal use and for making easier working with other people but I keep getting the same error message about the DESCRIPTION file not existing. when trying to install from a source tar.gz file: Error in .read_description(dfile) : file 'C:/Users/Propriétaire/AppData/Local/Temp/RtmpHFMONb/R.INSTALL647a3535/mypkg/DESCRIPTION' does not

Hi: I'm trying to create a package to pass to someone else to use a group of functions with help files. I'm working on Windows XP. Step One: I use the example > ## two functions and two "data sets" : > f <- function(x,y) x+y > g <- function(x,y) x-y > d <- data.frame(a=1, b=2) > e <- rnorm(1000) > >

Dear list, I'm trying to embed OpenBUGS in an R package for use of it on 64-bit Linux. In order to get the CLI working one has to compile C code contained in $OpenBUGS/Manuals/CBugs.html (copied to say CBugs.c) using gcc -m32 -o bugs CBugs.c -ldl I put the OpenBUGS distribution in the ./inst subdirectory of the package root. Where should I now put the CBugs.c and how

Dear friends, I am writing a package that I think may be of interest to many people so I am in the process to build-check-write-thedocumentation for it. I have some questions regarding the "rules" that a package should abide in order to be consistent with the other packages on CRAN. I have read and reread the Writing R extension manual and googled the mailing list and I have found

Greetings: I've installed Rtools, MikTeX, perl, minGW, and HTML Help Workshop, and have succeeded in making, checking (using R CMD check mypkg) then building the simple example package.skeleton(list=c("f","g","d","e"), name="mypkg") R CMD build mypkg produces a tarball. I don't know how to get a zip file. But when I try to Install

Hi, 'R CMD INSTALL mypkg' and 'install.packages(mypkg, repos=NULL)' don't update mypkg help pages when mypkg is a source directory. They only install new help pages if there are some but they leave the already installed pages untouched. So you end up with mixed man pages from different versions of the package :-/ I found no mention of this in 'R CMD INSTALL --help' or

I am building a package say mypkg. Five months ago, when I built the package I got the mypkg manual in pdf format. Today, after making updates, I build the same package, same name, and steps; unfortunately I do not get the manual in pdf format. Rather I get the following message: cd: can't cd to /cygdrive/c/Documents saving output to 'mypkg-manual.pdf' ...Done Could any one

----- Forwarded by Ajay DAS/US/BMNA01 on 05/19/2008 03:11 PM ----- Ajay DAS To: r-help

I wrote an R wrapper function (phylpro) around a C function (Rphylpro). The first time I'm running my function, it runs with no errors. The second time I'm trying to run it, I get an error message with the first argument to .Call garbled. Set up: > dyn.load("Phylpro.so") > source("phylpro.R") > WinHalfWidth<-30 > permReps<-10 > breaks<-c(548,