similar to: Warning in par(args)

Displaying 20 results from an estimated 3000 matches similar to: "Warning in par(args)"

2003 May 12
2
on.exit(par(old.par)) warnings
I often use something like old.par <- par(set someting) on.exit(par(old.par)) but in R 1.7.0. I now get warnings: > old.par <- par() > par(old.par) Warning messages: 1: parameter "cin" can't be set in: par(args) 2: parameter "cra" can't be set in: par(args) 3: parameter "csi" can't be set in: par(args) 4:
2007 Jan 26
1
Inferring dimensions on bitmap device from par()
Hi, I am trying to infer the dimension of an opened bitmap (png, jpeg, bitmap device...) from par() parmeters. From the help on par(), I found that: > dim <- c(400, 200) > png("foo.png", width=dim[1], height=dim[2]) > dim2 <- par("din") * par("cra") / par("cin") > dev.off() > dim2 [1] 399.9999 199.9999 I've tried the above on
2002 Nov 13
2
Wandering usr values in par(no.readonly=TRUE) (PR#2283)
>>>>> "Marc" == Marc Schwartz <mschwartz@medanalytics.com> >>>>> on Wed, 13 Nov 2002 11:01:49 -0600 writes: Marc> Marc Schwartz wrote: >> SNIP >> >> I am guessing that this may be the result of par("ylog") >> and par("xlog") being read only and perhaps impacting the >>
1999 Mar 24
0
par$csi
Dear R-help, I'm using 63.3 on windows NT. The improved graphics device has a problem in that the default par settings produce text that is way too small (63.2 seemed fine). I've compared the parameters between 63.3 and 63.2 and the ones that differ are : cin, cra, csi, mai, pin, plt. In the par help file, cin and cra have no documentation other than that they are read only, the last
2003 Mar 17
0
Problem with pdf device.
Hi, I seem to have broken the pdf device on my installation. I'm running R 1.6.1 under Apple's X11 on darwin 6.3. Running the following commands straight after starting R (and without touching 'par') gives different results - the png file looks fine but I'm missing axes and labels on the pdf. If I try and print the pdf, axes and labels appear but with text characters as
2004 Sep 14
1
documentation error par("cin") and par("cra") (PR#7227)
Dear all, the help of par() claims that cin and cra are c(width, height) but it appears to be rather c(height, width) Best regards Jens Oehlschl?gel > plot.new() > strheight("W", unit="inches") [1] 0.1354167 > par("cin") [1] 0.1354167 0.1875000 > version _ platform i386-pc-mingw32 arch i386 os mingw32
2007 Mar 31
0
X11 and linux and plotting and the vertical axis
I use R on linux and I go through exceed from a windows machine. Depending on the amount of plots I do on a screen, sometimes the numbers on the vertical axis of the plots don't show up. I tried infinite of combinations of mar and cex but nothing helps. Yet, if instead of shooting the graphic upto the screen, I send it to a pdf file or a postscript file, the numbers on the vertical axis of
1999 Nov 24
0
Re: DSE package for multi-variate time series (Please Read (Out of Office))
** Reply Requested When Convenient ** I will be attending a class during the week of November 29. I will get back to you as quickly as possible. If you need to reach me immediately by phone talk with Barb Severs or Diane Terry. Thank you David J. Krassen >>> r-help 11/24/99 10:46 >>> A new version of my DSE package for multi-variate time series analysis is now available
1997 Jun 23
0
R-alpha: various graphics Q.
"contour" can't return a list of contours (it would be nice) "arrows" has different options from S-PLUS (no "open" or "rel" options, no "lwd" parameter or graphics parameter pass-through; "size" in S corresponds to "length" in R). [I know we needn't follow S-PLUS syntax slavishly, but it would be nice at least to
1999 Oct 27
0
[R] par(uin)
Thank you Bendix, {I hope it's okay if I CC my answer to your private mail to R-devel ..} >>>>> On Wed, 27 Oct 1999 08:55:28 +0200, BXC@novo.dk (Bendix Carstensen) said: >> -----Original Message----- >> From: Martin Maechler [mailto:maechler@stat.math.ethz.ch] >> Sent: 25. oktober 1999 14:58 To:Gregory R. Warnes >> Cc:
2002 Nov 12
2
Wandering usr values in par(no.readonly=TRUW) (PR#2283)
--==_Exmh_1801894504P Content-Type: text/plain; charset=us-ascii Dear R folks, Initially I had a plotting routine using logarithmic y-axes that failed after repeated calls if I tried to restore the graphical parameters (which I wanted to do because I used `layout' within the routine. I tried to isolate the problem and found out that the following code with logarithmic axis is sufficient for
1999 Dec 02
1
Large plot symbols (with pch = 1 etc)
On my home (Windows 98) machine I find: > par()$cra [1] 42 16 > par()$csi [1] 0.1666667 > On my work machine I believe I had par()$cra [1] 17 16 So it looks as though R is reading the width wrongly, and that it is the width that is somehow used to determine the plot character size. Incidentally I noted Brian's comment that R had misread his character dimension information wrongly.
2009 Mar 19
1
Difference in client vs. server graphics defaults
Hello, I am having trouble with the difference between default graphic settings on my client machine and the instance of R on our company's server. I created a script locally that output graphs, but when I run it on the server the output graphs have titles running past the margins, legends improperly placed, etc. I checked the default par() settings and found differences between my machine
2006 Apr 28
4
par(mfror=c(1,2))
dear list, i have a problem using the par function. in one graphic device i want to have two plots so i tried to use par(mfror=c(1,2)). of course it worked out, but the height now is twice the length of the width for each single plot. what i actually wanted is something like par(mfrow=c(2,2)) where only the top (or bottom) two plots are drawn with entire length proportions of 1 to 2 ( height 1,
2008 Jul 18
1
par("din") vs dev.size()
Hello, I was messing around with graphics, and noted an odd behavior of par("din"). If the x11 device is empty, par("din") does not return the correct size if the device has been resized manually. dev.size() works correctly. R version 2.7.1; Fedora 8 # case 1 - empty device > x11() > dev.size() [1] 6.995263 6.994187 > par("din") [1] 6.995263 6.994187 #
2005 Jul 13
1
unexpected par('pin') behaviour
hi everybody, I noticed the following: in one of my scripts 'layout' is used to generate a (approx. square) grid of variable dimensions (depending on no. of input files). if the no. of subplots (grid cells) becomes moderately large (say > 9) I use a construct like ###layout grid computation and set up occurs here### ... opar <- par(no.readonly = T);
2001 Nov 30
1
mosaic.by(): vectorizing args passed by apply()?
I've just started learning R, so I'm still on the steep part of the learning curve, but my enthusiasm was heightened by learning that there's a very nice implementation of mosaicplot(). As a learning project, I've already done a basic implementation of a pairs.table() function which does a mosaic scatterplot matrix, and now I'm trying to do conditional mosaic plots (discrete
1998 Jun 19
1
DSE status
I have my DSE library working fairly well now with 0.62.1. It required a few changes because of the changes to R INSTALL and "xxx<-" functions. I would like to tar up a new version soon but 1/ for testing I have been using a kludge in .First.lib to select the first element of section - since I happen to know that is the element I need given the way I have $RLIBS set. This argument
2009 Nov 03
3
Weird operator behaviour
Hi, I have a dataset called 'fish'. fish$Species returns extract 1. When I use fish$Species != c("CRA","PHC"), i.e. I want all species except "CRA" and "PHC", I get extract 2 which is blatantly wrong. Can anyone see what I'm doing wrong? Regards, James EXTRACT 1 > fish$Species [1] ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB ALB
1999 Jul 27
2
Memory profiling/benchmarking
Hi, As a project for a computer performance analysis paper I am taking this semester, I am going to look at the performance of the memory manager in R, with the aim of determining how fast it is and which areas most need improvement. The idea is that I will compare various versions of R, starting with 0.64.2, and then at a few stages in the implementation of the new memory management scheme (of