similar to: R-beta: Using par(tck=,xaxs=)

Displaying 20 results from an estimated 1000 matches similar to: "R-beta: Using par(tck=,xaxs=)"

2008 Mar 21
0
lattice: emulating the par(xaxs="i") behaviour
I tried to emulate the axis interval calculation behaviour of the traditional graphics system (with par(xaxs="i")) in lattice but couldn't find a flexible solution. Let's say a have a simple xyplot: x <- seq(0, 1, 0.01) xyplot(x^2 ~ x, type="l") I want to restrict the plotting region to the data range _and_ have axis labels over the full data range like this:
2000 Jul 12
1
plot.times error -- missing or illegal tck parameter (PR#601)
There seems no default setting for tck, causing problems for plot.times() > library(chron) > dts <- dates(c("02/27/92", "02/27/92", "01/14/92", + "02/28/92", "02/01/92")) > y<-chron(dts,out.format=c("dmy","h:m:s")) > y [1] 270292 270292 140192 280292 010292 > plot(y,1:5) Error in axis(n, at =
2009 Sep 25
1
xaxs disactivated when asp=1 in plots (PR#13971)
Full_Name: Fran?ois Birgand Version: 2.9.0 OS: windows xp Submission from: (NULL) (152.1.16.161) When I type this sequence: x11() Ylim<-c(0,14) Xlim<-c(0,14) plot(0,0,xlim=Xlim,ylim=Ylim,col="white",main="",xlab="",ylab="",bty="n",xaxt="n",yaxt="n",xaxs="i",yaxs="i",asp=1)
2018 Feb 07
0
Re: [libvirt] [PATCH tck] Relabel SELinux when customizing virt-builder image
On Tue, Feb 06, 2018 at 12:50:51PM -0500, Laine Stump wrote: > On 02/06/2018 10:53 AM, Pino Toscano wrote: > > On Tuesday, 6 February 2018 16:40:04 CET Daniel P. Berrangé wrote: > >> When you tell virt-builder to install extra RPMs, this potentially > >> looses the SELinux labelling that Anaconda had originally setup. Thus we > >> must tell virt-builder to
2010 May 26
1
persp(); help with 'tck' option
Hi All, I'm using 'tck' option to *reduce* the length of tick marks but it is not working, can anyone please tell me where I'm going wrong... require(graphics) require(grDevices) x <- seq(-10, 10, length= 30) y <- x f <- function(x,y) { r <- sqrt(x^2+y^2); 10 * sin(r)/r } z <- outer(x, y, f) z[is.na(z)] <- 1 # 'bg' works but 'tck' is not showing
2003 Sep 18
2
hist will not use parameter xaxs (PR#4219)
Full_Name: Mark Wall Version: 1.6.0 OS: linux Submission from: (NULL) (63.251.119.254) I want to plot a histogram of a *subset* of some data: >t = c(0:9) >hist(t,right=FALSE,breaks=10,xlim=c(0,5),xaxs="i") This means I should plot a histogram from 0 to 5 with breaks at 1,2,3,4. This should produce exactly 5 bars of frequency=1. Instead I get 5 and 1/4 bars. I do not want the
1998 Feb 04
1
R-beta: Functionality of tck=1, and mtext()
In the version of R that I am running I have found two advertised features that don't appear to work correctly: Version 0.61.0 Alpha (December 21, 1997) (installed using r-base-0.61.0-2.i386.rpm) 1. mtext adj parameter is seriously offset to the right. For example: > par(oma=c(0,0,3,0)) > mtext("Try this", side=3, outer=T) # nothing is observed on x11 > mtext("Now
2018 Feb 06
2
Re: [libvirt] [PATCH tck] Relabel SELinux when customizing virt-builder image
On 02/06/2018 10:53 AM, Pino Toscano wrote: > On Tuesday, 6 February 2018 16:40:04 CET Daniel P. Berrangé wrote: >> When you tell virt-builder to install extra RPMs, this potentially >> looses the SELinux labelling that Anaconda had originally setup. Thus we >> must tell virt-builder to enable SELinux relabelling. >> >> Signed-off-by: Daniel P. Berrangé
1998 Feb 17
0
"tck" parameter
I have been making some changes to the axis drawing code which will allow users to use par(tck=...) to produce grid lines and tick marks which go into a plot rather than pointing outwards. I don't particularly like the strategy that S uses for determining tick mark size so I have introduces an alternative mechanism as well. There is now a new "par" parameter called "tcl"
2009 May 06
1
Add trend line to XYPlot using a subset of the original data
I've created an xyplot that I want to add a trend line to using a subset of the data. The xyplot is xyplot(X9444500~WY,data=mynewdata,xlim=c(1900,2020),ylab="TEST", xlab="",ylim=c(100,100000),scales=list(x=list(at=c(1900,1920,1940,1960,1980,2000,2020),axs="r",tck=-1),y=list(log=TRUE,tck=-100,at=c(100,1000,10000,100000))), panel=function(x,y,...) {
2009 Jan 05
1
adding a curve with xaxs="i"
I want the curve to touch the y axis like the curve touches the upper boundary. How can I eliminate the margin between axis and curve on the left side? x1 <- c(1,2,3,4,5) x2 <- c(2,4,6,8,10) mod <- lm (x2~x1) hm <- function (x) (mod$coe[1]+x*mod$coe[2]) plot.new() # ... box() curve (hm,lty=1,add=T,xaxs="i",yaxs="i") (R 2.8.1) -- Sensationsangebot verl?ngert: GMX
2007 Dec 19
1
lattice: axes drawn when relation='free' or relation='sliced' but not when relation='same'
I'm using lattice to draw a multi-panel figure: 5 rows, 4 columns. The y-axis for each panel is determined by yaxs <- list(draw=T , labels=c(0, '.5', '1', '1.5') , at=c(0, .5, 1, 1.5) , tck=c(.4, 0) , cex=.7 , alternating=2
2017 Mar 03
0
Control statements with condition with greater than one should give error (not just warning) [PATCH]
>>>>> Henrik Bengtsson <henrik.bengtsson at gmail.com> >>>>> on Fri, 3 Mar 2017 00:52:16 -0800 writes: > I'd like to propose that the whenever the length of condition passed > to an if or a while statement differs from one, an error is produced > rather than just a warning as today: >> x <- 1:2 >> if (x == 1)
2004 Jun 26
0
Re: plot.new() warning from coplot()'s par(*, new=FALSE)
{diverted from the R-SIG-gui list} >>>>> "PD" == Peter Dalgaard <p.dalgaard@biostat.ku.dk> >>>>> on 26 Jun 2004 11:51:02 +0200 writes: PD> James Wettenhall <wettenhall@wehi.edu.au> writes: >> Hi, >> >> Does anyone know a good way to get rid of warnings like: >> Warning message: calling
2009 Apr 04
0
split.screen bug and patch
I hope it's OK to post a bug report, and a possible patch, on this list. Introduction ======= The split.screen() docs suggest that users should not return to a screen after it has been drawn, and that curious errors may result from doing so. This is clear from the test file I put below. However, I have found that this test file will work properly, with a tiny change to the split.screen
2017 Mar 03
2
Control statements with condition with greater than one should give error (not just warning) [PATCH]
On Fri, Mar 3, 2017 at 9:22 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>> Henrik Bengtsson <henrik.bengtsson at gmail.com> >>>>>> on Fri, 3 Mar 2017 00:52:16 -0800 writes: > > > I'd like to propose that the whenever the length of condition passed > > to an if or a while statement differs from one, an
2017 Mar 03
2
Control statements with condition with greater than one should give error (not just warning) [PATCH]
I'd like to propose that the whenever the length of condition passed to an if or a while statement differs from one, an error is produced rather than just a warning as today: > x <- 1:2 > if (x == 1) message("x == 1") x == 1 Warning message: In if (x == 1) message("x == 1") : the condition has length > 1 and only the first element will be used There are
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
1998 Feb 25
1
attributes
During the last couple of months (at least) there has been a trickle of messages on R-help related to attributes (other than dim/dimnames) not being inherited. Example: x <- 1 class(x) <- "test" class(x+1) [returns NULL, not "test"] I have not seen a response from anyone in the R-core about this issue. Since our group uses locally-written code (in S+) that is
1998 Jun 14
5
R-beta: R-0.62 is released
I've put up R-0.62.0.tgz up for FTP from Auckland some minutes ago. As usual, don't get it from there unless you are desperate, but wait for it to be mirrored at a CRAN site near you within a day or two. Note that beginning with this version, you need Fortran in some form or other to compile R. (f2c is good enough) Here is the relevant part of the CHANGES file: CHANGES IN R VERSION