similar to: locate nearest value in lookup table

Displaying 20 results from an estimated 4000 matches similar to: "locate nearest value in lookup table"

2006 Mar 02
1
extracting RGB values from a colorspace class object
Greetings, After pouring over the documentation for the 'colorspace' package, I have not been able to figure out how the plot() method converts colorspace coordinates to RGB values for display on the screen. I am convert between colorspaces with the various as() methods... but cannot seem to find a way to extract RGB (i.e. for displaying on a computer screen) triplets from color space
2009 Jun 30
2
odd behaviour in quantreg::rq
Hi, I am trying to use quantile regression to perform weighted-comparisons of the median across groups. This works most of the time, however I am seeing some odd output in summary(rq()): Call: rq(formula = sand ~ method, tau = 0.5, data = x, weights = area_fraction) Coefficients: Value Std. Error t value Pr(>|t|) (Intercept) 45.44262 3.64706 12.46007
2007 Jan 28
1
extra panel arguments to plot.nmGroupedData {nlme}
Greetings, I have a groupedData (nmGroupedData) object created with the following syntax: Soil <- groupedData( ksat ~ conc | soil_id/sar/rep, data=soil.data, labels=list(x='Solution Concentration', y='Saturated Hydraulic Conductivity'), units=list(x='(cmol_c)', y='(cm/s)') ) the original data represents longitudinal observations in the form of:
2011 Aug 16
2
sysdata.rda, namespaces and package dependencies
Hi all, I'm struggling with accessing a package dataset (munsell.map, stored in sysdata.rda) when that package is imported, not required. A simple reproducible example is: install.packages("munsell") munsell::mnsl("10B 4/6") # Error in match(col, munsell.map$name) : object 'munsell.map' not found library(munsell) munsell::mnsl("10B 4/6") # Function
2007 Dec 03
1
plotting step functions in plot vs. xyplot
Hi, I have noticed an odd inconsistency when plotting a 'step' function (type='s') in xyplot() vs. plot(). For example, given the following data: ## generate some profile depths: 0 - 150, in 10 cm increments depth <- seq(0,150, by=10) ## generate some property: random numbers in this case prop <- rnorm(n=length(depth), mean=15, sd=2) ## since the 0 is not a depth, and we
2010 Jan 26
0
ANCOVA with measurement error in x and y
Hi, I am looking for some tips on how to incorporate known measurement error into the comparison of slopes in an analysis of covariance. Specifically, if I know that each measurement comes with a 5% error, is it possible to 'expand' the confidence intervals around the estimates for the slope of the line passing through the data defined by the grouping variable? With standard linear
2007 Oct 08
1
do not plot polygon boundaries with spplot {sp}
Hi, Is there a simple way to suppress the plotting of polygon boundaries with spplot() ? # simple list of 12 colors cols <- brewer.pal(12, "Paired") # plot pile of polygons, with 12 classes: spplot(x, zcol='class2', col.regions=cols, scales=list(draw=T), xlab="Easting (m)", ylab="Northing (m)") ... seems to work well. However the polygon boundaries
2008 Jun 09
3
piper diagram
Hi, Is anyone on the list familiar with an R implementation of Piper Diagrams? Example: http://faculty.uml.edu/nelson_eby/89.315/IMAGES/Figure%209-78.jpg I am thinking that two calls to triax.plot (plotrix) along with some kind of affine-transformed standard plot would do the trick. Not so sure about the final layout, or a nice generalized version for something like lattice. Cheers, Dylan
2006 Jul 31
1
questions regarding spline functions
Greetings, A couple general questions regarding the use of splines to interpolate depth profile data. Here is an example of a set of depths, with associated attributes for a given soil profile, along with a function for calculating midpoints from a set of soil horizon boundaries: #calculate midpoints: mid <- function(x) { for( i in 1:length(x)) { if( i > 1) { a[i] = (x[i] -
2010 Sep 16
2
parallel computation with plyr 1.2.1
Hi, I have been trying to use the new .parallel argument with the most recent version of plyr [1] to speed up some tasks. I can run the example in the NEWS file [1], and it seems to be working correctly. However, R will only use a single core when I try to apply this same approach with ddply(). 1. http://cran.r-project.org/web/packages/plyr/NEWS Watching my CPUs I see that in both cases
2008 Feb 13
1
use of poly()
Hi, I am curious about how to interpret the results of a polynomial regression-- using poly(raw=TRUE) vs. poly(raw=FALSE). set.seed(123456) x <- rnorm(100) y <- jitter(1*x + 2*x^2 + 3*x^3 , 250) plot(y ~ x) l.poly <- lm(y ~ poly(x, 3)) l.poly.raw <- lm(y ~ poly(x, 3, raw=TRUE)) s <- seq(-3, 3, by=0.1) lines(s, predict(l.poly, data.frame(x=s)), col=1) lines(s,
2008 Mar 05
1
testing for significantly different slopes
Hi, How would one go about determining if the slope terms from an analysis of covariance model are different from eachother? Based on the example from MASS: library(MASS) # parallel slope model l.para <- lm(Temp ~ Gas + Insul, data=whiteside) # multiple slope model l.mult <- lm(Temp ~ Insul/Gas -1, data=whiteside) # compare nested models: anova(l.para, l.mult) Analysis of Variance
2010 Feb 17
1
strangeness in Predict() {rms}
Hi, Running the following example from ?Predict() throws an error I have never seen before: set.seed(1) x1 <- runif(300) x2 <- runif(300) ddist <- datadist(x1,x2); options(datadist='ddist') y <- exp(x1+ x2 - 1 + rnorm(300)) f <- ols(log(y) ~ pol(x1,2) + x2) p1 <- Predict(f, x1=., conf.type='mean') Error in paste(nmc[i], "=", if (is.numeric(x))
2009 Oct 23
2
interpretation of RCS 'coefs' and 'knots'
Hi, I have fit a series of ols() models, by group, in this manner: l <- ols(y ~ rcs(x, 4)) ... where the series of 'x' values in each group is the same, however knots are not always identical between groups. The result is a table of 'coefs' derived from the ols objects, by group: group Intercept top top' top'' 1 6.864 0.01 2.241 -2.65
2007 Jul 25
0
DF and intercept term meaning for mixed (lme) models
Hi, I am using the lme package to fit mixed effects models to a set of data. I am having a difficult time understanding the *meaning* of the numDF (degrees of freedom in the numerator), denDF (DF in the denomenator), as well as the Intercept term in the output. For example: I have a groupedData object called 'Soil', and am fitting an lme model as follows: ## fit a simple model #
2008 Aug 28
1
drop.unused.levels for two factors {lattice}
Hi, Is there any way to suppress plotting of panels that don't actually contain any information? I have tried using 'drop.unused.levels=TRUE', but there doesn't seem to be any effect. Here is an example: library(lattice) # some fake data: d <- data.frame(x=runif(20), x.class=rep(letters[1:5], each=4), f1=rep(letters[1:2], each=10), f2=rep(letters[10:19], each=2) ) # plot
2009 Oct 26
1
Cbind() on the right-side of a formula in xYplot()
Hi, Using the latest rms package I am able to make nice plots of model predictions +/- desired confidence intervals like this: # need this library(rms) # setup data d <- data.frame(x=rnorm(100), y=rnorm(100)) dd <- datadist(d) options(datadist='dd') # fit model l <- ols(y ~ rcs(x), data=d) # predict along original limits of data l.pred <- Predict(l) # plot of fit and
2009 Jan 23
1
lattice: reverse order of panel.lmline, panel.smooth
Hi, is it possible to reverse the order in which panel.lmline() or panel.smooth() operation in xyplot() ? This type of situation might occur when plotting some variable with depth, but the relation we want to describe is variable ~ depth, and not depth ~ variable, as the plotting formula would suggest. # an example: d <- 1:100 v <- d * rnorm(100) xyplot(d ~ v, ylim=c(100,0),
2010 Jul 19
1
possible bug in ape::extract.clade()
Hi, I was recently splitting some massive phylo class objects with extract.clade() and noticed what appears to be a bug in how tip labels are copied from the full tree to the pruned tree. This possible bug was also mentioned here: http://www.mail-archive.com/r-sig-phylo at r-project.org/msg00537.html An example: library(ape) set.seed(5) x <- matrix(rnorm(100), ncol=10) p <-
2007 Dec 17
0
odd error messages coming from val.prob() {Design}
Hi, after upgrading my R install from 2.5 -> 2.6.1 and performing multiple iterations of update.packages(), I am getting an odd error when trying to plot a calibration curve from the val.prob() function in package Design. when running this function (which used to work) I get the following error message: Error in .C("lowess", x = as.double(xy$x[o]), as.double(xy$y[o]), n,