similar to: Fwd: [R-SIG-Mac] Window titles

On Mon, 6 Feb 2006 18:12, Simon Urbanek wrote: > On Feb 6, 2006, at 5:24 PM, Paul Roebuck wrote: > >> Tried on R-Sig-Mac with no responses, but I need some kind >> of answer. >> [...] >> Does the following work on your system? > > Interesting, no, it doesn't either. For png and pdf I use > Quartz + quartz.save (it produces much nicer results) so > I

I meant to send this to R-help, but it went to Gabor instead... This is my shot at it using diff(), assuming breaks is in non-decreasing order: chop <- function(x, breaks) { s <- sign(x - breaks) if (x <= breaks[1]) { ans <- x } else { numPieces <- sum(s == 1) ans <- diff(c(0, breaks[1:numPieces], x)) } ans } Some tests: >

What a delicious example! (I'm taking the liberty of sharing it with r-devel, since it raises some good issues.) You have two questions, presumably: 1 - how could the order of the setMethod calls make a difference in the results? 2 - what's causing the infinite loop & how could it be avoided, reliably? Second question first. The danger sign is the "vector" method:

Can the value of a list element be referenced from a sibling list element during list creation without the use of a temporary variable? The following doesn't work but it's the general idea. > list(value = 2, plusplus = $value+1) such that the following would be the output from str() List of 2 $ value : num 2 $ plusplus: num 3

How would one go about getting sprintf to use the values of a vector without having to specify each argument individually? > v <- c(1, 2, -1.197114, 0.1596687) > iv <- c(3, 1, 2, 4) > sprintf("%9.2f\t%d\t%d\t%8.3f", v[3], v[1], v[2], v[4]) [1] " -1.20\t1\t2\t 0.160" Essentially, desired effect would be something like: >

What's the best way to simulate Recall for parent function? Consider this one-time recursive code: alwaysEven <- function(x) { handleOdd <- function(x) { alwaysEven(x-1) # use Recall-like here } return(if (x %% 2) handleOdd(x) else x) } any2even <- alwaysEven rm(alwaysEven) any2even(3) ---------------------------------------------------------- SIGSIG --

Was looking at what was output for <pkgname>-package.Rd and wondered if any there was any means (via macro, etc) to merge some of the same information with a template for my package manpage? As much (all?) of the generated information was already provided in the DESCRIPTION, I'd prefer not to have to update the information in multiple places. I'm thinking here that I could provide a

I have the following: > a <- matrix(1:10, nrow = 2, byrow = TRUE) > b <- array(as.integer(0), c(7, 5)) > idx <- list() > length(idx) <- 2 > dim(idx) <- c(1, 2) > idx[[1]] <- as.integer(1:2) > idx[[2]] <- as.integer(1:5) I can do the following, which works if 'b' is a matrix. > b[idx[[1]], idx[[2]]] <- a > b [,1] [,2] [,3] [,4] [,5]

I have some code where the primary dispatching is on other parameters so I'd like not to have to create a set of functions for "matrix" and another duplicate set for "array". But the class union technique isn't working as implemented below and I don't have my Green book with me. How do I fix my infinite recursion problem?

At this point I would just due: formals(body(method)[[2L]]) At some point we need to figure out what to do with this .local() confusion. On Wed, Jan 28, 2015 at 10:07 AM, Roebuck,Paul L <PLRoebuck at mdanderson.org> wrote: > I'm attempting to reflect the information for use with corresponding > fields in GUI (in a different package), to provide default values, > argname

I'm attempting to reflect the information for use with corresponding fields in GUI (in a different package), to provide default values, argname as key for UI label lookups, etc. So I want something much more like the formals of the implementation: { "object", "method": c("median", "vs", "tukey"),

Paul Roebuck wrote: >I have the following contrived code in package format. >On Solaris and Mac OS X, code runs just fine. On Windows, >it crashes the R environment with the "Send Bug Report" >dialog. I tried R 1.8.1 (Win2K) and R 1.9 (WinXP) binaries >with the same result. PCs otherwise appear properly >configured for creating R packages. Anything blatantly >wrong?

Dear list, I found a strange behavior of the graphic display when using bquote to set a title to a plot. The problem arise when you manually resize the graphic window using the mouse. It happens on both quartz and x11 devices. Here's a reproducible example: par(mfrow = c(1,3)) for (i in 1:3){ title <- as.expression(bquote(gamma[.(i)])) plot(1:10, main = title) } Once you ran the

I recently encountered this and was wondering if someone could explain what happened. Basis of question involves what the difference between the calls makes as the end result is the same: > identical(matrix(1:8, nrow = 1), array(1:8, c(1, 8))) TRUE If I run the code below as shown, I get the following: > foo(1:8, 4) foo (vector, numeric) val = 4 foo (matrix, ANY) val = 500 foo

On Jan 28, 2015, at 6:37 PM, Michael Lawrence <lawrence.michael at gene.com> wrote: > At this point I would just due: > > formals(body(method)[[2L]]) > > At some point we need to figure out what to do with this .local() confusion. Agreed, definitely. The current hack is to avoid re-matching arguments on method dispatch, so a fix would need to be fairly deep in the

Under Details section for as.Date: as.Date will accept numeric data (the number of days since an epoch), but only is origin is supplied. ^^ should be "if" R version 2.7.0 Patched (2008-06-04 r45830) ---------------------------------------------------------- SIGSIG -- signature too long (core dumped)

Those are good news. Prof Brian Ripley wrote: > You didn't tell us the version of R. quartz() is different in 2.7.0 > alpha, and there the function arguments do work (and the size is > really as advertised and not at a notional 72dpi). In fact, it is a > much more standard device and interface, so less to learn. > I assumed that > version provides most of the

Is there a means to split a vector into its individual elements without going the brute-force route for arguments to a predefined function call? offred.rgb <- c(1, 0, 0) * 0.60; ## Brute force style offred.col <- rgb(offred.rgb[1], offred.rgb[2], offred.rgb[3], names = "offred") ## Desired style

Anyone aware of tools available that can provide complexity metrics and/or code coverage analysis for R source? ---------------------------------------------------------- SIGSIG -- signature too long (core dumped)

Hi All, I am looking for help in rotating species titles produced using the strat.plot( ) function in the rioja package. This function produces a stratigraphic plot of paleoenvironmental data. Currently the titles of each species are plotted vertically while they are typically plotted at a 45 degree angle in other programs. Does anyone have any idea of how to rotates these titles? Below is an