search for: userast

Hi R-help list What is the threshold for the `useRaster` argument of graphics::image() to decide whether a grid is "regular" or not (i.e. the usage of useRaster=T is allowed or not). My `dev.capabilities("rasterImage")$rasterImage` is "yes". I could not find this information in the internet. I also could not find the sou...

the details section of ?image says: > If useRaster is not specified, raster images are used when the > getOption("preferRaster") is true, the grid is regular and either > dev.capabilities("raster") is "yes" or it is "non-missing" and there > are no missing values. but in my experience this is n...

...make a *huge* difference, with a very small number of added/changed lines of code. (Of course I have barely tested it at all.) Is there any reason this *shouldn't* go into the next release? > source("image.R") > z <- matrix(runif(1e6),nrow=1000) > image(z) > image(z,useRaster=TRUE) (Patch against SVN 54284 attached; people can contact me if it doesn't go through and they want it.) Ben Bolker -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: image_diff.txt URL: <https://stat.ethz.ch/pipermail/r-devel/at...

I noticed some undocumented and inconsistent behavior in device_Raster when a plot is produced with reflected axes such as: image(volcano, xlim = c(1,0), useRaster = TRUE) image(volcano, ylim = c(1,0), useRaster = TRUE) The `pdf` device will perform horizontal and vertical reflections, while `quartz` will ignore the transformations when plotting to the screen, but when plotting to a file, `quartz(file = 'test.pdf', type = 'pdf')`, it wi...

Dear R users, I have a desktop computer and a laptop, both of them with Ubuntu Lucid. The former has R2.10 installed from Ubuntu repositories (this is the most recent version in the repositories), while the latter has R2.13 from the CRAN repositories. I noticed that postscript files generated with R2.10 are "better" than files generated with the latest release of R, in particular for

...7E7E7 4 1 4 14289229 11 #E7E7E7 5 1 5 11945929 11 #E7E7E7 6 1 6 8401235 11 #E7E7E7 The values in 'j' run from 1 to 11. I would like to plot the point (a1,a2) with color given by j I tried mi <- image(d[,"a1"],d[,"a2"],d[,"j"],col=mycols(length(f)),useRaster=TRUE) (where mycols is from colorRampPalette(c("#000000","#FFFFFF"),bias=1.5) However, i got the following error: Error in image.default(d[, "a1"], d[, "a2"], d[, "j"], col = mycols(length(f)), : increasing 'x' and 'y' values...

Hi, I'm no longer on the subscribing list, but was hoping to get my question posted.? Please inform if this is ok, although I am guessing you wont post with the image below.? If so, let me know and I will resend without the image. Thanks Hi, I just upgraded my system and my version of R all at once.? Upon running old code for heatmaps etc, I suddenly notice that there is an odd grid pattern

...aBits=1) of in OSX's preview makes the plots look really smooth, but makes everything else look bad (personal opinion..). The plots do look ok in acrobat reader. I think it would be much better if R corrected this problem - even if it is not totally R's fault. It seems that using the option useRaster=T in image() solved this problem, but creates other problems for OSX's Preview (it seems that OSX's preview first anti-aliases the raster, and then scales it... creating a mess). Density plots produced by gnuplot do not seem to have this problem: --- set pm3d map set pm3d at b set ticsl...

...0.777777777777778, -0.666666666666667, -0.555555555555556, -0.444444444444444, -0.333333333333333, -0.222222222222222, -0.111111111111111, 0, 0, 1, 10, 6000) m <- t(m[nrow(m):1,ncol(m):1]) par(las=2, mar=c(8,8,1,1)) image(t(m), ylab='', xlab='', axes=FALSE, col=cols, breaks=br, useRaster=FALSE) axis(2, at=seq(0,1,length=6), labels=rownames(m), font=2) axis(1, labels = FALSE, tick=FALSE) labels <- sprintf("Compound%d", 1:ncol(m)) text(seq(0, 1, length=ncol(m)), par("usr")[3] - 0.1, srt = 45, adj = 1, labels = labels, xpd = TRUE, col='#666666...

...34634 (xmin, xmax, ymin, ymax) coord. ref. : +proj=longlat +datum=WGS84 +no_defs +ellps=WGS84 +towgs84=0,0,0 values : in memory min value : 2116 max value : 36070 ##### plot Rasterlayer > plot(img, col=rev(terrain.colors(25)), axes = TRUE, xlab="x", ylab="y", useRaster=TRUE) Erro em as.double(y) : cannot coerce type 'S4' to vector of type 'double' I can plot the data with image function, but i don't know put the legend with the color palette. Thanks Julio [[alternative HTML version deleted]]

Hello R-users, I am trying to do an image plot where I have been given latitudes, longitudes and the values at the corresponding locations. A sample of the data is given as follows: values=c(0,1,0,0,0,0,2,2,0,0) lat=c(29.6660,29.6756,29.3492,29.2654,29.2827,29.4070,35.3510,35.6590,35.7587,38.2794)

Dear R users, I'm currently using the Graphics package to display several hundred of matrix objects, using a layout and the image() function. It works well except for large matrices (> 1000*1000) or for a large number of matrices (there is a limitation around 400 if I remember well) To solve these issues, I move to the Matrix package which is much more efficient for large sparse matrix,

...objects in packages which used S4 classes but did not Depends: methods in their DESCRIPTION file. o The HTML Help Search page had malformed links. (PR#14769) o A couple of instances of lack of protection of SEXPs have been squashed. (PR#14772, PR#14773) o image(x, useRaster=TRUE) misbehaved on single-column x. (PR#14774) o Negative values for options("max.print") or the max argument to print.default() caused crashes. Now the former are ignored and the latter trigger an error. (PR#14779) o The text of a function body containing...

...objects in packages which used S4 classes but did not Depends: methods in their DESCRIPTION file. o The HTML Help Search page had malformed links. (PR#14769) o A couple of instances of lack of protection of SEXPs have been squashed. (PR#14772, PR#14773) o image(x, useRaster=TRUE) misbehaved on single-column x. (PR#14774) o Negative values for options("max.print") or the max argument to print.default() caused crashes. Now the former are ignored and the latter trigger an error. (PR#14779) o The text of a function body containing...

Hi all, I would like to ask your help to add a color band (Ι am not sure regarding the right term, this color band at the right of the plot "describing" values with their corresponding color. For now I have only this code test<-matrix(data=runif(10000),nrow=100) plot(test,axes="FALSE") axis(1,at=c(0,1),labels=c("a","b")) # but  I would like to add

...pping to be turned off completely). ? nls(algorithm="port") now shares more code with nlminb(), and is more consistent with the other nls() algorithms in its return value. ? xz has been updated to 5.0.1 (very minor bugfix release). ? image() has gained a logical useRaster argument allowing it to use a bitmap raster for plotting a regular grid instead of polygons. This can be more efficient, but may not be supported by all devices. The default is FALSE. ? list.files()/dir() gains a new argument include.dirs() to include directories in t...

...pping to be turned off completely). ? nls(algorithm="port") now shares more code with nlminb(), and is more consistent with the other nls() algorithms in its return value. ? xz has been updated to 5.0.1 (very minor bugfix release). ? image() has gained a logical useRaster argument allowing it to use a bitmap raster for plotting a regular grid instead of polygons. This can be more efficient, but may not be supported by all devices. The default is FALSE. ? list.files()/dir() gains a new argument include.dirs() to include directories in t...

...om the misuse of the matrix method (such as PR#14618). o The identical() function gains an ignore.bytecode argument to control comparison of compiled functions. o pmin and pmax now warn if an argument is partially recycled (wish of PR#14638). o The default for image(useRaster=) is now taken from option "preferRaster": for the small print see ?image. o str() now displays reference class objects and their fields, rather than treating them as classical S4 classes. o New function aregexec() in package utils for finding the positions o...

...om the misuse of the matrix method (such as PR#14618). o The identical() function gains an ignore.bytecode argument to control comparison of compiled functions. o pmin and pmax now warn if an argument is partially recycled (wish of PR#14638). o The default for image(useRaster=) is now taken from option "preferRaster": for the small print see ?image. o str() now displays reference class objects and their fields, rather than treating them as classical S4 classes. o New function aregexec() in package utils for finding the positions o...