search for: rpackages

...art writing any code. S4 introduced a file .S.chapters which can contain a list of S chapters (equivalent to R packages) to be loaded on start-up. This was the germ of this proposal. Proposal: Extend the initialization as described in Startup.Rd by having optionally files named, say, R_HOME/etc/Rpackages.site and .Rpackages, the latter in the starting directory or failing that the user's home directory. Each would contain a list of packages, one per line, to be loaded when R is started, in the order in the files. Some details: 1) I think the packages should be loaded before .Rprofile and .RDa...

Hello, I am using EC2 to launch several instances. On each instance, I perform the following commands yum -y install R (installs R-2.6) R CMD javareconf sleep 10 wget rpackage.tgz R CMD INSTALL rpackage.tgz Now, rpackage.tgz needs to be built with jni libraries. When the instance is fully up, i log in and check if rpackage was successfully installed and find out it wasn't. Running R CMD

Dear All, I have been working on building a new version of the Wavethresh package for some time now. Having build a working version on Linux, I am getting the following error when checking on Windows: C:\Rpackages\R\rw2000\bin>Rcmd check wavethresh * checking for working latex ... OK * using log directory 'C:/Rpackages/R/rw2000/bin/wavethresh.Rcheck' * checking for file 'wavethresh/DESCRIPTION' ... OK * checking if this is a source package ... OK installing R.css in C:/Rpackages/R/rw2000/...

> 4) One problem with saving an R session and then restoring it is that > the packages in use are not reloaded. Quitting an R session and > saving could write .Rpackages in the current directory (with the > library recorded if it were not the default). Then restarting a > session in that directory would restore the loaded packages > automatically. I've been using another approach for this. For the R + Zope tools that I've developed he...

...and citation of every R package mentioned, and it is a pain to create these manually, no less maintain them for current versions. The result of that query was a function, Rpackage.bibs() by Achim Zeileis that I have been using ever since. Code in: http://euclid.psych.yorku.ca/SCS/Private/Rbibs/Rpackages.bib.R On one current system I get the following: > Rpackage.bibs(file="Rpackages-R.2.11.1.bib") Converted 230 of 230 package citations to BibTex Results written to file Rpackages-R.2.11.1.bib Warning messages: 1: In citation(x) : no date field in DESCRIPTION file of package 'code...

Lately I've been doing some work with the manipulateWidget package, which lives on Github at https://github.com/rte-antares-rpackage/manipulateWidget/. Last week I found a bug, so being a good community member, I put together a patch. Since the package lives on Github, I followed instructions to put together a "pull request": - I forked the main branch to my own Github account

...with the standard package structure. I can set the repository in the directory that contains my R packages, but then I have a single repository for all of my packages, which is not ideal. Of course, I could add one extra layer of directory structure (for example, if a package foo sit in directory RPackages/foo I could move it to directory RPackages/foo/foo and set the repository in RPackages/foo) but this seems roundabout and inelegant... I'd be grateful for any suggestions/pointers. Thanks, Peter

...with the standard package structure. I can set the repository in the directory that contains my R packages, but then I have a single repository for all of my packages, which is not ideal. Of course, I could add one extra layer of directory structure (for example, if a package foo sit in directory RPackages/foo I could move it to directory RPackages/foo/foo and set the repository in RPackages/foo) but this seems roundabout and inelegant... I'd be grateful for any suggestions/pointers. Thanks, Peter

Dear all, When running function 'testQAReport()', which uses function 'buildVignettes()' to create a pdf-file I get the following error: > source("testQAReport.R") > testQAReport() Error in .get_package_metadata(pkgdir) : Files 'DESCRIPTION' and 'DESCRIPTION.in' are missing. Since I did not get this error in earlier versions of R, could you

Please, is there anyone who can give me some suggestions? (1) I have to use a package from R on my work. The package is the "quantreg" developed by Koenker (Uni Illinois). I have installed the package in the R library tree /usr/local/lib/R/ library of my Linux Operating System. I did R CMD INSTALL -l /usr/local/lib/R/ library /path/to/quantreg_x.y-z.tar.gz. However, when I call any

...function no longer generates keys for packages which contain *more than one citation*. I've tried debugging with browser(), but can't figure out how to make the lines around FIXME work. Can someone help? You can see the result from this at http://euclid.psych.yorku.ca/SCS/Private/Rbibs/Rpackages-2.14.0.bib The function is also at: # Original code by Achim Zeileis, 16 Dec 2009, R-help # Added: support header and preamble Rpackages.bib <- function(filename = paste("Rpackages-",getRversion(), ".bib", sep=""), header=TRUE, preamble=NULL, suppress.wa...

...I dont have to carry duplicate copies around to wherever I fire up an R sesssion. However, I have problems locating the help files for those functions. Here are some details. I created the library "myR" and installed this in /home/royle/R using: R INSTALL -l /home/royle/R /home/royle/Rpackages/myR This went well, and I can access all of those functions in the usual way....i.e. like: library(myR,lib.loc="/home/royle/R/") But, I found that to get the help files I have to type: help(interp,lib.loc="/home/royle/R/") and so it is kind of a pain to have to specify t...

...I dont have to carry duplicate copies around to wherever I fire up an R sesssion. However, I have problems locating the help files for those functions. Here are some details. I created the library "myR" and installed this in /home/royle/R using: R INSTALL -l /home/royle/R /home/royle/Rpackages/myR This went well, and I can access all of those functions in the usual way....i.e. like: library(myR,lib.loc="/home/royle/R/") But, I found that to get the help files I have to type: help(interp,lib.loc="/home/royle/R/") and so it is kind of a pain to have to specify t...

On 24/01/2018 6:35 PM, G?bor Cs?rdi wrote: > When you create a branch for your bug fix, don't create it off the > previous fix. Create it off the original, forked state of the repo. Branches keepclass2 through to keepclass5 are my attempts to do that. As far as I can see they are all the same as keepclass, which was branched from the head of the master branch of my fork. > >

Hi, I'm trying to build R-2.3.1 on windows, but make gives me following error while building pkg-base: ---------- Making package base ------------ adding build stamp to DESCRIPTION make[4]: *** [frontmatter] Error 1 make[3]: *** [all] Error 2 make[2]: *** [pkg-base] Error 2 make[1]: *** [rpackage] Error 2 make: *** [all] Error 2 Please note that R.exe, Rterm.exe, Rgui.exe, RCmd.exe are

...nf CYGWIN environment variable option "nodosfilewarning" turns off this warning. Consult the user's guide for more details about POSIX paths: http://cygwin.com/cygwin-ug-net/using.html#using-pathnames ERROR: compilation failed for package 'mypackage' * removing 'C:/Rpackages/mypackage.Rcheck/mypackage'. What I understood from above is that it is something with PATH variable. I had set the following PATH variable: C:\Rtools\bin;C:\Rtools\MinGW\bin;"C:\Program Files\R\R-2.13.0\bin";"C:\Program Files\MiKTeX 2.9\miktex\bin";%SystemRoot%\system32;%S...

Hi All, I am trying to make R package using R 2.6.2 And I am getting following error. When I give R CMD check t1\ ---------- Making package t1 ------------ adding build stamp to DESCRIPTION making DLL ... making CGHseg_rewrite.d from CGHseg_rewrite.c making rowMedians.d from rowMedians.c making runavg.d from runavg.c gcc-sjlj -std=gnu99 -Ic:/R/R-2.6.2/include -O3 -Wall -c

When compiling R on Windows, I am getting the following error. Does anyone have any suggestions? ---------- Making package datasets ------------ adding build stamp to DESCRIPTION installing R files installing data files preparing package datasets for lazy data loading Error in load(zfile, envir = envir) : input has been corrupted, with LF replaced by CR Execution halted make[4]: ***

On 25/01/2018 2:57 AM, I?aki ?car wrote: > For what it's worth, this is my workflow: > > 1. Get a fork. > 2. From the master branch, create a new branch called fix-[something]. > 3. Put together the stuff there, commit, push and open a PR. > 4. Checkout master and repeat from 2 to submit another patch. > > Sometimes, I forget the step of creating the new branch and I

I'm attempting to build an R package for distribution and am working from the directions found at http://www.maths.bris.ac.uk/~maman/computerstuff/Rhelp/Rpackages.html#Wi n-Win I've read through Writing R Extensions and various other "helpful" web sites. I've installed all relevant software (perl, cygwin, mingwin, hhc.exe). Here is what I have done so far: 1) Sourced data and functions into R 2) Used package.skeleton 3) Edited Description...