similar to: pairs and triples of a data.frame

I discover last week the R software statistics programm, I have a small questions, When we generate a bivariate normal distribution is it possible to plot the generate distribution. The second one if there is a code to generate a bivariate student distribution. If yes i would ask you gratefully a help. Thank you very much

Hi all, I am currently using the code snippet below to minimize a function which I wasn't able to minimize properly with optim (cliffy surface, constraints, poles). Obviously this iteration is probably the poorest way of implementing such a function and it is expectedly slow. I've already written some vectorized functions, but I'm afraid that I'm missing the "big

On 6/23/14, 8:31 AM, David Chisnall wrote: > On 23 Jun 2014, at 15:13, Renato Golin <renato.golin at linaro.org> wrote: > >> The main issue with your patch is that it can change user expected >> behaviour, and I can't tell you what is the expected behaviour in >> Darwin or BSD. If people usually use "unknown" in triples, this will >> break their

Hi Jonathan, The main issue with your patch is that it can change user expected behaviour, and I can't tell you what is the expected behaviour in Darwin or BSD. If people usually use "unknown" in triples, this will break their builds. If not, this could break the build of someone who does. My advice is to create a "default" mechanism for the affected targets, something

I still need to do some repetitive statistical analysis on some outcomes from a dataset. Take the following as an example; id sex hiv age famsize bmi resprate 1 M Pos 23 2 16 15 2 F Neg 24 5 18 14 3 F Pos 56 14 23 24 4 F Pos 67 3 33 31 5 M Neg 34 2 21 23 I want to know if there are statistically detectable differences in all of the continuous variables in

Hi, I have imported three text files into R using read.table. Their variables are called d, e and f. I want to run a function on all the possible combinations of these three files. The only way I know how to do that is like this: bigfunction(d,e) bigfunction(d,f) bigfunction(e,d) bigfunction(e,f) bigfunction(f,e) bigfunction(f,d) Is there an easier way? I will have five files later on, so

Hi Jonathan, This looks a bit odd. Any reason for the unknown->none conflating in this way? For most (all) of the ports unknown-elf works the same as none-elf. I'm also not sure if someone decided to have, arm-codesourcery-elf that this would still work with the patch. Thoughts? -eric On Tue, Jun 24, 2014 at 7:35 AM, Amara Emerson <amara.emerson at gmail.com> wrote: > Hi Jon,

> -----Original Message----- > From: Renato Golin [mailto:renato.golin at linaro.org] > Sent: 08 July 2015 16:09 > To: Daniel Sanders > Cc: LLVM Developers Mailing List (llvmdev at cs.uiuc.edu); Eric Christopher > (echristo at gmail.com); Jim Grosbach (grosbach at apple.com) > Subject: Re: The Trouble with Triples > > On 8 July 2015 at 15:31, Daniel Sanders

After re-reading your last couple emails with the benefit of sleep, that all makes sense to me. The user/driver would be responsible for ensuring each tool is called with the same options, while each tool is responsible for using the same TargetTuple in all its calls to LLVM. The only bit I'm unsure about w.r.t to not having a serialization in the IR is the ModuleLinker where we currently have

> Another very annoying fact is that the Clang driver re-parses triples many > times, and sometimes they change the triple based on a CPU, and then end > up with a different CPU. I’ve recently been tasked with cleaning this up. Before starting on this full gusto, I want to make sure I’m not stepping on any toes or duplicating work. The rough plan is as follows; 1. Replace the call to

Hi Daniel, I'm not sure I agree with the basic idea of using the target triple as a way of encoding all of the pieces of target data as a string. I think in a number of cases what we need to do is either open up API to the back end to specify things, or encode the information into the IR when it's different from the generic triple. Ideally the triple will have enough information to do

[+llvmdev, -llvm-dev] (Oopsies, llvmdev doesn't have a hyphen in it like all the others do) On 6/17/14, 10:45 AM, Jonathan Roelofs wrote: > [+llvm-dev, cfe-dev] > > Was "Re: [PATCH] ARM: allow inline atomics on Cortex M" > > On 6/17/14, 10:42 AM, Jonathan Roelofs wrote: >> >> >> On 6/17/14, 9:35 AM, Renato Golin wrote: >>> On 17 June 2014

On 31 July 2015 at 17:47, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > After re-reading your last couple emails with the benefit of sleep, that all makes sense to me. The user/driver would be responsible for ensuring each tool is called with the same options, while each tool is responsible for using the same TargetTuple in all its calls to LLVM. The only bit I'm unsure about

Does anyone know what target triples are used for Cygwin and mingw? If someone has a GCC compiler available for one of these systems, typing 'gcc -v' should tell. Thanks! -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/

Hello, I see that in the 2.8 source the target triples are enums. This means that if I am to avoid conflicts in the future that I will have to push changes back to the LLVM SVN. Would it be fair to say that patches are welcome in that regard? I'm in the process of adding support for i386-PC-AROS. Thanks for your consideration, --Sam Crow

On 30 July 2015 at 15:30, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > I haven't fully researched why the triple is there but one reason is to make backends target the same target as the frontends. Consider the case where clang is used to generate IR and then llc is used to compile it. We currently use the information in the IR to set the GNU triple, the target features,

On 9 July 2015 at 10:39, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > The use-case that I’d really like to go from mostly-working to actually-working is the ability to create symlinked versions of clang with a triple prefix and have it behave sensibly. We can symlink clang to mips64-unknown-freebsd-clang and get a working cross-compiler, more or less, except that we also want

> -----Original Message----- > From: Renato Golin [mailto:renato.golin at linaro.org] > Sent: 30 July 2015 15:07 > To: Daniel Sanders > Cc: Eric Christopher; LLVM Developers Mailing List (llvmdev at cs.uiuc.edu); > Jim Grosbach (grosbach at apple.com) > Subject: Re: The Trouble with Triples > > On 30 July 2015 at 14:52, Daniel Sanders <Daniel.Sanders at

Dear useR I want to know why package gregmisc did not work very well. I did not find this package in my library directory. > local({a <- CRAN.packages() + install.packages(select.list(a[,1],,TRUE), .libPaths()[1], available=a, dependencies=TRUE)}) trying URL `http://cran.r-project.org/bin/windows/contrib/2.0/PACKAGES' Content type `text/plain; charset=iso-8859-1' length 21630 bytes

> -----Original Message----- > From: Renato Golin [mailto:renato.golin at linaro.org] > Sent: 08 July 2015 19:01 > To: Daniel Sanders > Cc: LLVM Developers Mailing List (llvmdev at cs.uiuc.edu); Eric Christopher > (echristo at gmail.com); Jim Grosbach (grosbach at apple.com) > Subject: Re: The Trouble with Triples > > On 8 July 2015 at 17:43, Daniel Sanders