similar to: create dataset permanently in package (i.e. default or our own package)

Our Query: Actually while opening R console and R commander we see some packages like car and datasets. In these packages we have default datasets. For example: "Women" and "Prestige" so on. Now we created a "Sales" dataset importing either from excel, xml or text file. Now we are trying to store that dataset permanently in any one of the packages mentioned above

Hi all, I'm putting together some common code + data into a custom package, everything is working out fine, but the ``R CMD INSTALL MyPackage`` call seems to take a particularly long time in the "**data" step: $ R CMD INSTALL MyPackage/ * installing to library ?/Library/Frameworks/R.framework/Resources/ library? * installing *source* package ? MyPackage? ... ** R ** data

I have been using delay() quite successfully to 'load on reference' some large data files (earthquake catalogues). One minor difficulty I have not been able to overcome is that upon first reference, the data set is loaded into memory as expected, but also remains as a permanent object in the user's environment, instead of appearing to be only in the library from which it was loaded.

Hola! I am writing a package with some large data files, so it would be good to use the feature of zipping data. However, I use .R files to read in the data from one (sometimes more) files, so Rcmd build --zip-data gives a package which does'nt work. How should I do it, is it better ti zip each data file individually and use the functions to read from zipped files, or are there some other

I can't tell from the docs ("Writing R Extensions" 1.9.1) exactly what environment the tests, examples, and vignettes that R CMD check tries to run are in. In particular: 1) how do I get the package loaded? 2) how do I access data in the data/ directory? 3) where is the material in the other directories? (e.g., has inst/ material been installed? where?) Apparently (section 1.3)

Hi Yan, Before I try to answer your question: please send R questions to the r- help mailing list (cc'd here). You will likely get your answer more quickly (since I'm not the only one looking at it) and it might help other people who get stuck on a similar situation by finding the answer on a public forum (just like you did). On Sep 8, 2009, at 5:44 AM, Yan Hui wrote: > Dear

Dear List, I would like to include a couple of objects in a package I am developing and I don't really get it yet. The objects should be available after package load as some functions depend on it. I tried the following: 1) Bundling all objects that I need in the file '/R/sysdata.rda' as described in the "Writing R Extensions" manual on page 7 2)

Hi I have a package which was built using R 1.9.1 and everything worked fine. I recently upgraded to R 2.0.1 and tried to re-install my package - and I got: Error in library(mypackage) : 'mypackage' is not a valid package -- installed < 2.0.0? So I tried rebuilding it using my new version of R: R CMD BUILD --binary mypackage hhc: not found cp: cannot stat `mypackage.chm': No

Function/file names are hypothetical. Say I have written myfunction.R, which calls myfunction.c via .C("myfunction", ...). I've compiled successfully myfunction.c via R CMD SHLIB myfunction.c in the terminal. Then, in the R console: dyn.load("myfunction.so") source("myfunction.R") test <- myfunction() # works fine So everything is in order, myfunction works

Hello. I have what I know to be a simple question, but never having done anything like this it is pretty tough. I'm trying to write an R package. I have a collection of functions that I loaded into R and then used package.skeleton(). After editing everything in the resulting folder, call it NewPackage, I tried to follow along with some instructions I found for Windows users. I installed

I have some questions about 1. nomenclature, 2. recommended file locations and 3. overall procedure related to creating packages. To the extent that it matters, examples here relate to Windows XP R 2.0.1 beta. The questions are interspersed and prefaced with ***. My understanding is that there are actually 6 forms of a package that one should use in package development: 1.

Dear friends, I am building an R package called *mypackage*. I followed every possible steps (to my understanding) for the same. I got following problem while doing *R CMD check mypackage*. * installing *source* package 'mypackage' ... ** libs cygwin warning: MS-DOS style path detected: C:/PROGRA~1/R/R-213~1.0/etc/i386/Makeconf Preferred POSIX equivalent is:

Hey R-users, I think I followed the steps but still couldn't figure this out.. I am creating a personal package and I want to include several datasets in the package. I created a subdirectory 'data' in the package, save a dataset 'test.rda' there, built the package, checked it, installed it. Then I loaded the package and tried load(test), data(test), attach(test), none of them

Dear all I noticed from NEWS 2.11.0,dev SIGNIFICANT USER-VISIBLE CHANGES o Packages must have been installed under R 2.10.0 or later, as the current help system is the only one now supported. So I tried to follow instructions in manual, Duncan Murdoch presentation and help pages to prepare and accomplish installation of a set of functions I use. However in R 2.11.0dev and too in

I'm putting together an R package. I would like to show example code in the vignette, where example data files (included in the package) are used to generate an (example) output file. I read about using example data in Hadley Wickham's post ( http://r-pkgs.had.co.nz/data.html), and believe I should keep my example data as raw data, as it must be parsed to generate the output. So, I

Hi, I need to link mypackage to 2 other packages so I can call some C functions defined in these 2 packages from mine. I've tried Depends: packageA, packageB LinkingTo: packageA, packageB as suggested by the "5.4 Registering native routines" section of the "Writing R Extensions" manual but then only packageA is seen at compilation time (gcc is called with

I have question regarding package installation. What is the difference between check, INSTALL, build and build --binary, which imply which and what order does one normally perform them? I have been trying: R CMD build /mypackage R CMD check /mypackage R CMD build --binary /mypackage in that order but wanted to check that this is right. Also, what portion of the check process can be run

Hi I found yum-downloadonly and executed my command do that and save the dependencies in my current directory. Now when I execute my command: rpm -i mypackage all the dependencies are not found even though they are in the current directory. if I do a "yum install mypackage" (and its in the current directory) its not found either. How do I now install the mypackage in the current

When I run the following: cd \Rpkgs rcmd install mypackage -l library I get a message that it cannot find quadprog which is a library that mypackage depends on. Error: package 'quadprog' could not be loaded I previously used C:\Program Files\R\rw2011\library as my library for CRAN packages and did not have a problem but now that I use C:\Program Files\R\library this problem

Dear List, I’m doing my first baby steps towards developing own R Packages and ran into the following problem: R CMD check mypackage works fine (no errors, no warnings) R CMD build mypackage works fine (no errors, no warnings) R CMD INSTALL –library=”C:\R\R-2.11.1\library” “something\mypackage\mypackage_1.0.tar.gz” works fine (no errors, no warnings) However, when I try loading the