similar to: Different results for different order of factor levels?

Hi, I am trying to run a panel regression where I have a matrix of observations and a matrix of independant variables - examples would trying to predict countries's GDP with their data on education, FDI, tax rates, over time. For the purpose of simplicity, my data would be: dep = matrix(rnorm(50),ncol=5) indep1 = matrix(rnorm(50),ncol=5) indep2 = matrix(rnorm(50),ncol=5) >From what I

Dear subscribers, I am looking for a function which would allow me to model the dependent variable as the number of successes in a series of Bernoulli trials. My data looks like this ID TRIALS SUCCESSESS INDEP1 INDEP2 INDEP3 1 4444 0 0.273 0.055 0.156 2 98170 74 0.123 0.456 0.789 3 145486 30 0.124

Hello everybody, I have experience coding with R, but am brand new to R Shiny. I am trying to produce an application that will allow users to upload their own dataset, select columns they want an ANOVA analysis run on, and generate graphs that will allow users to view their results. However, I am getting the following error: *"Argument is of length zero."* Being new to Shiny, I am

Hello, could anyone explain what am I doing wrong. When I use colldiag function from package perturb I get different Variance Decomposition Proportions matrix in R than in SAS, although the eigenvalues and indexes are the same. Thanks for your attention. Results: in R: eigen(cor(indep2)) $values [1] 4.197131e+00 6.674837e-01 9.462858e-02 4.070314e-02 5.323022e-05 colldiag(indep2,c=T)

Dear all, I am attempting to perform what should be a relatively simple calculation on a number of data frame columns. I am hoping to find the average on a per-row basis for each of the 50 columns. If on a particular row a 'NA' value is encountered, then this should be ignored and the mean formed on the basis of the other rows. However, I'm finding that the end result for each row

hi i try to use arima and holtwinter to predict drought from 1895-2006 but i cannot read whole period of time and i try to do the exponent fitting, but it comes out as the coordinate x-y error i send the source code and data to take a look if anyone can help me, i am really new in R thank u so much jam

Hello. That's what I've got from ld: /usr/lib/libxenguest.a(xg_private.o): In function `unlock_pages': (.text+0x490): multiple definition of `unlock_pages' /usr/lib/libxenctrl.a(xc_private.o):(.text+0x6a0): first defined here /usr/lib/libxenguest.a(xg_private.o): In function `lock_pages': (.text+0x4d0): multiple definition of `lock_pages'

On 20/10/12 03:15, Michael Spencer wrote: > On Fri, Oct 19, 2012 at 2:55 AM, r4start <r4start at gmail.com> wrote: >> Hi all. >> >> While compiling next code >> @A = weak unnamed_addr constant { i32, i32, i32 } { i32 0, i32 0, i32 0 }, >> section ".data" >> was discovered that llc ignores weak linkage if we emit it in COFF object. >>

Getting closer... When emitting symbols, how do I set the symbol's value to the address of the current instruction? Do I need to emit a label in the current section and another that uses the former to point to the latter? If possible, a code sample would be very helpful. And probably questions for Tim, are these "section-relative" mapping symbols, as defined in 4.6.5.1 of the

Hello -- I desperately want to start using Ogg compression on music I release on the internet, but I am encountering a fair amount of artifacts. I noticed some in beta4 and was hoping they would disappear with RC1. However, I've been playing with RC2 and I've still been banging my head into a number of problems. A majority of the music I make has long drones with a fair amount of spectral

Hi David, On Thu, Jun 7, 2012 at 10:17 AM, Fan Dawei <fandawei.s at gmail.com> wrote: > Could you please tell me more about $a, $t and $d symbols? How these symbols > are used to define different regions? Where I can find this symbols in ELF > object file? At the start of each range of ARM code, an assembler or compiler should produce a "$a" symbol with that address, and

Compiling llvm on a linux/amd64 box produces: home/rafael/dev/llvm/build/Debug/lib/LLVMX86.o: In function `_X86CompilationCallback': (.text+0x316fe): undefined reference to `_X86CompilationCallback2' /home/rafael/dev/llvm/build/Debug/lib/LLVMX86.o: In function `llvm::X86JITInfo::getLazyResolverFunction(void* (*)(void*))': /home/rafael/dev/llvm/cvs/lib/Target/X86/X86JITInfo.cpp:219:

On Jun 7, 2012, at 7:53 AM, Fan Dawei <fandawei.s at gmail.com> wrote: > Hi Tim, > > Thanks a lot for your help! I'm very grateful. > > libc.so is a prelinked library, I'll build a non-prelinked one and have another try. > > I'm now at the start of a binary translation project. I want to convert ARM binary code [*] to llvm ir, which is then translated to

That depends on how you define "one ARM instruction." It's not a clear cut thing. For example, is "add r1, r2, r3" the same ARM instruction as "add r1, r2, #4"? What is a distinct instruction and what's a variant encoding of the same instruction is often entirely a matter of convenience. -Jim On Jun 8, 2012, at 6:40 AM, Fan Dawei <fandawei.s at

Hi Tim, Thanks a lot for your help! I'm very grateful. libc.so is a prelinked library, I'll build a non-prelinked one and have another try. I'm now at the start of a binary translation project. I want to convert ARM binary code [*] to llvm ir, which is then translated to binary for our mips like architecture. That's why I'm looking for a decoder for ARM binary. The

Hi Jim, Thanks for reply. I'm sorry I didn't make myself clear enough. The MCInst created by MCDisassembler depends on the instructions defined in td files. These instructions do not have a one to one mapping to ARM instructions. There are usually one or more instructions defined in the td file correspond to one actual ARM instruction. Thanks, David On Thu, Jun 7, 2012 at 1:27 PM, Jim

On 16 October 2012 03:16, Greg Fitzgerald <garious at gmail.com> wrote: > Lastly, from MCELFStreamer, how do I determine if we generating an ARM or > Thumb ELF? That was the only part I didn't know how to get. Jim should know. > I can catch Thumb from the EmitThumbFunc, but that seems a > little odd. Ignore EmitThumbFunc, it has nothing to do with your change. > $

Some doxygen annotations are attached to the wrong entry, which can be misleading. This patch fixes the mistake everywhere I could find it. --- include/llvm/InstrTypes.h | 54 ++++++++++++++++++++-------------------- include/llvm/MC/MCDirectives.h | 42 +++++++++++++++--------------- include/llvm/Pass.h | 10 +++--- 3 files changed, 53 insertions(+), 53 deletions(-) diff

CC llvm-dev ---------- Forwarded message ---------- Hello Duncan The size of ARM binaries created by clang has increased after r236642. Would you be able to find some time to look at my findings and share your thoughts about the problem, please? r236642 prevents emitting of temp label names into object files to save memory. This is fine, the label names do not appear in the resulting binaries.

Attached is an example of how to reproduce the issue. It uses a C file that happens to has a bunch of switch statements which are encoded as jump tables, giving us data-in-code. Usage: To build object files with clang via the -integrated-as versus via GCC: $ export NDK_DIR=<my_ndk_dir> $ export LLVM_DIR=<my_llvm_bin_dir> $ make To test that the generated objects contain the same