What if WinBUGS crashes with a Trap full of gibberish?
The usual reason is that the sampling algorithm has failed due to the prior being incomparable with the data, or because therer is too little information concerning a parameter given a “vague” prior. Try to check what was happening just before the crash. Ensure initial values are appropriate, or use stronger priors. It is sometimes possible to carry on sampling by closing the Trap window and clicking on update a couple of times. However, if you repeatedly crash, it may be best to quit and start WinBUGS again.
Related Questions
- My system crashes with either ``Fatal trap 12: page fault in kernel mode\, or ``panic:\, and spits out a bunch of information. What should I do?
- My system crashes with either `` Fatal trap 12: page fault in kernel mode \, or `` panic: \, and spits out a bunch of information. What should I do?
- What if WinBUGS crashes with a Trap full of gibberish?
