Displaying 5 results from an estimated 5 matches for "_variable_".
2005 Nov 27
1
fixed, random effects with variable weights
...ne,
I have tried to solve a simple problem for days but I can't figure out
how to run it properly. If someone could give me a hint, this would be
really great.
Basically, I want to run a standard economist's fixed, and random
effects regression (corresponds to xtreg in STATA) but with _variable_
weights (they correspond to changing industry shares in the market).
Here is what I do:
regsc<-lme(dsc~dcomp+dperc,random=~1|ind7090)
update(regsc,weights=varFixed(~wt))
1. however, my results are different from what I obtain in Stata using
areg (the weighted fixed effects times series regr...
2020 Feb 25
2
[RFC] DebugInfo: A different way of specifying variable locations post-isel
...r the current and new-style DBG_VALUEs could coexist in LiveDebugValues? Could that be done by e.g. introducing a new debug instr MI (DBG_INSTR_REF)?
I believe it should be relatively straightforwards: we would have an
additional kind of location-record (i.e. VarLoc) that, instead of
identifying a _variable_, identified the instruction/operand that
computed a value. Handling a DBG_INSTR_REF as you suggest would mean
looking up such a VarLoc by instruction/operand to find its register,
then creating a register location VarLoc for the variable as we do
today. Propagating the location of an instruction/op...
2019 Dec 26
4
Settable minimum RSA key sizes on the client end for legacy devices.
Recently I tried to turn on SSH on my 12 year old APC-UPS.? I soon
discovered that I couldn't connect to it because my newer version of
openssh doesn't support RSA key sizes below 1024 bits.
I'd rather not dredge up a big fight, but I _would_ like to express a
desire for some form of overriding the minimum key size.? Basically I've
had to turn on telnet access again, lowering
2012 Mar 23
11
Plugins and Hiera
Dear all,
This is a continuation of another thread, but I think the question diverged
enough to create a new one.
I have a hiera hierarchy like this:
:hierarchy:
- %{fqdn}
- %{secundary_group}
- %{primary_group}
- %{productname}
- all
And I need to define the secondary/primary groups as facts, on the nodes. Gary
has suggested me to use plugins, that they will provide the facts before
2020 Feb 24
5
[RFC] DebugInfo: A different way of specifying variable locations post-isel
Hi debuginfo cabal,
tl;dr: I'd like to know what people think about an alternative to
DBG_VALUE instructions describing variable locations in registers,
virtual or real. Before instruction selection in LLVM-IR we identify
the _values_ of variables [0] by the instruction that computes the
value; I believe we should be able to do the same post-isel, and it
would avoid having to analyse register