similar to: Clean up after "R CMD INSTALL" and/or "R CMD check"

Displaying 20 results from an estimated 10000 matches similar to: "Clean up after "R CMD INSTALL" and/or "R CMD check""

2004 Oct 07
3
"R CMD check" with R 2.0.0
G'day all, I am not sure whether I should file this as a bug report, but I thought that I should make the developers of R aware of the following feature: I have just installed R 2.0.0 and when I run "R CMD check" on the source of some packages, I noticed that the XXX-examples.ps file contains one page with two graphics overlaid. This seems to happen when the first graphic is
2012 Jan 11
2
Changed behaviour of 'R CMD INSTALL'
G'day all, I found the following snippet in the NEWS file for R 2.14.1: ? R CMD INSTALL will now do a test load for all sub-architectures for which code was compiled (rather than just the primary sub-architecture). This seems to have the following (unintended?) consequence: Most of my machines are running some version of 64-bit Ubuntu and I do not necessarily have all
2010 Oct 10
1
Query about .check_packages_used_in_examples
G'day all, looking at http://cran.at.r-project.org/web/checks/check_results_Sleuth2.html I noticed that r-prerel-* and r-devel-* issue notes. Apparently, now examples are more thoroughly checked by R CMD check and the note pointed out that a package used in the examples was not declared. This was easily fixed by adding 'Suggests: lattice' to the DESCRIPTION file (now this change has
2016 Jan 12
1
Small inaccuracy in the Writing R Extensions manual
G'day Duncan, On Tue, 12 Jan 2016 07:32:05 -0500 Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 11/01/2016 11:59 PM, Berwin A Turlach wrote: > > G'day all, > > > > In Chapter 1.4 (Writing package vignettes) the Writing R Extensions > > manual states: > > > > By default @code{R CMD build} will run @code{Sweave} on all > >
2016 Jan 12
3
Small inaccuracy in the Writing R Extensions manual
G'day all, In Chapter 1.4 (Writing package vignettes) the Writing R Extensions manual states: By default @code{R CMD build} will run @code{Sweave} on all Sweave vignette source files in @file{vignettes}. If @file{Makefile} is found in the vignette source directory, then @code{R CMD build} will try to run @command{make} after the @code{Sweave} runs, otherwise @code{texi2pdf} is run on
2016 Apr 17
2
Building R-patched and R-devel fails
G'day all, probably you have noticed this by now, but I thought I ought to report it. :) My scripts that update the SVN sources for R-patched and R-devel, run `tools/rsync-recommended' (for both) and then install both these versions from scratch failed this morning. Apparently the new version of the recommended package `survival' depends on the recommended package `Matrix', but
2023 May 18
1
suprising behaviour of tryCatch()
G'day Federico, On Wed, 17 May 2023 10:42:17 +0000 "Calboli Federico (LUKE)" <federico.calboli at luke.fi> wrote: > sexsnp = rep(NA, 1750) > for(i in 1:1750){tryCatch(sexsnp[i] = fisher.test(table(data[,3], > data[,i + 38]))$p, error = function(e) print(NA))} Error: unexpected > '=' in "for(i in 1:1750){tryCatch(sexsnp[i] =" Try: R> for(i in
2023 Aug 12
1
geom_smooth
G'day Thomas, On Sat, 12 Aug 2023 04:17:42 +0000 (UTC) Thomas Subia via R-help <r-help at r-project.org> wrote: > Here is my reproducible code for a graph using geom_smooth The call "library(tidyverse)" was missing. :) > I'd like to add a black boundary around the shaded area. I suspect > this can be done with geom_ribbon but I cannot figure this out. Some >
2006 Jul 19
1
Test for equality of coefficients in multivariate multipleregression
Dear Berwin, Simply stacking the problems and treating the resulting observations as independent will give you the correct coefficients, but incorrect coefficient variances and artificially zero covariances. The approach that I suggested originally -- testing a linear hypothesis using the coefficient estimates and covariances from the multivariate linear model -- seems simple enough. For
2006 Feb 18
3
Bug in Sweave? -- scoping problem? (PR#8615)
I have found a strange scoping problem in Sweave. The following Rnw file doesn't produce the same output in Sweave as it does if I produce an R file using Stangle and execute that: \documentclass[12pt]{article} \begin{document} <<R>>= election <- data.frame(A=1:3, B=9:7, C=rep(0,3)) partytotal <- rep(0, ncol(election)) for (i in 1:ncol(election)) { partytotal[i] <-
2020 Feb 08
4
Development version of R fails tests and is not installed
G'day all, I have daily scripts running to install the patched version of the current R version and the development version of R on my linux box (Ubuntu 18.04.4 LTS). The last development version that was successfully compiled and installed was "R Under development (unstable) (2020-01-25 r77715)" on 27 January. Since then the script always fails as a regression test seems to fail.
2010 Oct 29
2
R version 2-12.0 - running as 32 or as 64 bit?
Question: I installed R verison 2-12.0 on my Windows 7 (64 bit) PC. When I was installing it, it did not ask me anything about 32 vs. 64 bit. So, if I run R now - is it running as a 32-bit or a 64-bit? thank you! -- Dimitri Liakhovitski Ninah Consulting www.ninah.com
2017 Aug 03
1
Problem compiling R patched and R devel on Ubuntu
G'day all, since about a week my daily re-compilations of R patched and R devel are falling over, i.e. they stop with an error during "make check" (while building the 32 bit architecture) on my Ubuntu 16.04.3 LTS machine. Specifically, a test in graphics-Ex.R seems to fail and the last lines of graphics-ex.Rout.fail are: > ## Extreme outliers; the "FD" rule would
2024 Feb 16
1
Packages sometimes don't update, but no error or warning is thrown
Hey everyone, Thanks for all the input. It's happening again. This time for the packages "DBI", "parallelly", "segmented", "survival", "V8". So, RStudio shows updates for those and updating them via RStudio leads to this output: ``` > install.packages(c("DBI", "parallelly", "segmented", "survival",
2017 Dec 20
1
Nonlinear regression
G'day Timothy, On Tue, 19 Dec 2017 18:28:00 -0600 Timothy Axberg <axbergtimothy at gmail.com> wrote: > Should I repost the question with reply-all? Nope, we got all from Jeff's post. :) > On Tue, Dec 19, 2017 at 6:13 PM, Jeff Newmiller > <jdnewmil at dcn.davis.ca.us> wrote: > > > You also need to reply-all so the mailing list stays in the loop. > >
2023 Nov 07
1
non-linear regression and root finding
G'day Troels, On Mon, 6 Nov 2023 20:43:10 +0100 Troels Ring <tring at gvdnet.dk> wrote: > Thanks a lot! This was amazing. I'm not sure I see how the conditiion > pK1 < pK2 < pK3 is enforced? One way of enforcing such constraints (well, in finite computer arithemtic only "<=" can be enforced) is to rewrite the parameters as: pK1 = exp(theta1) ##
2016 Apr 17
1
Building R-patched and R-devel fails
On 17.04.2016 11:01, Prof Brian Ripley wrote: > On 17/04/2016 07:25, Berwin A Turlach wrote: >> G'day all, >> >> probably you have noticed this by now, but I thought I ought to report >> it. :) > > Already fixed for Unix by the time this reached me. Since that version > of Survival has been put into 3.2 patched, that also needed its > Makefile.in
2010 Apr 01
2
pdf files in loops
I need to make a bunch of PDF files of histograms. I tried gatelist = unique(mdf$ArrivalGate) for( gate in gatelist) { outfile = paste("../", airport, "/", airport, "taxiHistogram", gate, ".pdf", sep="") pdf(file = outfile, width = 10, height=8, par(lwd=1)) title=paste("Taxi time for Arrival Gate", gate, "by
2019 Mar 05
3
Development version of R fails tests and is not installed
G'day all, I have daily scripts running to install the patched version of the current R version and the development version of R on my linux box (Ubuntu 18.04.2 LTS). The last development version that was successfully compiled and installed was "R Under development (unstable) (2019-02-25 r76159)" on 26 February. Since then the script always fails as a regression test seems to
2010 Apr 08
1
LOGICAL arguments in FORTRAN code
G'day all, I just took over maintenance of the quadprog package from Kurt Hornik and noticed that one of the FORTRAN routines has an argument that is declared to be a LOGICAL. The R code that calls this routine (via the .Fortran interface) passes the argument down wrapped in a call to as.logical(). This was fine (and as documented) under S-Plus 3.4, for which this code was originally