## the jags model first
mod <- jags(data, parameters.to.save, model.file, n.chains, n.iter)model.update <- mod
save(model.update)
#--- update MCMC ---------- for (i in 2:N.STEPS) { model.update <- update(model.update, parameters.to.save, n.iter) save(model.update) }#end of i loop (steps)
--
You received this message because you are subscribed to the Google Groups "nimble-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nimble-users+unsubscribe@googlegroups.com.
To post to this group, send email to nimble...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nimble-users/6039ef23-89af-4e1d-9602-edff07e2a725%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
It seems to me that the Cmcmc will become bigger and bigger when I continue to run more iterations. Sometimes I need a very long burnin for my model to get converge. The machine will run out of space/memory to continue the run since Cmcmc will become too big. Is there a way to get by this?
I need at lease 1 million iterations to get convergent, with about 5k parameters. I'm not sure when my model will converge. So I need to let the mcmc run for 2 or 3 millions and monitor the iterations from time to time. I'm wondering if nimble can discard the past iterations (to free up the space) after I save each portion of iterations and keep on running the mcmc (like what jags did as shown in the code in my 1st post)?
Thanks!
Fengqing
To unsubscribe from this group and stop receiving emails from it, send an email to nimble-users...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to nimble-users+unsubscribe@googlegroups.com.
To post to this group, send email to nimble...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nimble-users/9fb7fd4f-5737-469e-b7c6-f25a823113b0%40googlegroups.com.