search for: colormodel

I have made some modifications to the X11 graphics driver so that it is more flexible about its use of colors. I have added a new parameter to the X11/x11 function which controls this. The parameter is currently called "colormodel" and works as follows: colormodel = 0 Monochrome graphics colormodel = 1 Grayscale (256 shades) colormodel = 2 Pseudocolor1 colormodel = 3 Pseudocolor2 colormodel = 4 Truecolor Pseudocolor1 allocates as big a color cube as possible and then approximates requested colors with colors...

I'm trying to create figures in PDF that use the 'gray' colormodel instead of the default 'RGB' model, by requirements of a publisher. My problem has to do with the fact that I'm not being able to get gray colors with this option on the pdf() driver. Here is a small example for problem replication: > R.version _...

hi! I would like to produce simple black and white postscript figures for publishing. A black/white or grayscale or CMYK colormodel can be used, but not RGB colours. Can I produce postscript graphs in R that satisfy this? Following an earlier advice on the help-list I have tried using Photoshop to convert - but this seems to convert the vector format into raster format - giving larger, but less precise figures. many than...

...rt of the big Pantone family. The problem is that both pdf() and postscript() offer either rgb or cmyk, but no spotcolors such as pantone. I'm afraid this constraint can't be solved at all, and we can't use R for creating these plots? I did not find any package that would extend the colormodel to include spot colors... Did anyone had a similar experience? Thanks!! Matthieu

...1) It appears that number values are mysteriously changing. e.g. if you look at the Hashtable error there is no way the IllegalArgumentException could be thrown, unless the float value passed into a function is being corrupted somehow on the stack. 2) I''m seeing JVM crashes (e.g. the ColorModel crash below). I''m seeing other crashes inside native code methods in other apps I''m running. I''ve tried this with/without /lib/tls. And on a RHEL4 and Debian Sarge DomU. I don''t see either problem when the same app runs on a non-Xen server. Guesswork: I no...

...0 x1 <- cumsum(runif(n)) x2 <- cumsum(runif(n)) d <- data.frame(val=c(x1,x2),id=c(1:n,1:n), nt=c(rep("A",n),rep("B",n))) u1 <- xyplot(val~id | nt, data=d,aspect=1,layout=c(1,2)) u2 <- xyplot(val~id|nt, data=d,aspect=0.5,layout=c(1,2)) postscript("~/k.ps",colormodel="rgb",paper="letter",horiz=T) print(u1,position=c(0,0,1/3,1),more=T,newpage=T) print(u2,position=c(1/3,0,1,1),more=F,newpage=F) dev.off() The two figures are not base aligned. I would like them share the same the baseline and same height, if necessary the paper width and heigh...

...o install.packages() with Ncpus > 1 guards against simultaneous installation of indirect dependencies as well as direct ones. o Sweave now knows about a few more Windows' encodings (including cp1250 and cp1257) and some inputenx encodings such as koi8-r. o postscript(colormodel = "rgb-nogray") no longer sets the sRGB colorspace for each colour and so some viewers may render its files much faster than the default colormodel ="rgb". o The default for pdf(maxRasters=) has been increased from 64 to 1000. o readBin() now warns if...

...o install.packages() with Ncpus > 1 guards against simultaneous installation of indirect dependencies as well as direct ones. o Sweave now knows about a few more Windows' encodings (including cp1250 and cp1257) and some inputenx encodings such as koi8-r. o postscript(colormodel = "rgb-nogray") no longer sets the sRGB colorspace for each colour and so some viewers may render its files much faster than the default colormodel ="rgb". o The default for pdf(maxRasters=) has been increased from 64 to 1000. o readBin() now warns if...

...z() and the cairographics-based X11() types with buffering (which are the default on-screen devices). o New function dev.capture() for capture of bitmap snapshots of image-based devices (a superset of the functionality provided by grid.cap() in grid). o The default colormodel for pdf() and postscript() is now called "srgb" to more accurately describe it. (Instead of "rgb", and in the case of postscript() it no longer switches to and from the gray colorspace, by default.) The colormodel for postscript() which does use both gr...

...z() and the cairographics-based X11() types with buffering (which are the default on-screen devices). o New function dev.capture() for capture of bitmap snapshots of image-based devices (a superset of the functionality provided by grid.cap() in grid). o The default colormodel for pdf() and postscript() is now called "srgb" to more accurately describe it. (Instead of "rgb", and in the case of postscript() it no longer switches to and from the gray colorspace, by default.) The colormodel for postscript() which does use both gr...

...not defined by the arguments to postcript(): > args(grDevices::postscript) function (file = ifelse(onefile, "Rplots.ps", "Rplot%03d.ps"), onefile, family, title, fonts, encoding, bg, fg, width, height, horizontal, pointsize, paper, pagecentre, print.it, command, colormodel, useKerning, fillOddEven) and in the list of predefined device options they are zero: > ps.options()[c("width", "height")] $width [1] 0 $height [1] 0 and debugging postcript() they are indeed passed as zeros to .External(PostScript, ...). > sessionInfo() R version 2.1...

dear R experts---I am struggling with the requirements to prepare my files for my printers. I am printing in 2/2 format, which means cyan and black for me, which they take from my color-separated pdf files. R comes into play, because it produces all the figures that are embedded in my book (pdflatex). now, TeX has no problems producing CMYK files. However, R produces RGB files (for

...width of the device region as w millimetres and here I calculate # its height, taking care of the aspect ratio h <- b + t + asp*(w - (l + r)); postscript(output, onefile=FALSE, paper="special", width=w/25.4, height=h/25.4, horizontal=FALSE, fonts=c("Times"), print.it=FALSE, colormodel="rgb", pointsize=12); # here I set all the possible paddings to make sure that all other margins are 0: trellis.par.set(layout.widths=list(left.padding=l, right.padding=r, key.ylab.padding = 0, ylab.axis.padding = 0, axis.key.padding = 0, units="mm"), layout.heights=list(bottom...

...en. Is this the expected behavior of mfrow and layout? Paul -------------------------------- My code is as follows (ToruosityPlot and DiameterPlot are essentially identical to LDRPlot). layout(matrix(1:3, ncol=1)) #par(mfrow=c(3,1)) pdf("results.pdf", width=4, height=3, pointsize=4, colormodel="cmyk", onefile=TRUE) TortuosityPlot(left, right) DiameterPlot(left, right) LDRPlot(left, right) dev.off() LDRPlot <- function(left, right) { plot(left$x, left$LDR, bty="n", ann=FALSE, xlim=c(-1500, 1000), ylim=c(1.0, 1.5)) abline(v=0, col=gray(.90)) lines(le...

...t has essentially the same structure as it did back then. I think it may have finally dawned upon me what the issue really is: > > The logic is that in Rf_addX11Device, we have > > if (!X11DeviceDriver(dev, display, width, height, > ps, gamma, colormodel, maxcubesize, > bgcolor, canvascolor, sfonts, res, > xpos, ypos, title, useCairo, antialias, family)) { > free(dev); > errorcall(call, _("unable to start device %s"), devname); >...

...ut... > >It is probably not unrelated to the R_ProcessEvents line that >I took out, but that was definitely wrong. However, one might reenable >it if one could change this bit of code > > if (!(ptr_X11DeviceDriver)((DevDesc*)(dev), display, width, height, ps, gamma, > colormodel, maxcubesize, canvascolor)) { > free(dev); > errorcall(gcall, "unable to start device %s", devname); > } > gsetVar(install(".Device"), mkString(devname), R_NilValue); > dd = GEcreateDevDesc(dev); > addDevice((DevDesc*) dd); > initDisplayList((...

...ntially the same structure as it did back then. I think it may have finally dawned upon me what the issue really is: >>> The logic is that in Rf_addX11Device, we have >>> if (!X11DeviceDriver(dev, display, width, height, >>> ps, gamma, colormodel, maxcubesize, >>> bgcolor, canvascolor, sfonts, res, >>> xpos, ypos, title, useCairo, antialias, family)) { >>> free(dev); >>> errorcall(call, _("unable to start device %s&quot...

...current code, and AFAICT it has essentially the same structure as it did back then. I think it may have finally dawned upon me what the issue really is: The logic is that in Rf_addX11Device, we have if (!X11DeviceDriver(dev, display, width, height, ps, gamma, colormodel, maxcubesize, bgcolor, canvascolor, sfonts, res, xpos, ypos, title, useCairo, antialias, family)) { free(dev); errorcall(call, _("unable to start device %s"), devname); } dd = GEcreateDevDesc...

...it has essentially the same structure as it did back then. I think it may have finally dawned upon me what the issue really is: >> The logic is that in Rf_addX11Device, we have >> if (!X11DeviceDriver(dev, display, width, height, >> ps, gamma, colormodel, maxcubesize, >> bgcolor, canvascolor, sfonts, res, >> xpos, ypos, title, useCairo, antialias, family)) { >> free(dev); >> errorcall(call, _("unable to start device %s"), devname); &g...

Hi everyone, Does anyone know how to get "black and white theme" (grey scale,, I would say) graphs using lattice or ggplot2, as it is shown in this webpage: http://lmdvr.r-forge.r-project.org/figures/figures.html? I am using Sweave, and I cannot get that color configuration. I have added the following option: trellis.device(color=FALSE) but I got a pdf file with color graphs. Thank