search for: getcaller

Displaying 17 results from an estimated 17 matches for "getcaller".

Did you mean: getcallee
2012 Sep 17
2
"eval" inside a function call in connection with updating the data slot in the call of lmer
Dear list, Given a linear mixed model (from lme4) I want to 1) first change the input dataset and then 2) change the model formula. I want this to happen in a function call; Please see below. Options 1) and 2) below work whereas 3) fails with the message > foo() Error in is.data.frame(data) : object 'beets2' not found Question: What is it one must to in case 3) to have R look
2017 Feb 10
2
help me understand how nounwind attribute on functions works?
On Thu, Feb 9, 2017 at 8:41 AM, Reid Kleckner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Wed, Feb 8, 2017 at 5:45 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >> What isn’t clear to me still is : why shouldn't this be transitive? >> In the example you’re showing, for a caller of f() in bar, what is the >> advantage of knowing that f()
2015 Mar 22
2
robust updating methods
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 WARNING: this is long. Sorry I couldn't find a way to compress it. Is there a reasonable way to design an update method so that it's robust to a variety of reasonable use cases of generating calls or data inside or outside a function? Is it even possible? Should I just tell users "don't do that"? * `update.default()` uses
2009 Oct 27
1
recover and "called from" information
Hello, When using recover, the called from information is always "eval(expr, envir, enclos)", which is not particularly useful. > f <- function( ){ g <- function(){ stop( "ouch") }; g() } > options( error = recover ) > f() Error in g() : ouch Enter a frame number, or 0 to exit 1: f() 2: g() Selection: 1 Called from: eval(expr, envir, enclos) I'm
2015 Mar 24
2
robust updating methods
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15-03-23 12:55 PM, Thierry Onkelinx wrote: > Dear Ben, > > Last week I was struggling with incorporating lme4 into a package. > I traced the problem and made a reproducible example ( > https://github.com/ThierryO/testlme4). It looks very simular to > the problem you describe. > > The 'tests' directory contains
2018 Jan 20
2
Paquete pdp
Buenas. El Paquete pdp es muy fácil de usar, pero cuando se lo aplico a mis datos me da: Error in eval(stats::getCall(object)$data) : object 'x.data' not found. Os copio abajo un ejemplo de aplicación a un RF. El mio es de un boosted regression trees (paquete gbm). No sé si esa puede ser la razón del error. En el paquete pdp no especifica que sea solo para RF, aunque en los
2012 Jan 22
1
Calling update on an lm-object inside a function
Dear all, I want to update an lm (or glm) object by changing the response variable and I want to do so inside a function. Doing the update outside of a function is straight forward: x <- 1:5 y <- c(1,2,3,3,6) mm <- lm(y~x) y2 <- c(1,3,3,4,6) mm2<- update(mm, y2 ~ .) But I want to make the update inside a function (where the new response variable is declared inside the
2015 Mar 23
0
robust updating methods
Dear Ben, Last week I was struggling with incorporating lme4 into a package. I traced the problem and made a reproducible example ( https://github.com/ThierryO/testlme4). It looks very simular to the problem you describe. The 'tests' directory contains the reproducible examples. confint() of a model as returned by a function fails. It even fails when I try to calculate the confint()
2007 Nov 06
4
[LLVMdev] Dynamic (JIT) type resolution
Hi everyone, I would like to implement an equivalent mechanism of function callbacks in the JIT, but for fields. Typically in Java, when you compile a method, there may be some instructions (getfield, putfield) that depend on a type which is not yet resolved. I think the best way to do this in LLVM is to add an intrinsic. The intrinsic would be only valid if we jit, and would be lowered only in
2007 Nov 06
0
[LLVMdev] Dynamic (JIT) type resolution
Nicholas, I guess you're trying to solve the fragile base-class problem by deferring field offset calculations until JIT compilation time? Perhaps I'm missing something, but can't you accomplish this by using external constants in the source program, to be supplied at JIT/link time? external constant i32 @obj.x.offs; external constant i32 @obj.y.offs; define
2015 Mar 27
0
robust updating methods
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Sorry to those who don't like it for top-posting] Thierry, I'm curious whether this addresses your problem (although we don't have a hard timetable for the next release [it has to avoid conflicts with the 3.2.0 release in 2.5 weeks at the very least], so this might be problematic if your package needs to depend on it). I'm
2007 Nov 06
2
[LLVMdev] Dynamic (JIT) type resolution
Hi Gordon, Gordon Henriksen wrote: > Nicholas, > > I guess you're trying to solve the fragile base-class problem by > deferring field offset calculations until JIT compilation time? > > No. I'm deferring field offset calculation until /execution /time. > Perhaps I'm missing something, but can't you accomplish this by using > external constants in
2009 Jul 14
0
[LLVMdev] "Recursive compilation detected" and signals
Hello, Platform is RHEL5, GCC 4.2.4, x86-32, and LLVM/LLVM-GCC from subversion (yesterday evening). I'm compiling C code into bitcode, and then executing the bitcode using the JIT compiler (lli). I've managed to reproduce a problem when multiple signals go off around the same time. A sample program is below. The result is the "recursive compilation detected" JIT compiler
2018 Jan 17
4
Random Forests
Buenas tardes a todos. El paquete randomForest tiene la función treesize, que es el nº de nodos. Me dan valores realmente elevados (en torno a 1000), y eso me parece extraño. ¿sabéis si es así? Gracias, Manuel -- Dr Manuel Mendoza Department of Biogeography and Global Change National Museum of Natural History (MNCN) Spanish Scientific Council (CSIC) C/ Serrano 115bis, 28006 MADRID Spain
2011 Oct 31
0
R 2.14.0 is released
The byte pixies have rolled up R-2.14.0.tar.gz (codename "Great Pumpkin") at 9:00 this morning. This is a development release with several new features; see the list below for details. You can get it from http://cran.r-project.org/src/base/R-2/R-2.14.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For
2011 Oct 31
0
R 2.14.0 is released
The byte pixies have rolled up R-2.14.0.tar.gz (codename "Great Pumpkin") at 9:00 this morning. This is a development release with several new features; see the list below for details. You can get it from http://cran.r-project.org/src/base/R-2/R-2.14.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For
2015 Dec 03
3
Function attributes for LibFunc and its impact on GlobalsAA
----- Original Message ----- > From: "James Molloy via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Vaivaswatha Nagaraj" <vn at compilertree.com> > Cc: "LLVM Dev" <llvm-dev at lists.llvm.org> > Sent: Thursday, December 3, 2015 4:41:46 AM > Subject: Re: [llvm-dev] Function attributes for LibFunc and its impact on GlobalsAA > >