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 (here) I have a handful of not-very-big *.rda files in my data dir, but also a rather large sqlite db. Is R trying to do anything in particular to my data during the install? index or something? Is there anything I can do to make this step go faster? If this were a 1-time install, it wouldn't matter, but since this package is evolving as I'm using it, I find myself constantly needing to tweak some code here, or change something there, and this always requires another round of R CMD INSTALLing ... Is there something I can do to make this cycle turn around quicker? How do you guys deal with growing a package organically during your analyses? For this particular situation, I reckon I can create a separate package for my dataset since its static (and I might do eventually down the road, anyway), but I'm wondering if there are other alternatives. Thanks, -steve -- Steve Lianoglou Graduate Student: Computational Systems Biology | Memorial Sloan-Kettering Cancer Center | Weill Medical College of Cornell University Contact Info: http://cbio.mskcc.org/~lianos/contact
Steve, I can't speak to your exact question, but perhaps suggest a simple alternative. What I do is simply make changes to the .R file containing my code, and use the "source" function to read in the new definitions of my functions while I'm tweaking them. Then, at the end of the day, I do my R CMD INSTALL just once. If you use ESS, this is particularly easy since you can just type C-c C-l to source the current .R file into a running *R* process. Also, see the Examples section of ?source for a function that sources a bunch of files, presumably all the .R files in your package, at once. I hope that might help, Erik -----Original Message----- From: r-help-bounces at r-project.org [mailto:r-help-bounces at r-project.org] On Behalf Of Steve Lianoglou Sent: Tuesday, September 15, 2009 2:08 PM To: R-help at r-project.org Subject: [R] Putting together a constantly evolving package 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 (here) I have a handful of not-very-big *.rda files in my data dir, but also a rather large sqlite db. Is R trying to do anything in particular to my data during the install? index or something? Is there anything I can do to make this step go faster? If this were a 1-time install, it wouldn't matter, but since this package is evolving as I'm using it, I find myself constantly needing to tweak some code here, or change something there, and this always requires another round of R CMD INSTALLing ... Is there something I can do to make this cycle turn around quicker? How do you guys deal with growing a package organically during your analyses? For this particular situation, I reckon I can create a separate package for my dataset since its static (and I might do eventually down the road, anyway), but I'm wondering if there are other alternatives. Thanks, -steve -- Steve Lianoglou Graduate Student: Computational Systems Biology | Memorial Sloan-Kettering Cancer Center | Weill Medical College of Cornell University Contact Info: http://cbio.mskcc.org/~lianos/contact ______________________________________________ R-help at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Hi, Maybe you can put the sqlite database somewhere else in the package, for example: inst/sqlite/data.sqlite and access it like this : db <- system.file( "sqlite", "data.sqlite", package = "YourPackage" ) Romain On 09/15/2009 09:07 PM, Steve Lianoglou wrote:> > 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 > > (here) > > I have a handful of not-very-big *.rda files in my data dir, but also a > rather large sqlite db. > > Is R trying to do anything in particular to my data during the install? > index or something? Is there anything I can do to make this step go faster? > > If this were a 1-time install, it wouldn't matter, but since this > package is evolving as I'm using it, I find myself constantly needing to > tweak some code here, or change something there, and this always > requires another round of R CMD INSTALLing ... > > Is there something I can do to make this cycle turn around quicker? How > do you guys deal with growing a package organically during your analyses? > > For this particular situation, I reckon I can create a separate package > for my dataset since its static (and I might do eventually down the > road, anyway), but I'm wondering if there are other alternatives. > > Thanks, > -steve > > -- > Steve Lianoglou > Graduate Student: Computational Systems Biology > | Memorial Sloan-Kettering Cancer Center > | Weill Medical College of Cornell University > Contact Info: http://cbio.mskcc.org/~lianos/contact-- Romain Francois Professional R Enthusiast +33(0) 6 28 91 30 30 http://romainfrancois.blog.free.fr |- http://tr.im/yw8E : New R package : sos |- http://tr.im/y8y0 : search the graph gallery from R `- http://tr.im/y8wY : new R package : ant
Maybe Matching Threads
- As a package author, is there a way to specify that your package is architecture (x86_64) specific?
- create dataset permanently in package (i.e. default or our own package)
- Need more information about VGLM
- Symbolic eigenvalues and eigenvectors
- Using C code in R