The script command "coda" is not necessary, unless you want to read in in
coda-format output. Necessary are the other commands: "history & save
(odc)". "save (txt)" lets you read the on-screen output of winbugs later as
a text-file.
Another way is also to take the saved last values of the chains a
I found a very simple way:
you start winbugs from R and state: debug=TRUE, start maybe with few
iterations, like 10.
If everything goes fine, open a new & empty "odc" document in winbugs. Now
scan the log file and find something like this:
update(10)
coda(*,C:/DOKUME~1/Frederic/LOKALE~1/Temp/Rtmp
On 14.07.2010 18:31, Ben Bolker wrote:
Frédéric Holzwarth uni-leipzig.de> writes:
Hello there,
is there a way to update a model, which was called by "bugs()"? For
instance starting with few iterations and then updating more and more,
as is possible inside the WinBUGS-window. If set "debug
Frédéric Holzwarth uni-leipzig.de> writes:
>
> Hello there,
>
> is there a way to update a model, which was called by "bugs()"? For
> instance starting with few iterations and then updating more and more,
> as is possible inside the WinBUGS-window. If set "debug=TRUE", then the
> window rema
4 matches
Mail list logo
