search for: orthoganal

Displaying 4 results from an estimated 4 matches for "orthoganal".

2010 Dec 03
3
Checking for orthogonal contrasts
A common point made in discussion of contrasts, type I, II, III SS etc is that for sensible comparisons one should use contrasts that are 'orthogonal in the row-basis of the model matrix' (to quote from http://finzi.psych.upenn.edu/R/Rhelp02/archive/111550.html) Question: How would one check, in R, that this is so for a particular fitted linear model object? Steve Ellison
2011 Feb 23
0
[LLVMdev] New TargetSpec 'llvmnote'
...at take -arch have to map them onto something internally. Most of these are motivations for refactoring and code cleanup, but not really for inventing a new target mini-language to replace triples. The main problems with triples IMHO which motivate this are: - The vendor field is vague and non-orthoganal. - Triples don't represent subtarget attributes, except in the way that subtarget attributes are sometimes mangled into the architecture field in confusing ways. At an initial read, the targetspec proposal's solutions to these problems seem reasonable. It's a little surprisi...
2011 Feb 23
7
[LLVMdev] New TargetSpec 'llvmnote'
Hi All, There is recently a discussion on the LLDB list about how to deal with targets, and our current mismash of llvm::Triple and the various subclasses of TargetSubtarget leave a lot to be desired. GNU target triples are really important as input devices to the compiler (users want to specify them) but they aren't detailed enough for internal clients. Anyway, in short, I think that we
2011 Feb 23
2
[LLVMdev] New TargetSpec 'llvmnote'
...something internally. > > Most of these are motivations for refactoring and code cleanup, but not > really for inventing a new target mini-language to replace triples. > > The main problems with triples IMHO which motivate this are: > > - The vendor field is vague and non-orthoganal. > - Triples don't represent subtarget attributes, except in the way that > subtarget attributes are sometimes mangled into the architecture field > in confusing ways. > > At an initial read, the targetspec proposal's solutions to these > problems seem reasonabl...