Displaying 3 results from an estimated 3 matches for "initx".
Did you mean:
init
2003 Jul 04
0
degrees of freedom in nlme() (PR#2384)
...7.1 running on Red Hat Linux 7.2
###########
library(nlme)
nseeds <- 20
DF <- numeric(nseeds)
for(i in 1:nseeds)
{
set.seed(i)
a <- 2
x <- rep(rnorm(3),rep(5,3))
id <- rep(c("a","b","c"),rep(5,3))
y <- a+x+rnorm(15)
data <- data.frame(y=y,id=id)
initx <- matrix(x[c(1,6,11)],dimnames=list(c("a","b","c"),"x"))
tryerror <- try(fit.nlme <-
nlme(y ~ a + x, fixed= a~1, random=x~1|id,
data=data, start=list(fixed=c(a=2),
random=list(id=initx)),method="ML&quo...
2010 Dec 10
2
Could concurrent R sessions mix up variables?
Hi, I'm working in R 2.11.1 x64 on Windows x86_64-pc-mingw32.
I'm experiencing a strange problem in R that I'm not even sure how to
begin to fix.
I've got a huge (forty-pages printed) simulation written in R that I'd
like to run multiple times. When I open up R and run it on its own,
it works fine. At the beginning of the program, there's a variable X
that I set to 1,
2010 Dec 11
0
is there a packge or code to generate markov chains in R
...simulation) done this and forgotten about it? If
all 4 processes are saving to the same place, then reading results back,
you'd see something like you describe.
If all calculations are held in memory, you shouldn't.
A simple approach that might debug this is to create a new variables
initX, set equal to X. Then sprinkle statements
stopifnot(X == initX)
through your simulation code. That should quit when the change happens,
and you can try to figure out why it happened.
Duncan Murdoch
------------------------------
Message: 58
Date: Fri, 10 Dec 2010 10:58:01 -0800 (PST)
From...