similar to: Newbie question about by()

Sorry about the lack of detail. I am running R v.1.2.2. I can recast my question (which I think I have partially answered) more succinctly as follows: 1. This seems to work (note that group takes values 1,2,3,4, or 5): my.newfun <- function(x) myfile <- lm(award ~ ilogemp + ilogage, x) test.by <- by(wintemp, as.factor(wintemp$group), my.newfun) 2. This does not work (leaving aside

Dear R listers -- The program below does the following tasks: 1. It creates a file (wintemp4) that is a subset of alldata4 consisting of "winner" records in 50 industry groups (about 5400 obs); 2. It defines a function (myppr1) that runs the ppr function in modreg once to generate goodness of fit (sum of squared errors) measures by number of terms included in model and then reruns

Dear R listers -- I have several questions about using the ppr command in the modreg module. I discovered -- quite by accident -- that if I re-order the data, I obtain different results. The output below shows what I mean. I have two datasets (dataset1 and dataset2) that are identical (tested using proc compare in SAS) except for the fact that the records are in different order. Below I have

I used the supersmoother function in the modreg package as follows: super <- supsmu(ilogemp,award) Then I decided that I might want additional explanatory variables (other than ilogemp) in my model. The ppr function in modreg seemed a logical extension of supsmu from univariate to multidimensional explanatory variables. As a "check" I ran the following: pprest <-

Dear R users, I am looking for the source code of the implementation of ppr (Projection Pursuit Regression) in R. It will be great if citations of the source papers on which the implementation is based, are also provided. Thank you, Arvind Iyer, Grad student, Deptt. of Biomedical Engineering Viterbi School of Engineering University of Southern California, Los Angeles [[alternative HTML

Folks, The projection pursuit regression function in the base R seems to crash when the optimization level is set to zero, i.e. the initial ridge terms are accepted without refitting. I encountered this problem in an out-of-sample prediction exercise using predict. But further investigation suggests the issue is with the ppr fit and predict just sppeds up the crash. The other optlevels seem to be

Hi, Recently, I installed the 1.1.0 version of R (for Windows), since it includes an implementation of Projection Pursuit (I failed to write my own version of PP as a standalone C++ program). As far as I know, R offers two interfaces/sintax for the ppr() function. The first one requieres a regression formula and a data frame. The other requieres X, a matrix with the explanatory variables, and Y,

Hi all, I am doing a projection pursuit regression using the ppr() function from modreg. I would also like to use predict.ppr(). However, I cannot find any information about it in the help files. There is a link to predict.ppr in the index for modreg, but that link is to the help for ppr(). Has predict.ppr() not been implemented? If not, does anyone have a suggestion as to how to implement

Dear all, I have been doing tests using SVM, random forests and PPR. The data is from a data stream (that is, the data for training and for test is always increasing / changing). With SVM and random forests everything is ok, but with ppr there are situations where it crashes. For the examples I have used I noticed that if one of the variables has just one value (it can happen), it crashes for

supsmu(periodic=TRUE) can crash R by reading before start of array. To reproduce: set.seed(1) xx <- runif(29000) yy <- rnorm(29000) span <- 0.49 i <- 1 while(i < 200){ cat(i,"\n") int <- supsmu(xx,yy,periodic=T,span=span) i <-i+1 } results in: 1 2 3 4 5 6 7 8 9 Program received signal SIGSEGV,

The pursuit projection packages ppr is an excellent contribution to R. It is great for one-to-three ridge fits, often somewhat intuitive, and for multi-ridge fits, where it at least describes a lot of variance. Like many folk, I need to report the fits obtained from ppr to the greater, outside, non-R world. It is fairly obvious how to use the terms alpha and beta to report on

Hopefully the last patch from me to UTF-8 issues. Metaflac can now print all console supported characters from tags on the screen. It also fixes metaflac to be able to import its own exports back without non-ascii characters getting mutilated. And --no-utf8-convert now works properly with import and export commands. I updated my Windows binary archive with these changes for any interested

Hello everybody, I'm a new user of R and I'm working right now with the ACE function from the acepack library. I Have a question: Is there a way to predict new responses using ACE? What I mean is doing something similar to the following code that uses PPR (Projection Pursuit Regression): library(MASS) x <- runif(20, 0, 1) xnew <- runif(2000, 0, 1) y <- sin(x) a <- ppr(x, y,

Greetings, I'm attempting to install R-0.64.1 on a Sun Sparc 20 running Solaris 2.4 with gcc-2.7.2.2, g77-0.5.20 and Gnu make 3.76-1. On several occasions, the make process aborted when trying to build the shared object file for the modreg package (its first attempt at such a beast). In all attempts, the error message is as follows: ../../../../bin/R SHLIB -o modreg.so bsplvd.o bvalue.o

I have a Supermicro SuperServer 6013P-8 system which features a X5DPR-8G2 motherboard with embedded Adaptec AIC-7902 dual-Ultra320 SCSI controller. Said system boots and runs fine with 4.8-RELEASE (with a slight cosmetic problem during boot that can be cured by building a kernel without eisa support). With STABLE (as of 19 June) the system locks up hard (no response to the keboard) during the

Hello, I tried to compile v2.3.1 on Solaris x86 with SUN Pro compilers. I had an error while stats libarary was being compiled and I notice that "-xtarget=generic64" was not passed to f95 while cc used it. Could you tell me how to fix this problem? f95 -PIC -O -I/mounts/devel/SUNWspro/prod/include -c sgram.f -o sgram.o f95 -PIC -O -I/mounts/devel/SUNWspro/prod/include -c

Hi, I've noted that not all `predict' methods are hidden in the namespace: > methods("predict") [1] predict.ar* predict.Arima* [3] predict.arima0* predict.glm [5] predict.HoltWinters* predict.lm [7] predict.loess* predict.mlm [9] predict.nls* predict.poly [11] predict.ppr* predict.prcomp* [13]

Full_Name: Hugh Miller Version: 2.8.1 OS: XP Submission from: (NULL) (128.250.24.101) Hi there, I've been looking at approaches that use the projection pursuit regression function fairly (ppr) heavily, and have discovered that it crashes my R system on occasion. It only happens with the inputs are pathological in some way I don't understand. I have pasted such an example below. Any

Hi has anyone succeeded in installing R on DEC alpha OSF 4.0 with gcc/g77 ? The PLATFORMS file mentions successful installtion on OSF 3.2 using cc. Here is the output I get when trying to compile: ld -shared -o eda.so line.o smooth.o ld: Warning: Unresolved: floor ceil rsort __exc_add_pc_range_table __exc_add_gp_range __exc_remove_pc_range_table __exc_remove_gp_range make[4]: Leaving

Full_Name: Hervé Dréau Version: not applicable OS: not applicable Submission from: (NULL) (212.198.234.254) Here's the listing of difference in version and existence between the PACKAGES file found in the contrib directory and the content of the directory. This cause a problem with the automatic install (and upgrade) of packages NISTnls 0.9-1 NISTnls_0.9-2.tar.gz bats not found in