search for: catchability

...e, however I also want to include random effects and I'm not sure how to construct a model that incorporates both of these things. Data was collected from 6 different groups of 6 individuals with 10 replicates for each group. Whether an individual was caught in a trial or not was called "Catchability" and the outcome is binomial (caught = 1, not caught = 0). "Catchability" is my response variable that I want to see if I can explain by the other variables. "Individual" and "Group" would be my random effects. I have already installed lme4 but not sure how to cod...

Just for the record (not a request for fix) and an ad hoc workaround if anyone needs it: REASON: Running an R script as a plugin on a remote Suse Linux 8.2 with R v2.1.0 (2005-04-18), I have noticed that capabilities() generates (to standard error) Xlib: connection to "base:0.0" refused by server Xlib: Client is not authorized to connect to Server which cannot be caught by

Hi Philip, Thanks for the positive response from all of you! > One question: How are you handling EOM? Error return? Custom region allocator? When running into an Out-of-memory situation we're currently only doing an error return, i.e. the compilation fails, but does so without crashing the process in which the compilation/jitting occurs. It is ok for us if llvm returns with a

----- Original Message ----- > From: "Philipp Becker" <philipp.becker at sap.com> > To: "Philip Reames" <listmail at philipreames.com>, "LLVM Dev" <llvmdev at cs.uiuc.edu> > Sent: Friday, December 13, 2013 6:55:59 AM > Subject: Re: [LLVMdev] Making LLVM safer in out-of-memory situations > > Hi Philip, > > Thanks for the

Dear R-Team! I am a beginner in R and use the WISP library for a project. I am using mark-recapture to estimate abundance. I would like to know if it is possible to only survey a part of the created area (with the created population) and not all of it. I am trying to quantify bias introduced by non random sampling design (i.e. the area is 24x100 but I only wanna search 24x40) Thank you already in

On 12/12/13 4:25 AM, Gasiunas, Vaidas wrote: > Hello, > > Philipp Becker and me, Vaidas Gasiunas, are developers at SAP and part of a team developing a C-like domain-specific language for the SAP HANA in-memory database. We use LLVM as a backend to translate our language to native code, primarily on x86-64 platforms. Our programs are created dynamically, compiled and optimized in a

Hi Hal, > Does this mean that you're using C++ exception handling to manage the cleanup? No, not really. From the place where we're calling into llvm we are catching all exceptions that may occur during compilation, but normally we do not add any additional catch clauses into the llvm source itself. We mainly rely on correct stack unwinding by destructors in llvm when an exception is

Hello, Philipp Becker and me, Vaidas Gasiunas, are developers at SAP and part of a team developing a C-like domain-specific language for the SAP HANA in-memory database. We use LLVM as a backend to translate our language to native code, primarily on x86-64 platforms. Our programs are created dynamically, compiled and optimized in a running database. As a result of that we have special

I'm having trouble understanding the value in the way exceptions are handled on Linux, the dwarf/system V ABI exception spec. The mechanism allows for both cleanup routines and catch handlers, where by cleanup handlers don't stop the search for a normal handler. The personality function (I guess no longer part of the standard, but a C++ thing) can also compare types of the landingpads.

Hi everyone! I've been silently working on the previous exception handling proposal I published last year (http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-November/027311.html). However, there were some major deficiencies in it. After discussing this further with Jim Grosbach and John McCall, we've come up with another proposal. As you can see, it incorporates the idea of