similar to: compiling under windows

SAS has something called the "cubic criterion" cutoff for finding the most appropriate number of clusters. Does R have anything that would replicate that? I've been searching the lists and can't seem to find anything that would point me in the right direction. Thank in advance, Philip Bermingham

SAS Enterprise Miner recommendeds to standardize using X / STDEV(X) versus [X ? mean(X)] / STDEV(X) Any thoughts on this? Pros Cons Philip

Hi All, is there any general advice about speeding up recursive functions (not mentioning 'don't use them')? Regards, Federico Calboli -- Federico C. F. Calboli Department of Epidemiology and Public Health Imperial College, St. Mary's Campus Norfolk Place, London W2 1PG Tel +44 (0)20 75941602 Fax +44 (0)20 75943193 f.calboli [.a.t] imperial.ac.uk f.calboli [.a.t]

Hello, I am trying to compile ROracle _0.5-4 under R 1.9.0 without much success. I am running Windows 2000 SP4, Visual C++ 6.0 SP6, and Oracle client 9.2.0.1.0. I was able to run the pre-compiled version of ROracle_0.5-2 under R 1.7.1, but does not work on R 1.8.1 or R 1.9.0. Here is the output from nmake: C:\Program Files\R\rw1090\library\ROracle\src>nmake Microsoft (R) Program

I'm hoping someone can help me. I have downloaded the proj4R.zip and under my version of R (2.3.1) I install the package from local zip file. This worked great. I then type library(proj4R) to load the library and I get the error: Error in library(proj4R) : 'proj4R' is not a valid package -- installed < 2.0.0? I have read through the install documentation and have downloaded and

We are trying to compile and run the ttest.c example that comes with R (in C:\Program Files\R\rw1081\src\library\windlgs\src\ttest.c). After compiling it with MS Visual C++ we load the DLL with dyn.load. So far it seems good, but when we try to call it from R (after running C:\Program Files\R\rw1081\src\library\windlgs\R\windlgs.R) R crashes. We have tried changing the exports from DLL but have

I'd like to make MikTeX the default TeX package in 2.2.0, but we still need to let people use other packages. The problem is that MikTeX wants a command line option --include-directory $R_HOME/share/texmf, while other packages specify includes via environment variables, and barf when they see the unexpected option. The choice should be controlled by the user's settings in the MkRules

As the build process, especially for Windows, is changing significantly for R 3.2.0, I am trying to build R-devel in preparation. When running `make rinstaller`, I get the following error: cp -p ../../../etc/x64/Makeconf R-devel/etc/x64 mkdir -p R-devel/doc cp -p ../../../doc/CRAN_mirrors.csv R-devel/doc mkdir -p R-devel/doc/manual/images cp -pR ../../../doc/html R-devel/doc

Dear All, I have a pair of .cpp and .def file can be compiled using VC++ and works perfectly well in S-PLUS. I wanted to do the same for R; so I followed the guidline given in "Building from a source-code library under Windows" as much as possible and manage to compile them using VC++ and call it from R. But it gives different answer from the one called from S-Plus. I know that I did

Hello, When compiling R-2.0.0 for cross-compiling, I get the following error when calling 'make R' ---------- Making package base ------------ adding build stamp to DESCRIPTION /bin/sh: line 1: --vanilla: command not found make[5]: *** [frontmatter] Erro 127 make[4]: *** [all] Erro 2 make[3]: *** [pkg-base] Erro 2 make[2]: *** [rpackage] Erro 2 make[1]: *** [all] Erro 2 make[1]:

Ok, one last try. R1.2.0, WinNT 4.0: [R is installed in: R_HOME=D:\Programme\R\rw1020] Can anyone give a hint what the following error message (when running Rcmd INSTALL) means and what to do about it? cd D:\Programme\R\rw1020\src\library D:\Programme\R\rw1020\bin\rcmd install testfunctions make: Entering directory `/cygdrive/d/Programme/R/rw1020/src/gnuwin32' dlltool -k --as as --dllname

I am not sure if this is already known. I checked BUGS and found some references to similar behavior when R_HOME is set? Here is what I get: (1) Fresh build of 1.4.1 under Linux/RH-7.2. All tests pass. > R CMD check ctest * checking for working latex ... OK * using log directory `/home/andyj/stat/R-1.4.1/library/ctest.Rcheck' Installing *source* package `ctest'

I am trying to build R under 64bit Windows7. I am using a fresh install of Rtools34 and R-patched_2016-07-05. I am getting the following error: C:/Rtools/mingw_64/bin/gcc -shared -s -static-libgcc -o tcltk.dll tmp.def init.o tcltk.o tcltk_win.o ../../../gnuwin32/dllversion.o -L../../../../Tcl/bin64 -ltc l85 -ltk85 -LC:/R/RLocalSoft/lib/x64 -LC:/R/RLocalSoft/lib -L../../../../bin/x64 -lR

The make variable $(R_SHARE_DIR) seems to be available for use in tests/Makefile when running under Linux, but not Windows (R-2.6.2, R-2.6.1, R-2.7.0 alpha 2008-04-06, under Windows XP 64 bit, built locally for 32 bit). Is this intentional, or an oversight? Is it OK to use $(R_HOME)/share instead (seems to work OK)? I notice the following in /src/gnuwin32/front-ends/rcmdfn.c (from R-alpha

Hello, I am using cygwin (latest version) and I managed to generate a dll partly with rcmd shlib although there was a problem with both the resouce file (I had to remove "FILEOS VOS__WINDOWS32") and the command line for gcc (--shared is not supported for instance). So I would like to know which compiler/environment you advise to use for windows OS. Then I could load the library in R

Dear r-helpers, I have been trying to invoke R from Java in a Windows 2000 computer (unfortunately). All my environment variables seem to be properly set, everything seems to be in order, but I obtaining a Fatal error: unable to open the base package error window. Also, the output of the invoker is Loading RInterpreter library R_HOME: R_HOME=C:/Programas/R RVersion: R_VERSION=1.6.1 whereas

I am attempting to build a customized R installer on Windows, using the Inno Setup installer. I am following the instructions in Section 3.1.8 of the R Installation and Administration Manual ("Building the Inno Setup installer"), which includes the following passage: An alternative way to customize the installer starting with a binary distribution is to first make a full

Dear R-help, I'm having problem creating a dll using Rcmd SHLIB with R-1.3.1 on WinNT4: C:\TEMP>Rcmd SHLIB tryf.o make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. C:\TEMP>Rcmd SHLIB tryf.f make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. I

Dear R-help, I'm having problem creating a dll using Rcmd SHLIB with R-1.3.1 on WinNT4: C:\TEMP>Rcmd SHLIB tryf.o make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. C:\TEMP>Rcmd SHLIB tryf.f make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. I

I just installed the R-patched 1.4.0 and for some reason I now have trouble compiling R packages - I could compile it a few weeks ago with R 1.4.0 released in December. This only happens if I put the --binary option in. For example: Rcmd build --binary cw returns the error: make: Entering directory `/cygdrive/c/PROGRA~1/R/RW1040/src/gnuwin32' make DLLNM= \ -C C:/MyRWork/cw PKG=cw