similar to: Re: [R] Postscript query: plotting long vectors (PR#3132)

This may not be considered a bug but it is an incompatibility with S. There was a convention in S that the graphics parameter setting lwd = 0 is supposed to use the minimum possible line width on the device. It is not clear what that means on modern graphics devices but there is still code (like mine) that assumes something sensible happens with lwd = 0 It seems that R's postscript

Hi, I have a query about the maximum length of vector that can be plotted in one go in a postscript driver. Try the following code (in 1.7.0; version details below): t <- seq(from=0, to=4*pi, length=200000) y <- sin(t) postscript(file="o.ps") plot(t, y, type="l") dev.off() If I view the postscript file o.ps in "gv", it takes many seconds before eventually

Hello R Developers, Dear R-developers, I ran some standard tests with currently (today morning) compiled R release candidate in Linux R 2.12.1 RC (2010-12-13 r53843). Some of these tests used plot.TukeyHSD function. This worked OK on the screen (X11 device), but PostScript file could not be rendered. The following example had the problem with me: postscript(file="tukeyplot.ps")

This may not actually be an R/Splus problem, but it started off that way ..... ===+===+===+===+===+===+===+===+===+===+===+===+===+===+===+===+===+===+=== Executive summary: ================== Simulations involving extreme value distributions seem to ``work'' when the underlying distribution is exponential(1) or exponential(2) == chi-squared_2, but NOT when the underlying distribution is

For a long string in an axis title, or main title the postscript device breaks apart the long strings into smaller strings. For example, > postscript('linebreaktest.eps') > plot(1,xlab='aReallyLongStringToSeeHowItBreaks',ylab='aReallyLongStringToSeeHowItBreaks') > for(i in c(.6,1,1.4))text(i,i,'aReallyLongStringToSeeHowItBreaks') > dev.off() produces

To the plot experts: when creating a plot containing different lines, each with a special line type, it may happen that the result of 'postscript()' is not readable by ghostview (which may not be an R error, thus not bug report ;-). This is the case when mixing lty as 0:6 and character or even when using lty as character only. Example: postscript("test.ps") plot(1:10,

Hi, When R generates density plots and these are exported to postscript( a=matrix(1:100,10,10);image(a,col=rainbow(100);dev.copy2eps(file="image.eps") ) The result often looks bad when rendered on screen. The help page states that this is because programs use anti-aliasing. That seems to be true - turning off anti-aliasing for gs (-dGraphicsAlphaBits=1) of in OSX's preview makes

Hi, I am VERY interested in getting the xfig driver so that I can edit graphical output from R. Searching through the mail archives and reading documentation isn't helping. Is there or isn't there a working driver for this purpose. How can I get it? I tried looking at the development version of the tarballs, but I didn't find anything that looked promising in there. Also, does

I have a non-PS printer setup to print under linux using ghostscript as a filter. This printer has two paper trays, one has letter paper, the other tabloid size paper. If I print from a program that uses a PPD file to configure the printer, like StarOffice or The Gimp, I can select the paper size from a nifty list. If I select letter size, the printer print with paper from the letter tray. If

I discovered a little problem when using the Windows NT release of R 1.0.1, and it's still there in R 1.1.0. The boiled down version is this: I want to draw the following plot and put it into a Postscript file: x <- c(1,2,3,4); y1 <- c(1,2,3,4); y2 <- c(2,2,2,2) Fred <- c(1,2) postscript(file="d:/Bob/Papers/IFM/try2.ps") plot(x,y1, type="l")

I have generated a graph on the X11 device, but when I > dev.copy(postscript) postscript 3 > dev.off() X11 2 > the Rplots.ps file is generated but contains a prologue only. Can anyone suggest what I am doing wrong? Just to anticipate the upgrade reply ... > version _ platform i686-pc-linux-gnu arch i686 os linux-gnu

Prof Brian Ripley <ripley@stats.ox.ac.uk> writes: > Except that there is nothing reproducible in that report, not even the > claimed (by Don MacQueen) incorrect lines! Er, right, sorry. Here's a version of the effect, for inclusiont with the report: postscript() x <- seq(0,2*pi,,50000) plot(x,sin(x),type="l") dev.off() Count reduced from the original 200000 to

Full_Name: Mr. Daniel Murray Bolser Version: R 2.0.0 (2004-10-04) OS: Linux beagle 2.4.20-31.9 #1 Tue Apr 13 17:38:16 EDT 2004 i686 athlon i386 GNU/Linux Submission from: (NULL) (193.60.81.207) Trying to execute the following code produces a 'not a valid postscript' error from various postscript readers (gv, ggv, ghostscript). A very similar code works fine. <CODE> postscript()

It seems that the text command isn't working for a postscript device. Here is my code: #----------------------------- # I have stored some data in a 21 by 21 matrix called mat x <- 1:ncol(mat); y <- 1:nrow(mat); labs <- c(" ", "1298", "1537", "TP53", "786", "974", "1303", "1288", "1294",

Can you help me to use Sys.setlocale("LC_NUMERIC", "cs_CZ") (comma as a decimal point) in some useful way, without all the workarounds? After switching to Sys.setlocale("LC_NUMERIC", "cs_CZ"): -- How do I set attributes in read.csv2() not to get columns of real numbers (decimal point = comma, field separator = semicolon) as factors? Wokrkaround: I can go

Full_Name: Zdenek Valenta Version: 1.9.0. OS: Windows XP Submission from: (NULL) (147.231.7.250) I could not copy/save (Trelis) graphics using R version 1.9.0. The graphics displayed normally, but copying/saving it only produced an empty file. Everything works o.k. with R rel. 1.8.1. Best regards, Zdenek Valenta

Hi guys at mapstraction, I made a change in the Polyline.toMicrosoft() function, in order to have all the power that a VEShape has, for instance fill color. Below is the new code, if you want to use it, change it, or whatever. Cheers, Beta /** * toMicrosoft returns a Microsoft polyline * @returns a VEShape */ Polyline.prototype.toMicrosoft = function() { var mpolyline; var mpoints

forgot to fix psx11.c and devPicTeX.c while I was at it (devPicTeX.c doesn't seem to change the color). Should psx11.c be devpsx11.c? Diffs: *** psx11.c.orig Wed Jul 30 10:08:48 1997 --- psx11.c Wed Jul 30 10:09:10 1997 *************** *** 293,298 **** --- 293,299 ---- } if(fg != NA_INTEGER) { psx11_SetColor(fg); + psx11_SetLinetype(GP->lty); PostScriptOpenRectangle(psfp,

I don't think arima works exactly the way one would expect when there is differencing. What I think should happen is that by default the mean of the differenced series is estimated and if include.mean=F, then it is not. This is not what happens. Instead when there is differencing the include.mean argument is ignored. Now I guess, someone could argue that the mean of the original series

Michael Lapsley was suggesting on R-help direct copies to gif/png/jpeg. The following seems to do a sensible job for me of copying the current device to any bitmap format supported by gs. The manipulation is needed to work around assumptions made by postscript(), and I think better fixed in postscript() (but not a couple of days before a release). I want to make onefile=FALSE work on