similar to: Windows 7 installation issues

I installed R on my Windows laptop in C:\Program Files\R\R-2.15.2 and am able to open RGUI (640bit), see packages and run commands. However, when I test the installation and run the basic tests and all the tests on the standard and recommended packages i.e.: library("tools") testInstalledBasic("both") testInstalledPackages("base", errorsAreFatal

I have R 2.15.0 running under Windows 7. I installed the igraph 0.5.4 package from a zip file. When I attempt to load igraph using "library(igraph)", I get the error package igraph is not installed for arch=x64.  When I repeat this using the 32-bit version of R, I get the same basic error but with "arch=i386" instead of x64. [[alternative HTML version deleted]]

Dear group, ? When running the installation test: ? testInstalledPackages("both",outDir='c:/Test') ? I got the following message: Running ?testci.R? comparing ?testci.Rout? to ?testci.Rout.save? ... files differ in number of lines: Please note the test does not result in 'OK' as do the other tests.? Is this a concern? Regards, ???-Cody Hamilton

I've run into a number of problems. I'm not sure where they belong, so I thought I'd send it here in hope someone will send them where they do belong. It mostly seems to be either errors in the autoconf input or system header weirdness. There was one genuine compiler bug when compiling saveload.c which google resolved (add "-xunroll=1" ). -liconv is missing from LIBS in

Could someone tell me the difference between igraph and igraph0? I searched the CRAN web site, but cannot find an explantion of the differences. Thanks, Alan [[alternative HTML version deleted]]

I am not experienced at R but have searched the manuals. . . . I have tried placing a setwd command in the Rprofile.site and Rprofile files.  But it does not seem to work.  It always reverts to a particular directory I have been using (saved in workspace image?) for a while.  However, I can print out text from thr Rprofile files! Could this be an issue with confilcts between my workspace/

Hello, I'm writing a script that automates the testing of reverse dependencies of a package. I found the function testInstalledPackage in the tools package, which seems to do what I want. However, when I use it for a source package that was installed with --install-tests, I've noticed that only the actual test files (e.g. located in inst/tests) are available and run. In other words the

Background: I run tools::testInstalledPackage on all packages that dependend on survival (605 as of today) before sending a new release to CRAN. It has a few false positives which I then follow up on.? (Mostly packages with as-yet-incomplete tests in their inst directory). ?Issue: testInstalledPackage("mets")? generates an? "Error in checkVignettes(pkg, lib.loc, latex = FALSE,

Dear all, To create a *.pdf file from a *.Rnw file I do: olddir <- getwd(); setwd(outdir); tryCatch({Sweave("QAReport.Rnw"); tools::texi2pdf("QAReport.tex", clean=TRUE) }, finally = setwd(olddir) ); This works fine, however 'clean=TRUE' does only work when: outdir <-

Hello I am using Sweave to generate some pdf reports using R on a Windows platform and would like to control the output directory that the generated .tex file goes to. Basically I use the following commands in a batch file: set outdir=c:/output/1234 Rscript -e Sweave('C:/pathpathpath/script.Rnw') Which produces script.tex Sweave has the option of specifying an output directory for

... In addition, you may wish to also post on the Bioconductor list for this sort of thing. -- Bert Bert Gunter "The trouble with having an open mind is that people keep coming along and sticking things into it." -- Opus (aka Berkeley Breathed in his "Bloom County" comic strip ) On Thu, May 3, 2018 at 12:58 AM, Spencer Graves <spencer.graves at effectivedefense.org>

hi would you please remove my email from the mailing list. thanks in advance Sebastien [[alternative HTML version deleted]]

Hello, I got some of the R source code and not being able to Run it in RStudio. I get the error: Error in setwd("dir") : cannot change working directory I have gone through forums but nothing seemed relevant to my issue. What bugs me the most is the ("dir") that the error shows, is of those who wrote the source code and not mine(it still sees the directory of their

Hi all. Upon attempting to load the 'JGR' package, on a Win32 machine (SP3), a pop-up message appeared stating that R had encountered a problem and needs to close. Has anyone else encountered this? Thanks. ~Caitlin [[alternative HTML version deleted]]

Dear List, Say I can use getwd() and setwd() to change my working directory. How can I read in all the files within that directory using command line (like a ls() but for the path specified) Regards Ajay Websites- Technology http://decisionstats.com On Wed, Jul 4, 2012 at 3:30 PM, <r-help-request@r-project.org> wrote: > r-help@r-project.org [[alternative HTML version deleted]]

On the Mac it's pretty easy to get to a USB drive by name. For example the following command works if you have a USB drive named "MYUSB" setwd('/Volumes/MYUSB') Is there a way to do the same thing in Windows (without knowing the drive letter)? Thanks! [[alternative HTML version deleted]]

Hi. I am having trouble with something that should be simple. I am unable to get sprintf using escape sequences: > sprintf("a\nb") [1] "a\nb" > sprintf("a\"bc\"d") [1] "a\"bc\"d" But it seems to need them any way: > sprintf("a\"bc"d") Error: unexpected symbol in "sprintf("a\"bc"d"

Full_Name: Enrico Pegoraro Version: 2.7.2 OS: Windows (Vista or Xp PRO) Italian Submission from: (NULL) (87.4.189.202) If you send these lines of code: outdir="c:/pippo" file.path(outdir,"pluto.html") R replies correctly: [1] "c:/pippo/pluto.html" But if you change the first steps to: outdir="" file.path(outdir,"pluto.html") R replies

For 'R CMD check', it appears that option '--outdir' is not recognized and generates warning "unknown option '--outdir'". R CMD check --help says: Usage: R CMD check [options] pkgs [...] Options: [...] -o, --outdir=DIR directory used for logfiles, R output, etc. (default is 'pkg.Rcheck' in current directory,

On 5/3/16 11:29 AM, Thierry Onkelinx wrote: > Dear Mick, > > Note that both knitr and rmarkdown are listed under Suggests: both are > required to compile the vignette. Installing rmarkdown should solve > the problem. If not, please provide more information. OS, R version, > digest version, ... > > This is occurring in the context of an automated testing environment that