search for: ctgas

The result of > plot(c(-1,1),c(-1,1),type="n") > arrows(0,0,1,1) > arrows(0,0,0,0) is not what I expected. The first arrow is drawn correctly. The second does not collapse to a point but goes from (0,0) off to (-infinity,infinity). I guess something is divided by zero in the internal function. Chris. =============================================== platform Windows arch

...minor 1.0 year 2000 month June day 15 language R > -----Original Message----- From: Prof Brian Ripley [mailto:ripley at stats.ox.ac.uk] Sent: Thursday, September 28, 2000 2:16 PM To: r-help at stat.math.ethz.ch; Ritter, Christian C SRTCL-CTGAS Subject: Re: [R] non-ideal behavior in princomp > From: "Ritter, Christian C SRTCL-CTGAS" <Christian.C.Ritter at OPC.shell.com> > Date: Thu, 28 Sep 2000 12:59:25 +0200 > > This problem is not limited to R, but R is one of the packages in which it > arises. I'm...

...minor 1.0 year 2000 month June day 15 language R > -----Original Message----- From: Prof Brian Ripley [mailto:ripley at stats.ox.ac.uk] Sent: Thursday, September 28, 2000 2:16 PM To: r-help at stat.math.ethz.ch; Ritter, Christian C SRTCL-CTGAS Subject: Re: [R] non-ideal behavior in princomp > From: "Ritter, Christian C SRTCL-CTGAS" <Christian.C.Ritter at OPC.shell.com> > Date: Thu, 28 Sep 2000 12:59:25 +0200 > > This problem is not limited to R, but R is one of the packages in which it > arises. I'm...

This might be easy (but I didn't find an answer in the archives). I'm trying to make nice looking images (using image()). To make them look nice (not jagged), it usually takes me at least 100x100 points. This can be slow for frequent redraws. Is there a smarter (less point intensive) way? I was thinking in terms of hexabins, for example, which for much less jagged looking regions,

Hi to all who suffer from rterm not shutting down in xemacs/ESS on windows NT or 2000. Also hi to those who could eventually help. Here is some more information which could help and some ENCOURAGEMENT to contribute to a solution. 1. It may be an xemacs problem but it is more likely an interaction between rterm/comint/and xemacs. In fact, the problem started occurring around version R 1.6.0. I

There is a little problem in handling logicals in RMySQL: # here is the MySQL connection > con <MySQLConnection:(1816,0)> # here is the data frame > print(a<-data.frame(x=c(TRUE,FALSE),y=c(FALSE,TRUE))) x y 1 TRUE FALSE 2 FALSE TRUE # as promised, the two data frame columns are identified as logicals and # the field types are set to tinyint > field.types <-

This problem is not limited to R, but R is one of the packages in which it arises. princomp is a nice function which creates an object for which inspection methods have been written. Unfortunately, princomp does not admit cases in which the x matrix is wider than high (i. e. more variables than observations). Such cases are typical in spectroscopy and related disciplines. It would be nice if the

Hi all, I'll have to filter Raman spectra and I would like to do so in R. I'm trying to figure out how. Maybe one of you could help me ... This is what I have to do: General: separate the real spectrum (the set of peaks) from two contaminations: a drifting background and (white) noise Constraints (which should help the task): A - the spectrum is positive B - the spectrum is long

This message is for people who know the mechanics of model.frame within lm. I am fitting lm models for different responses on a data frame which has (at least some) factors. As it happens, some of the responses are NA for some of the factor levels. Logically, lm creates an xlevels list for which the length of levels is different from the original number of levels in the data frame (a

Maybe someone out there has done this already .... (which would save me some time): For a repetitive chemometric task I need to retrieve spectra from a Nicolet IR acquisition system into R and analyze them there. The raw spectra are in files ending in the extension .spa. I can use the Omnic software to export them to .csv, but I would like to skip this step since it is manual. Has anyone of you

Here is the first one. It concerns the handling of multiple offsets. The following lines creates a list with 3 explanatory variables and one response. > x<-seq(0,1,length=10);y<-sin(x);z<-cos(x); w<-x+y+z+rnorm(x) > data<-list(x=x,y=y,z=z,w=w) A lm is fitted with one explanatory variable and two offsets. So far, so good. >

I'll get to it tomorrow afternoon or on Thursday (if my son isn't sick anymore). Chris. -----Original Message----- From: Deepayan Sarkar [mailto:deepayan at stat.wisc.edu] Sent: Tuesday, January 15, 2002 4:13 AM To: r-announce at stat.math.ethz.ch Subject: new version of lattice A new version of the Lattice package is now available on CRAN. A list of the (mostly minor) changes are

Hi all, I''m still not quite happy with the NA and factor handling of lm and predict.lm in R1.6.1 (forcing me to use my not very skillfully crafted patches). Here is the problem 1: >