similar to: par(mfg=) and postscript and pdf

Full_Name: Dan Freak Bolser Version: Version 2.0.0 (2004-10-04) OS: Linux 2.4.20-31.9 (RedHat 9) Submission from: (NULL) (62.253.128.15) The same problem I am having has been reported here

Dear list, I've noticed a width/height scaling bug in multi-panel plots when you change the active plot using par mfg The underlying par setting that maps the full plot width (or height) to the numerical axis labels does not get updated when you change plots with par(mfg=...). Thus plotting a point at c(10,10) in the first plot will only be in the correct place IF the most recently

The same problem I am having has been reported here http://tolstoy.newcastle.edu.au/R/devel/04a/0344.html Namely that using par(mfg=...) with a postscript (eps) for inclusion with latex makes the figure appear upside down and back to front (flipped)! Converting the dvi to ps makes matters worse (the eps seems to be broken), however, it appears fine with gv. Here is (basically) the code I am

The same problem I am having has been reported here http://tolstoy.newcastle.edu.au/R/devel/04a/0344.html Namely that using par(mfg=...) with a postscript (eps) for inclusion with latex makes the figure appear upside down and back to front (flipped)! Converting the dvi to ps makes matters worse (the eps seems to be broken), however, it appears fine with gv. Here is (basically) the code I am

Hi, a colleague of mine encountered some unexpected behavior regarding the postscript output from R. It's difficult for me to tell whether or not this is an R problem or a ghostview/gv/interpreter problem. Just to note, I think it's exactly the same situation reported here: http://finzi.psych.upenn.edu/R/Rhelp02/archive/25436.html The following code produces a working plot (no

Hi, I'm trying to add points to 2 plots on the fly using par(mfg=vector) so switch between them. However, the appropriate scales aren't switched when changing from one plot to another, e.g. par(mfcol=c(2,1)) plot(1,1, col="blue") # blue plot plot(1.2,1.2, col="red") # red plot points(1.1,1.1) # appears to bottom left of red point par(mfg=c(1,1)) #

Ross Ihaka writes: > > I just checked my S manual and it appears that layout > parameters like can "mfg" only be given in par(). Yes. pty is another, for example. > I think that in fact "mfg" is only meant to be queried. No. One use for setting mfg is to produce a page of plots in portrait orientation with, say, two small plots on the top half of the page

Full_Name: Craig A. McKinstry Version: 1.0.0 OS: WinNT4.0 and Win98 Submission from: (NULL) (192.101.100.130) When creating a multi-panel graphic, the command par(mfg=c(i,j,r,c)) is supposed to allow the user free movement between graphics panels to develop each panel separately. This works for the first invocation of par(mfg=c()) and for the first panel panel specified, but not for subsequent

I'm having a problem with the mfg option of par. Am I making an error in my usage? Here is a simple example that I thought would plot to the 4 corners of a 2x2 plot but doesn't plot to the lower right and plots twice on the upper left. par(mfrow = c(2, 2)) pos <- as.matrix(expand.grid(1:2, 1:2)) for (ix in 4:1) { par(mfg = pos[ix, ]) plot(1:5) } Thank you in advance. R version

It seems there are problems with mfg, both the old version .61.2 and the snapshot .62. > x<-rnorm(100) > y<-rnorm(100) > y1<-x/y > x11() > par(mfcol=c(2,1)) > par(mai=c(.6,.6,.2,.2)) > plot(x,y,mfg=c(2,1,2,1)) I'm not sure if 2,1 is considered the top or the bottom position on the page, but whether you say mfg=c(2,1,2,1) or mfg=c(1,1,2,1), the first

Dear all, I have a simple plot using "gridBase" like this. The problem occurs whenever I execute this code there is always a blank page created before the actual plot. How can we disable that blank page? I am using: R version 2.7.2 (2008-08-25) and gridBase version: 0.4-3 __ BEGIN__ library(grid) library(gridBase) opar <- par(no.readonly=TRUE) par(opar) grid.newpage()

Full_Name: baptiste augui? Version: 2.10.1 RC (2009-12-06 r50690) OS: Mac OSX 10.5 Submission from: (NULL) (90.25.215.172) The following code, run with a vanilla R session, produces different visual output for the two devices, library(grid) pdf("test-pdf.pdf") grid.newpage() grid.lines(gp=gpar(lty="13", lineend = "butt")) dev.off() png("test-png.png")

Can we add a note to the documentation that setting par(fig) resets par(mfrow) and par(mfcol) to c(1,1)? Or are mfrow and mfcol now deprecated in favor of all the split screen stuff? (I was spending the morning trying to write some code that plotted multiple subplots within whatever plot region was active at the moment; I was able to set and reset fig successfully, but got very confused as to

I'm working on my 'oce' package, trying split.screen() instead of par(mfrow). My code is too long to post, and I hope it's ok that I ask this question without doing so. My code seems to work fine when I source() it, but when I do "R CMD check" on my package, I get the error that I've put as the subject line, when it runs examples. If I comment out the plot()

Hello, I'm currently using R-0.65.0 with --gnome option in configure on IRIX64 and Debian GNU/Linux. I found a problem in generated postscript file which has following sequence: x <- 1:30 postscript("output.ps") par(mfg=c(1,1,2,2)) plot(x,sin(x)) plot(x,sin(x)) plot(x,sin(x)) plot(x,sin(x)) dev.off() The generated postscript file "output.ps" can't

Hello all! I'm a newcomer to R, so please bear with me. My problem is the following: I'm trying to use R to do some geostatistics stuff (mostly kriging), and am having trouble printing a multiple figure. When I create a single figure (one image/contour command), it works fine. The instant I try to create a multiple figure file, I start getting postscript errors. I'm using the

Dear R-users, I have got the following problem. I need to create 4x2 arrays of xyplot's on several pages. The plots are created within a loop and plotted using the print function. It seems that I cannot find the proper grid syntax with my viewports, and the more/newpage arguments. The following script is a simplification but hopefully will suffice to illustrate my problem. Any suggestion

I am running into a limitation of the grid::grid.newpage function, for which I would like to overwrite this function with a slightly modified one. Hopefully this is a temporary working solution until the package gets updated. I found a way to overwrite the function in the package:grid namespace. However, lattice imports grid rather than depending on it. So I need a way to overwrite this imported

On 03/30/2016 09:12 AM, Minchan Kim wrote: > Now, VM has a feature to migrate non-lru movable pages so > balloon doesn't need custom migration hooks in migrate.c > and compact.c. Instead, this patch implements page->mapping > ->{isolate|migrate|putback} functions. > > With that, we could remove hooks for ballooning in general > migration functions and make balloon

On 03/30/2016 09:12 AM, Minchan Kim wrote: > Now, VM has a feature to migrate non-lru movable pages so > balloon doesn't need custom migration hooks in migrate.c > and compact.c. Instead, this patch implements page->mapping > ->{isolate|migrate|putback} functions. > > With that, we could remove hooks for ballooning in general > migration functions and make balloon