similar to: Matrixes as data

Hola! I am sending this to the list since emails from me to Simon Wood has bounced earlier. I get: > library(tsDyn) Loading required package: mgcv Erro en `parent.env<-`(`*tmp*`, value = NULL) : use of NULL environment is defunct Error: package 'mgcv' could not be loaded > library(mgcv) Erro en `parent.env<-`(`*tmp*`, value = NULL) : use of NULL environment

Hola! Este mail llegó a r-help hoy, yo lo mandó también a esta lista. Es interesante con competiciones de predicción/clasificación! ¿Alguien que quiere cooperar? Kjetil ---------- Forwarded message ---------- From: Kjetil Halvorsen <kjetilbrinchmannhalvorsen@gmail.com> Date: Fri, Jan 29, 2010 at 12:19 Subject: Fwd: [R] Classification of supernovae - a challenge To: Kjetil Halvorsen

I am experimenting with rSymPy, and it seems to work nice. However, I dislike the need to wrap all sympy expressions within quotes, it leads to ugly calls like library(rSymPy) Var("x,y,z") sympy("(x+y)**2") and so on. Inspired by the function cq from mvbutiles package: library(mvbutils) > cq function (...) { as.character(sapply(as.list(match.call(expand.dots =

Hola! I just changed my laptop to debian squeeze, downloaded R devel from svn repo, as described in the manual. Then I configured for building in a separate build dir with: kjetil at kjetil:~/R/Rbuilddir$ sudo ../svn/configure --- which succeeded, with: R is now configured for x86_64-unknown-linux-gnu Source directory: ../svn Installation directory: /usr/local C

Your understanding isn't similar to mine. Mine says robust/resistant methods are for data with heavy tails, not heteroscedasticity. The common ways to approach heteroscedasticity are transformation and weighting. The first is easy and usually quite effective for dose-response data. The second is not much harder. Both can be done in R with nls(). Andy From: Quin Wills > > I am

I'm trying to (re)learn Sweave and run into some problems. I use now ubuntu (8.10), emacs + ess. Slowly getting upto speed on ess. I have a complete (hopefully) .Rnw file, but the resulting .tex will not compile. The file does not contain anything exotic, but it produces pdf figures, and that is where the problems come: library(tools) > Sweave("varioCoo.Rnw") Writing to file

Hola! I ask here since I learnt from this list that the LaTeX package listings should be good for typesetting R code. I encountered one problem: \begin{lstlisting} X %*% V \end{lstlisting} in the output the * in %*% disappears! same with %/%, etc, the / disappears. Any ideas? Kjetil -- Kjetil Halvorsen. Peace is the most effective weapon of mass construction. --

Hello, I would like to know if there is an R-package available for computing the density, distribution function, quantiles and random numbers of the p-generalized normal distribution or if somebody is already working on it. Best regards, Steve Kalke

Hola! I have the following in a .Rd file: \eqn{\mbox{coef} = c(\mbox{coef}[1],\ldots, \mbox{coef}[n]) } {coef = c(coef[1], coef[2], \dots, coef[n])} However, both arguments come out in the latex file! Whats happening? Kjetil Halvorsen

I am trying to source a file defining a dataset, giving the full path. (rw1031 on windows 98) > source("c:\\kjetil\\audiometria\\data\\audiometria.R") Error in parse(file, n, text, prompt) : syntax error on line 6 also: > parse(file="c:\\kjetil\\audiometria\\data\\audiometria.R", n=-1) Error in parse(file, n, text, prompt) : syntax error on line 6 This seems very

I think the subject says it all. I want to make a simple lattice plot, using xyplot with the argument type=c("l","a"). The problem then is that in the resulting plot it is difficult/impossible to see which plot corresponds to the average and which to the individual profiles. I triedthings like extra arguments lwd=c(1,3) or col=c("blue","red") hoping

I just discovered that when the VGAM package (not on CRAN) is loaded, glm() doesn't work. This is because VGAM defines a family function() which gets found by glm() in place of the family function from stats. Then VGAM:::family returns an object which doesn't have a $family component, (it has a component $vfamily). I thought namespaces should protect us from this happening? Kjetil --

I am trying to install a local package and get this unexpected error: ---------- Making package UMSA ------------ adding build stamp to DESCRIPTION installing R files installing data files installing man source files installing indices Error: couldn't find function "na.omit" Execution halted na.omit of course is in package stats, and that is listed in the Depends field in

I get the following > library(foreign) Error in namespaceExport(ns, exports) : undefined exports: write.foreign Error in library(foreign) : package/namespace load failed for 'foreign' with rw2000dev as of (2004-09-17 Kjetil -- Kjetil Halvorsen. Peace is the most effective weapon of mass construction. -- Mahdi Elmandjra

I encountered something strange with read.spss (package foreign, version 0.7 with R2.0.0 and version 0.8 with R2.0.1 beta, windows XP) I made a test file test.sav with SPSS version 11.5.1 containing only one numeric variable, with a value label for one value not occuring in the file. According to ?read.spss this should result in a factor, but it results in all NA. Using the argument

With rw2010dev I get a strange protect(): protection stack overflow error with a small data frame which otherwise is usable: If anybody wants to have a look I can provide an RData file with the problematic data frame. Doesn't seem to be necessary, the following simulated example generates the error: > testmat <- matrix(1:80, 20,4) > dim(testmat) [1] 20 4 > str(testmat) int

Have I been sleeping in class? rw1071 from CRAN, windows XP incidencia is made by a call to tapply > class(incidencia) [1] "array" > incidencia <- unclass(incidencia) > class(incidencia) [1] "array" Kjetil Halvorsen

Hola! The R FAQ says: 7.12 How do I convert factors to numeric? It may happen that when reading numeric data into R (usually, when reading in a file), they come in as factors. If f is such a factor object, you can use as.numeric(as.character(f)) to get the numbers back. More efficient, but harder to remember, is as.numeric(levels(f))[as.integer(f)] In any case, do not call as.numeric()

I found the need of converting a matrix into a list of its columns (for use with do.call), and was surprised there was no method as.list.matrix, it could easily be a part of as.list default I wrote my.as.list.matrix <- function(mat) { if(!is.matrix(mat))stop("Argument must be a matrix") n <- NCOL(mat) res <- vector(mode="list", length=n)

Hola! I will want to identify pixels in an image with the mouse, for so getting the image data from the matrix(es), for use in subsequent discriminant analysis. But the following bombs R: (windows XP, rw1071) > str(baboon) list() - attr(*, "size")= int [1:2] 512 512 - attr(*, "cellres")= num [1:2] 1 1 - attr(*, "bbox")= num [1:4] 0 0 512 512 - attr(*,