similar to: testing on platforms, was Fortran error

Hello, my package passes R CMD check without any warnings on my local machine (Mac OS), as well as on Uwe Ligges' Winbuilder. On RForge, however, we sometimes run into problems building the Sweave vignettes. Now here's my question: is it necessary for a CRAN submission that the Sweave vignettes can be compiled on CRAN, or is it possible to provide the (locally compiled) pdf vignette to

I have a question about antialiasing when R generates bitmaps. (This follows a thread on the ggplot2 mailing list.) I mostly use R on Linux, although I sometimes use it in Mac and Windows as well. On Linux, I've found that plotting shapes 15-18 via cairo results in bad-looking output. The points are not antialiased, and they are jagged and misshapen. Plots generated in Windows also aren't

Dear all, winbuilder is down. Given current inspection results and circumstances, I expect a downtime of *at least* 24 hours. This applies to on-demand check services, CRAN check service results and CRAN binary builds for Windows. Best, Uwe Ligges

I received the following email note re: the vcdExtra package > A vcd update has shown that packages TIMP and vcdExtra are not > declaring their dependence on colorspace/MASS: see > > http://cran.r-project.org/web/checks/check_results_vcdExtra.html But, I can't see what to do to avoid this, nor understand what has changed in R devel. Sure enough, CRAN now reports errors in

Hello, I am trying to submit a new package to CRAN. I had checked the packages with R-devel and R-release in windows 7 local and ubuntu 12.04 local. The package has a C file in src folder which successfully compiled in all the cases (there were few trivial warnings). I had submitted the package last week and was asked to resubmit with few changes in the description file. However upon

At office, using the internal LAN at my disposal, I'm having a go at parallel computing - to begin with - with pvm, rpvm & snow. The two boxes are as follows Remote machine uffbsd: CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz (1994.13-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 real memory = 260046848 (248 MB) This machine NbBSD: CPU: Mobile Intel(R)

Ben Bolker gives some reasons why Numerical Recipes may be problematic as a starting point for R codes. CUP did a masterful job of marketing, but the license is restrictive as the links he gives points out. In some tests, I've also noted that some of the algorithms are less than stellar e.g, convergence tests in one or two optimization routines. Should we have a wiki item to help people find

I've recently updated the coxme package, which calls internal routines from the bdsmatrix package.? (It is in fact mentioned as an example of this in the Extensions manual.) The call connections are a blocks like this, one for each of the 9 called C routines. void bdsmatrix_prod4(int nrow,??? int nblock,?? int *bsize, ??????????????????? double *bmat, double *rmat, ??????????????????? int

> On 25 Apr 2015, at 13:11 , Prof J C Nash (U30A) <nashjc at uottawa.ca> wrote: > > Hendrik pointed out it was the parentheses that gave the complaint. > Single quotes and no parentheses seem to satisfy R CMD check. Perhaps > that needs to be in the WRE. Well, it is in ?toTitleCase: ...However, unknown technical terms will be capitalized unless they are single

Hello, As the author of package cts, I hope somebody on this list can kindly help (perhaps off-list) to resolve the build/check issue with package cts for Mac. The error occurred on Mac machines only: http://cran.r-project.org/web/checks/check_results_cts.html. Here is the error message: At line 10 of file machine.f Fortran runtime error: Range error during floating point read The source

Ravi Varadhan and I have been looking at UCMINF to try to identify why it gives occasional (but not reproducible) errors, seemingly on Windows only. There is some suspicion that its use of DBLEPR for finessing the Fortran WRITE() statements may be to blame. While I can find DBLEPR in Venables and Ripley, it doesn't get much mention after about 2000 in the archives, though it is in the R FAQ

Ravi Varadhan and I have been looking at UCMINF to try to identify why it gives occasional (but not reproducible) errors, seemingly on Windows only. There is some suspicion that its use of DBLEPR for finessing the Fortran WRITE() statements may be to blame. While I can find DBLEPR in Venables and Ripley, it doesn't get much mention after about 2000 in the archives, though it is in the R FAQ

I have tried to compile the working Fortran-90 routines (see attachment) to interface them with R. The compiler automatically caled by R CMD command line prints a bunch of error messages (as follows). I think I'm better off translating the Fortran implementation into R ... which is what I hoped I could avoid. Maura host705:Desktop mauede$ R CMD SHLIB ford.f90 gfortran -arch i386

Might this be related to the Linux version? I'm testing on one of our university servers, and they tend to be deprived of regular updates sometimes... (Dirk, sorry for sending you this twice.) > Sys.info() sysname "Linux" release

And remove the cast on the return value of R_GETCCallable. And check that your function is found before using it. #include <R.h> #include <Rinternals.h> #include <R_ext/Rdynload.h> void bdsmatrix_prod4(int nrow, int nblock, int *bsize, double *bmat, double *rmat, int nfrail, double *y) { DL_FUNC fun = NULL; if (fun==NULL)

On 24.04.2015 22:44, Ben Bolker wrote: > Prof J C Nash (U30A <nashjc <at> uottawa.ca> writes: > >> >> I was preparing a fix for a minor glitch in my optimx package and R CMD >> check gave an error that the title was not in title case. > > [snip] to make Gmane happy ... > >> I have found >> >> A Replacement and Extension of the

I am getting the following on CRAN windows and winbuilder https://www.r-project.org/nosvn/R.check/r-devel-windows-ix86+x86_64/penaltyLearning-00check.html Apparently there is an error in re-building vignettes, but I do not have any idea what it is, because all that is listed is three dots (...). Is this a bug in R CMD check? If not, the only solution I can think of is removing the vignette

Has anyone had any luck with moving files outside of /tftpboot? Its been particularly frustrating in my environment to support files within this directory. Especially since I support three different architectures and need to differentiate their boot loaders, kernels, configs, initrd's, etc. I'd really like to symlink off to my AFS space and let the sysname values do the work. Is there a

Dear all, I run R CMD build --compact-vignettes="both" gRbase and/or R CMD build --compact-vignettes="gs+qpdf" gRbase and in the log from r-devel (on winbuilder) I get * checking sizes of PDF files under 'inst/doc' ... WARNING 'gs+qpdf' made some significant size reductions: compacted 'gRbase-arrays.pdf' from 421Kb to 115Kb consider

Dear all, I run R CMD build --compact-vignettes="both" gRbase and/or R CMD build --compact-vignettes="gs+qpdf" gRbase and in the log from r-devel (on winbuilder) I get * checking sizes of PDF files under 'inst/doc' ... WARNING 'gs+qpdf' made some significant size reductions: compacted 'gRbase-arrays.pdf' from 421Kb to 115Kb consider