search for: _means_

I'm having trouble with a simple application with metRology. I need to estimate the uncertainty of the density thickness of seven sheets of film. This is calculated from measurements of mass, length and width of rectangular samples of film. It's not too hard to calculate the whole thing with a little Monte Carlo loop. I get about 0.07 with this: #sample area

...le time information (i.e. source description) there are (a) no references to undefined types, (b) no pointers to undefined symbols, (c) etc. These are all syntactic constructs that can be checked by LLVM without ever really understanding what the information in the compile time information actually _means_. That interpretation is left to the compiler writer. This just gives the compiler writer some assurance that the content of the compile time information at least makes some structural sense. Furthermore, this information, even though it may represent a very complex data structure, is treated as a...

Dear all, I'm struggling with weighted least squares, where something that I had assumed to be true appears not to be the case. Take the following data set as an example: df <- data.frame(x = runif(100, 0, 100)) df$y <- df$x + 1 + rnorm(100, sd=15) I had expected that: summary(lm(y ~ x, data=df, weights=rep(2, 100))) summary(lm(y ~ x, data=rbind(df,df))) would be equivalent, but

Hi all, First post for me here, but I have been reading on the forum for almost two years now. Thanks to everyone who contributed btw! I have a dataset of 4000 observations of count of a mammal and I am trying to predict abundance from a inflated-zero model as there is quite a bit of zeros in the response variable. I have tried multiple options, but I might do something wrong as every

> The point here is that XPL needs to keep track of what a given variable > represents at the source level. If the compiler sees a map that is > initially small it might represent it in LLVM assembly as a vector of > pairs. Later on, it gets optimized into being a hash table. In order to > do that and keep track of things, I need to know that the vector of > pairs is

> > The Triple object will remain unchanged. > > The Tuple will be the API to handle getting/setting parameters > depending on the Triple, compiler flags, attributes, etc. > > This part doesn't seem obvious from the direction the patches are going. > There will be no string representation of all options, as that would > be impossible, or at least, highly