search for: resi

...e log likelihood. Be aware that the calls to optim() take quite a while to execute; like 40 seconds on my laptop. Eternal gratitude for any words of wisdom on this matter! BTW, the recalcitrant parameter pair, used in the script below, is the pair of values which were used to simulate the data ``resi''. So they are the ``correct'' values. But optim() can't know that unless magic is loose in the world! Anyhow, there are other pairs, e.g. c(0.04,0.15),that result in the same behaviour. cheers, Rolf Turner rolf at math.unb.ca P. S. The help on optim() says...

...edge on R internals). I have four vectors a,b,c and z of size 10000 each. With these vectors I call .Call("hyp2f1forrey", a, b, b, z, PACKAGE = "hyp2f1") to access SEXP hyp2f1forrey(SEXP a, SEXP b, SEXP c, SEXP x) { int i,n; double *xa, *xb, *xc, *xx, *xresr, *xresi; SEXP resr, resi; n = LENGTH(a); PROTECT(a = AS_NUMERIC(a)); PROTECT(b = AS_NUMERIC(b)); PROTECT(c = AS_NUMERIC(c)); PROTECT(x = AS_NUMERIC(x)); PROTECT(resr = NEW_NUMERIC(n)); PROTECT(resi = NEW_NUMERIC(n)); xa = NUMERIC_POINTER(a); xb = NUMERIC_POINTER(b...

...this problem. ############################### f <- function(){ theta <- list(one=2.0, two=0.3, three=0.4) attach(theta) x <- c(one, two, three) sample(x, 1) } test <- function(n=400){ timeu <- numeric(n) for(i in seq(n)){ timeu[i] <- system.time({ resi <- f() })[3] } plot(timeu) } test() ############################## ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Li Dongfeng ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ldf-nospacm at math.pku.edu.cn ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2004-02-24

On May 28, 2009, at 6:03 PM, Jonathan Ragan-Kelley wrote: > In the current trunk, System/Atomic.[h,cpp] define void > llvm::sys::MemoryFence(). This conflicts with the MemoryFence macro in > <windows.h> and (since it's a preprocessor macro, and not a scoped > function definition) causes the sys::MemoryFence definition on > Atomic.cpp:23 to explode, as it's

Yes, indeed. On May 28, 10:41 pm, Owen Anderson <resis... at mac.com> wrote: > > Wait, it defines MemoryFence() AND MemoryBarrier()?? > > Sheesh, they had to take all the reasonable names.  :-/

En innebygd og tegnsett-uspesifisert tekst ble skilt ut... Navn: ikke tilgjengelig Nettadresse: https://stat.ethz.ch/pipermail/r-help/attachments/20080207/891f1e80/attachment.pl

On Apr 17, 7:01 pm, Owen Anderson <resis... at mac.com> wrote: > Gabor, > > Have you updated llvm2cpp to generate calls to the appropriate new Yes. These are caught by my conversion scripts. > constructors? Also, could you check the code in the tutorials to make > sure it matches the new API? Good point, will do. T...

Hey Duncan, hey everybody else, I just stumbled upon a problem in the latest llvm-gcc trunk which is related to my previous problem with the 64bit ABI and structs: Given the following code: struct float3 { float x, y, z; }; extern "C" void __attribute__((noinline)) test(float3 a, float3* res) { res->y = a.y; } int main(void) { float3 a; float3 res; test(a,

On Apr 18, 5:51 pm, heisenbug <ggr... at gmail.com> wrote: > On Apr 17, 7:01 pm, Owen Anderson <resis... at mac.com> wrote: > > > Gabor, > > > Have you updated llvm2cpp to generate calls to the appropriate new > > Yes. These are caught by my conversion scripts. > > > constructors?  Also, could you check the code in the tutorials to make > > sure it matches...

Hi Ralf, > llvm-gcc -c -emit-llvm -O3 produces this: > > %struct.float3 = type { float, float, float } > define void @test(double %a.0, float %a.1, %struct.float3* nocapture > %res) nounwind noinline { > entry: > %tmp8 = bitcast double %a.0 to i64 ; <i64> [#uses=1] > %tmp9 = zext i64 %tmp8 to i96 ; <i96> [#uses=1] >

Hi Ralf, > I do not understand why this behaviour is required. What is the problem > in having a function receive a single struct-parameter with three floats > compared to two scalar parameters? > > source-code (C++): > struct Test3Float { float a, b, c; }; > void test(Test3Float param, Test3Float* result) { ... } if you compile this with GCC, you will see that it too

Uh, sorry, did not pay attention where I was replying ;) Hey Duncan, I do not understand why this behaviour is required. What is the problem in having a function receive a single struct-parameter with three floats compared to two scalar parameters? source-code (C++): struct Test3Float { float a, b, c; }; void test(Test3Float param, Test3Float* result) { ... } bitcode:

On Jun 1, 2009, at 11:17 PM, Jonathan Ragan-Kelley wrote: > Yes, indeed. Are they macros or functions? If macros, why not just #undef them at the top of Atomics.h? -Chris > > > On May 28, 10:41 pm, Owen Anderson <resis... at mac.com> wrote: >> >> Wait, it defines MemoryFence() AND MemoryBarrier()?? >> >> Sheesh, they had to take all the reasonable names. :-/ > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu...

Gabor, Have you updated llvm2cpp to generate calls to the appropriate new constructors? Also, could you check the code in the tutorials to make sure it matches the new API? --Owen On Apr 15, 2008, at 5:32 PM, Gabor Greif wrote: > Hi All, > > here comes the patch for the second wave of Use class size reduction. > > I have included all the machinery that is needed, and it is

Is this actually the case? I can't find it documented anywhere on MSDN or the rest of the internet. --Owen On Jun 1, 2009, at 11:17 PM, Jonathan Ragan-Kelley wrote: > Yes, indeed. > > On May 28, 10:41 pm, Owen Anderson <resis... at mac.com> wrote: >> >> Wait, it defines MemoryFence() AND MemoryBarrier()?? >> >> Sheesh, they had to take all the reasonable names. :-/ > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu...

...to include main effect and/or covariate adjustments in the polygenic model statement pkin = kinship(pedigree[,2],pedigree[,3],pedigree[,4]) maineff1 = as.factor(SNPS[,1]) maineff2 = as.factor(SNPS[,2]) Yfit = polygenic(trait~maineff1+maineff2,pkin,simulation.GenABEL,trait.type="gaussian") resi = Yfit$pgresidualY When I calculated the GRAMMAR and ran the command, "*Yfit = polygenic(trait~maineff1+maineff2,pkin,simulation.GenABEL,trait.type="gaussian") *", the software gave an error alert as "*Error in polygenic(trait ~ maineff1 + maineff2, pkin, simulation.Ge...

...dio build. The trivial fix is to #undef MemoryFence immediately after including <windows.h>, since it's clearly assumed not to exist. A deeper and safer fix might consider avoiding a name conflict with a core system macro on a widely used platform. On May 17, 1:20 pm, Owen Anderson <resis... at mac.com> wrote: > On May 17, 2009, at 12:32 PM, Chris Lattner wrote: > > > Owen, I would really rather that you didn't take this path.  Threading > > support in LLVM should always be optional: it should be possible to > > use LLVM on systems where we don't...

I've "inherited" an old Lexmark Z11 and would like to plug it in to my CentOS 4 box as a second printer. I shut down, hooked it up to the parallel port, rebooted, and hwbrowser recognizes it on /dev/lp0, so I ran through setting it up as a queue with printconf-gui. However, printing the test page fails because the renderer "lz11.foomatic" is not found (details below for

On May 17, 2009, at 12:32 PM, Chris Lattner wrote: > Owen, I would really rather that you didn't take this path. Threading > support in LLVM should always be optional: it should be possible to > use LLVM on systems where we don't have support for threading > operations. Indeed, some systems don't support threads! I'm not trying to make it required. I had provided

Hi All, here comes the patch for the second wave of Use class size reduction. I have included all the machinery that is needed, and it is *active*. The User* inside of Use is even sometimes NULL, but the algorithm is able to recover it. If there is a non-null User* present, then I am asserting that it equals the computed value. I did not receive feedback for the algorithmic part yet, so I