I would like to post a general response to the recurring message: 'here is my problem. I am a newbie. Can someone show me how to code this in BUGS?' I realize that I may be a stick in the mud, but we really need to tell people that they need to learn BUGS first, and only then apply it to their problem. Working through the BUGS examples from simple to more complex not only provides experience, but demonstrates modeling options that may be superior to the model you originally intended to use. It should also be repeatedly pointed out that MCMC simulation is dangerous. Multi-modal distributions, poor burn-in, lack of convergence are all issues require considerable experience to identify and avoid. As such, even if you could provide a newbie with code to exactly fit their problem, they still lack the experience to avoid even common pitfalls. (A student once commented that statistical consulting is like giving a loaded handgun to someone who has never seen one and has no idea what it is, and then telling them to be careful). I think that it is useful to inform interested newbies that their problem can (or can't) be addressed in BUGS, but it is probably not a good idea to give them code help until they are already fairly proficient in coding and running models. Finn Krogstad University of Washington College of Forest Resources Seattle WA 98195 ------------------------------------------------------------------- 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