search for: nonequivalent

The Toolkit for Weighting and Analysis of Nonequivalent Groups (twang 1.0) has been released to CRAN. The package collects functions useful for computing propensity score weights for treatment effect estimation, developing nonresponse weights, and diagnosing the quality of those weights. The package includes a vignette containing some basic theory and w...

Hi Piotr, I think makes sense. Modulo bitcasts, the invariant is identified by a particular pointer SSA value. Given that you can't sensibly have two nonequivalent invariants associated with the same pointer SSA value simultaneously, there's no need to also identify the invariant with a metadata string as well. When we need a new "identifier" for the pointed-to value, we get one using invariant.group.barrier. -Hal On 01/24/2017 01:39 PM,...

...function when variables are stored as factors and was hoping someone could provide some advice on how to proceed. I am running propensity score matching as outlined in: Greg Ridgeway, Dan McCarey, Andrew Morral, Lane Burgette and Beth Ann Grin (May 3, 2013) Toolkit for Weighting and Analysis of Nonequivalent Groups: A tutorial for the twang package and have a question about using unordered categorical variables as a covariates. The tutorial indicates that: "There is no need to ? create indicator, or dummy coded, variables to represent categorical covariates, provided the categorical variables a...

...25 January 2017 at 15:03, Hal Finkel via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> Hi Piotr, >> >> I think makes sense. Modulo bitcasts, the invariant is identified by a >> particular pointer SSA value. Given that you can't sensibly have two >> nonequivalent invariants associated with the same pointer SSA value >> simultaneously, there's no need to also identify the invariant with a >> metadata string as well. When we need a new "identifier" for the pointed-to >> value, we get one using invariant.group.barrier. >>...

...l Finkel via cfe-dev < >> cfe-dev at lists.llvm.org> wrote: >> >>> Hi Piotr, >>> >>> I think makes sense. Modulo bitcasts, the invariant is identified by a >>> particular pointer SSA value. Given that you can't sensibly have two >>> nonequivalent invariants associated with the same pointer SSA value >>> simultaneously, there's no need to also identify the invariant with a >>> metadata string as well. When we need a new "identifier" for the pointed-to >>> value, we get one using invariant.group.barrie...

...to:cfe-dev at lists.llvm.org>> wrote: >> >> Hi Piotr, >> >> I think makes sense. Modulo bitcasts, the invariant is >> identified by a particular pointer SSA value. Given that >> you can't sensibly have two nonequivalent invariants >> associated with the same pointer SSA value >> simultaneously, there's no need to also identify the >> invariant with a metadata string as well. When we need a >> new "identifier" for the pointed-to v...

A friend of mine made the following comment in a discussion I had with him that on a website we adminster we should offer a) WAV or maybe shorten files b) Ogg as a decent reference lossy encoded version He's been trying to convince me that we should offer MP3 (in lieu of WAV) and possibly Ogg. The audio files are primarily vocals I am not a physics guy but his statements don't

Hi all, I would like to propose a new way clang would decorate vtable loads in order to handle devirtualization better. I've added *llvm-dev* also, because this can start a discussion about changing invariant.group to just invariant. PDF version of this RFC can be found here: https://drive.google.com/file/d/0B72TmzNsY6Z8ZmpOUnB5dDZfSFU/view?usp=sharing Background: Initial old design: