similar to: :predict.ppr

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 <-

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 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

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

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

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

Hi, I am segfaulting when using predict.loess() (checked with r62092). I've traced the source with the help of valgrind (output pasted below) and it appears that this is due to int overflow when allocating an int work array in loess_workspace(): liv = 50 + ((int)pow((double)2, (double)D) + 4) * nvmax + 2 * N; where liv is an (global) int. For D=1 (one x variable), this overflows at

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]

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

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

Hi there, I would like to draw a scatter plot and fit a smooth line by loess. Below is the data. However, the curve line started from 0, which my "resid" list doesn't consist of 0 value. It returned some warnings which I don't know if this is the reason affecting such problem. Here I also attached the warning messages. Please let me know if there is a solution to fix this. Thank

Hi, I have a data frame with 6563 observations. I can run a regression with loess using four explanatory variables. If I add a fifth, R crashes. There are no missings in the data, and if I run a regression with any four of the five explanatory variables, it works. Its only when I go from four to five that it crashes. This leads me to believe that it is not an obvious problem with the data,

Dear R community, I am trying to understand how the predict function, specifically, the predict.loess function works. I understand that the loess function calculates regression parameters at each data point in 'data'. lo <- loess ( y~x, data) p <- predict (lo, newdata) I understand that the predict function predicts values for 'newdata' according to the loess regression

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

I am using R to do a loess normalisation procedure. In 1.5.1 I used the following commands to normalise the variable "logratio", over a 2d surface (defined by coordinates x and y): > array <- read.table("121203B_QCnew.txt", header=T, sep="\t") > array$logs555<-log(array$s555)/log(2) > array$logs647<-log(array$s647)/log(2) >

Hi, if make and gmake are different on any machine (for example Solaris with gnu make as gmake), then compiling fails with gmake. A small transcript follows. If i make a link from gmake to make as under linux, then it works. This problem exists in all versions of R. g77 -O2 -fPIC -c sslvrg.f -o sslvrg.o g77 -O2 -fPIC -c stxwx.f -o stxwx.o ../../../../bin/R SHLIB -o modreg.so bsplvd.o bvalue.o

I'm updating the loess routines to allow for, among other things, arbitrary local polynomial degree and number of predictors. For now, I've given the updated package its own namespace. The trouble is, panel.loess still calls the original code in package:stats instead of the new loess package, regardless of whether package:loess or package:lattice comes first in the search list. If I

Respected R experts, I am trying to apply a user function that basically calls and applies the R loess function from stat package over each time series. I have a large matrix of size 21 X 9000000 and I need to apply the loess for each column and hence I have implemented this separate user function that applies loess over each column and I am calling this function foo as follows:

Full_Name: Frank Beimfohr Version: 0.64.1, devel. OS: Solaris 2.5.1 Submission from: (NULL) (129.217.131.31) I try to compile R on my Sparc 4 (Solaris 2.5.1) but the compilation fails. I tried the developer-version and the contributed 0.64.1-Version. I start configure with the --g77-Option. During the compilation it stops with an error, which says that the R/src/library/modreg/src/bsplvd.f

Dear R-Helpers, I suspect I'm about to ask a FAQ, but I haven't been able to find an answer in the FAQ, AItR or an R Site Search. When I look at the methods of summary (below) it says, "Non-visible functions are asterisked". I looked at the help file for summary.princomp, which did not comment on it being non-visible. I ran its help file example, which printed visible output. I