You could consider JAGS. It's an MCMC package which uses (almost exactly)
the same model description language as BUGS. JAGS has both 32 bit and 64
bit versions, and as far as I know, it has no RAM limitations. It's easily
run from R, so if you install 64-bit R and 64-bit JAGS, then you should be
set.
Tim Handley
Fire Effects Monitor
Santa Monica Mountains NRA
805-370-2300 x2412
BUGS automatic
digest system
<LISTSERV@JISCMAI To
L.AC.UK> [log in to unmask]
Sent by: "(The cc
BUGS software
mailing list)" Subject
<[log in to unmask] BUGS Digest - 15 Jun 2011 to 16 Jun
.UK> 2011 (#2011-64)
06/16/2011 04:01
PM
Please respond to
"(The BUGS
software mailing
list)"
<[log in to unmask]
.UK>
On 16/06/2011 00:01, BUGS automatic digest system wrote:
> Date: Wed, 15 Jun 2011 13:26:16 +0000
> From: "Woolfolk, William (wdw7m)"<[log in to unmask]>
> Subject: RAM Limits in BUGS
>
> > From the responses I've seen, BUGS has a RAM limit of 2 GB. More RAM
will not speed it up. Faster processor
will.****************************************
Both WinBUGS and OpenBUGS are 32 bit applications and therefore the
maximum that they could use in principle is 4Gb. The main reason people
run out of memory is that they try to monitor too many variables.
Suppose that you monitor one variable. At each iteration 8 bytes (for a
real value) will be stored. Thus 106 iterations will store 8Mb.
Suppose that you now monitor a complete array which is 1000 by 1000; at
each iteration, 8Mb storage will be required, so you are rapidly going
to run out of memory.
Large models are going to require a lot of memory for nodes and
updaters, etc, but unfortunately it's not possible to estimate a priori
how much memory will be required to run the model. But if the job
appears to be increasing in size as time goes on, the reason is the
number of variables being monitored.
Steve,
MRC-BSU.
-------------------------------------------------------------------
This list is for discussion of modelling issues and the BUGS software.
For help with crashes and error messages, first mail [log in to unmask]
To mail the BUGS list, mail to [log in to unmask]
Before mailing, please check the archive at
www.jiscmail.ac.uk/lists/bugs.html
Please do not mail attachments to the list.
To leave the BUGS list, send LEAVE BUGS to [log in to unmask]
If this fails, mail [log in to unmask], NOT the whole list
------------------------------
End of BUGS Digest - 15 Jun 2011 to 16 Jun 2011 (#2011-64)
**********************************************************
-------------------------------------------------------------------
This list is for discussion of modelling issues and the BUGS software.
For help with crashes and error messages, first mail [log in to unmask]
To mail the BUGS list, mail to [log in to unmask]
Before mailing, please check the archive at www.jiscmail.ac.uk/lists/bugs.html
Please do not mail attachments to the list.
To leave the BUGS list, send LEAVE BUGS to [log in to unmask]
If this fails, mail [log in to unmask], NOT the whole list
|