similar to: axTicks on a reverse ylog plot (PR#7973)

Displaying 20 results from an estimated 1000 matches similar to: "axTicks on a reverse ylog plot (PR#7973)"

2005 Jun 28
2
boxplot by factor (Package base version 2.1.1) ( PR#7976)
The issue is not with boxplot, but with split. boxplot.formula() calls boxplot(split(split(mf[[response]], mf[-response]), ...), but look at what split() returns when there are empty levels in the factor: > f <- factor(gl(3, 6), levels=1:5) > y <- rnorm(f) > split(y, f) $"1" [1] 0.4832124 1.1924811 0.3657797 1.7400198 0.5577356 0.9889520 $"2" [1] -1.1296642
2005 Jun 28
0
boxplot by factor (Package base version 2.1.1) (PR#7976)
I consider this to be an old bug, which also persists in Splus 7. It is unnecessary, and annoying. ## Section 1: Consider a simple data frame with three possible factors (in levels) d <- data.frame(a=sort(rnorm(10)*10), b=factor(c(rep("A",4), rep("C", 6)), levels=c("A","B","C"))) tapply(d$a, d$b, mean) # returns three results, which I
2001 May 29
2
format for tick labels
Running R 1.2.3, Windows 98 I checked the archives, and I couldn't find anything pertaining to this: How do I control format (scientific notation versus decimal, e.g.) on tick labels? TIA, Henry Dr. M. Henry H. Stevens Postdoctoral Associate Department of Ecology, Evolution, & Natural Resources 14 College Farm Road Cook College, Rutgers University New Brunswick, NJ 08901-8551 email:
2011 Feb 11
1
How to compute "yaxp" and "usr" without plotting ?
Dear all, I'd like to know how I could compute the parameters "yaxp" and (the y components of) "usr" without having to plot the data first. Note that "ylim" is /a priori/ fixed. The aim is to automatically adjust the parameter "mgp" without having to make the plot twice. Then, with "yaxp" and "usr" known, it should be easy to
1997 May 21
1
R-alpha: plot(1); axis(1, at=10) >>> Seg.fault -- and a patch
This problem has been mentioned by Arne Kovac <maak@stats.bris.ac.uk> on May 9-10. The patch is really a replacement of 'axis' in RHOME/src/library/base/funs/ It contains the fixes which where proposed Arne Kovac and fixes (all?) the errors he/she (?) reported on May 9. "axis" <- function (which, at, labels = TRUE, ...) { if (which%%2 == 1) { axp <-
2004 Feb 19
1
Possible error in ?axTicks
Hi all, Before posting to r-bugs, I thought that I would just verify this one first. It looks like the help for axTicks() needs to be corrected. It presently says: 'axTicks()' can be regarded as an R implementation of the C function 'CreateAtVector()' in '..../src/main/graphics.c' which is called by 'axis(side,*)' when no argument 'at' is specified.
2007 Apr 07
2
Setting where the x-axis crosses the y-axis
Hi all, my apologies for a probably very obvious question but i can't figure out if, on a bar plot, there is a simple way to have the x-axis cross the y-axis at 1, when the y-axis is on a log-scale? I want to draw a bar plot, and have some of the bars "drop" below 1 while starting from 1. Is this possible? I have been trying various things using barplot, barplot2 etc... without
2004 Apr 15
1
pretty for a log-axis
Is there a function that does the same as pretty but on a log-scale? Suppose you have x <- exp( runif( 100, 0, 6 ) ) (which will between 1 and 403), then I would like to have a result like: log.pretty( x ) [1] 1 5 10 50 100 500 Bendix C. ---------------------- Bendix Carstensen Senior Statistician Steno Diabetes Center Niels Steensens Vej 2 DK-2820 Gentofte Denmark tel: +45 44 43 87 38
2011 Feb 04
1
axTicks.Rd documentation bug
?axTicks says: usr: numeric vector of length four, defaulting to ?par("usr")? giving horizontal (?x?) and vertical (?y?) user coordinate limits. but this is not how the function is implemented -- in fact 'usr' should be a vector of length two corresponding to the appropriate elements of par("usr") [1:2 if side is 1 or 3, 3:4 if side is 2 or
2005 Aug 18
2
axTicks and window resizing
Dear listers, I have written a function to facilitate the drawing of altitude profiles with x (distance), y (altitude) and a z parameter (altitude magnification). profplot<-function(x,y,z=10,...){ op <- par()$mai par(mai=c(0.95625,0.76875,0.76875,0.95625)) plot(x,y*z, type="l",asp=1,las=1,xlab="",ylab="",yaxt="n",...)
2012 Dec 15
3
Cannot build custom locale with utf-8 charset
I am trying, without success, to compile a custom locale for the utf-8 character set. I have issued this command: localedef --no-archive -f UTF-8 -i /usr/share/i18n/locales/en_CA at yyyy-mmm-dd en_CA at yyyy-mmm-dd.utf8 which produces the requisite files without reporting an error but which none-the-less insists on using the iso-8859-1 charset: LC_ALL=en_CA at yyyy-mm-dd locale charmap
2005 Oct 08
1
how to control ticks in plots with yasp or xasp
Hi, A few times I tried to control the number and position of tick marks in plots with the yasp or xasp parameters. For example, a y axis was drawn by default with tick marks at 0, 20, 40, 80 and 100. I tried to get tick marks every 10 by adding yasp=(0, 100, 10) but this had no effect at all. I know I can draw the axis and tick marks manually, but often this simple option would suffice
2010 Aug 18
2
'panel.smooth' error
Hi, The following call: xyplot(incidence ~ year, melanoma, panel=panel.smooth) produces a blank plot region with an error message: Error using packet 1 plot.new has not been called yet > sessionInfo() R version 2.11.1 (2010-05-31) x86_64-pc-linux-gnu locale: [1] LC_CTYPE=en_CA.UTF-8 LC_NUMERIC=C LC_TIME=en_CA.UTF-8 LC_COLLATE=en_CA.UTF-8 LC_MONETARY=C
2007 Jun 27
1
error message from lmer
Hi, I've begun to use the lme4 package, rather than nlme, for more flexibility during modelling, and running the examples in lmer I receive this error message: ---<---------------cut here---------------start-------------->--- R> (fm1 <- lmer(Reaction ~ Days + (Days|Subject), sleepstudy)) Error in printMer(object) : no slot of name "status" for this object of class
2009 Jul 25
1
yaxp problem for more irregular time series in one plot
Good day, I'm trying to get more time series in one plot. As there are bigger differences in values of variables I need logaritmic y axis. The code I use is the following: nvz_3_data <- read.csv('/home/tomas/R_outputs/nvz_3.csv') date <- (nvz_3_data$date) NO3 <- (nvz_3_data$NO3) NH4 <- (nvz_3_data$NH4) date_p <- as.POSIXct(date, "CET") par(mfrow=c(2,1), ylog
2024 Apr 25
1
[External] View() segfaulting ...
I saw it also on some of my Ubuntu builds, but the issue went away after a make clean/make, so maybe give that a try. Best, luke On Wed, 24 Apr 2024, Ben Bolker wrote: > I'm using bleeding-edge R-devel, so maybe my build is weird. Can anyone > else reproduce this? > > View() seems to crash on just about anything. > > View(1:3) > *** stack smashing detected ***:
2006 Oct 27
2
POSIXct time zone and daylight savings issues
Hello, Suppose we need a function that takes a POSIXct object and need to calculate the time difference between it and GMT time: gmtDiff <- function(time) { time.gmt <- as.POSIXct(format(time, tz="GMT")) time.plt <- as.POSIXlt(time) dlstime <- ifelse(time.plt$isdst > 0, 1, 0) timezone <- as.numeric(difftime(time, time.gmt, units="hours"))
2011 Dec 09
3
bug in sum() on integer vector
Hi, x <- c(rep(1800000003L, 10000000), -rep(1200000002L, 15000000)) This is correct: > sum(as.double(x)) [1] 0 This is not: > sum(x) [1] 4996000 Returning NA (with a warning) would also be acceptable for the latter. That would make it consistent with cumsum(x): > cumsum(x)[length(x)] [1] NA Warning message: Integer overflow in 'cumsum'; use
2009 Oct 06
1
vignette() failure
Hi, I can't pinpoint exactly since what R version I first noticed this error, but are others seeing this? R> vignette("grid") R> sh: : command not found instead of having the vignette displayed in the proper viewer? This is with: R> sessionInfo() R version 2.9.2 (2009-08-24) x86_64-pc-linux-gnu locale:
2009 Oct 22
1
r-cran-lattice build
Hi, After the latest update of r-cran-* packages in sid, I'm getting the following message on startup: During startup - Warning message: package 'lattice' was built under R version 2.9.2 and help may not work correctly I haven't found anything wrong with the package's functionality so far though. ---<--------------------cut