This weekend I noticed that my R2WinBUGS connection was no longer working on my Windows computer at work AND my Ubuntu linux computer at home. As soon as WinBUGS opens, the message reads Index Out Of Range. I have un-installed and re-installed R on both computers and the problem remains the same. At first I thought it was the new version of R, but I was able to overcome the problem (on Windows only) with the use of program="openbugs" in R2WinBUGS. But that doesn't work on Linux. PS The smallest WinBUGS program I have, essentially a t-test, still works. But anything larger than that gets the error. Help. Thanks. -- View this message in context: http://old.nabble.com/R2WinBUGS-not-working--tp26160111p26160111.html Sent from the R help mailing list archive at Nabble.com.
Paul Heinrich Dietrich wrote:> This weekend I noticed that my R2WinBUGS connection was no longer working on > my Windows computer at work AND my Ubuntu linux computer at home. As soon > as WinBUGS opens, the message reads Index Out Of Range. I have un-installedYes, thanks, problem known for R-2.10.0 and under investigation.> and re-installed R on both computers and the problem remains the same. At > first I thought it was the new version of R, but I was able to overcome the > problem (on Windows only) with the use of > > program="openbugs" > > in R2WinBUGS. But that doesn't work on Linux.That works because it just uses a wrapper for BRugs and the real is done be BRugs. Best, Uwe Ligges> PS > The smallest WinBUGS program I have, essentially a t-test, still works. But > anything larger than that gets the error. > > Help. Thanks.
I have a fix in R2WinBUGS_2.1-15 which is on its way to CRAN and will appear there within 2 days, probably. Best wishes, Uwe Ligges Paul Heinrich Dietrich wrote:> This weekend I noticed that my R2WinBUGS connection was no longer working on > my Windows computer at work AND my Ubuntu linux computer at home. As soon > as WinBUGS opens, the message reads Index Out Of Range. I have un-installed > and re-installed R on both computers and the problem remains the same. At > first I thought it was the new version of R, but I was able to overcome the > problem (on Windows only) with the use of > > program="openbugs" > > in R2WinBUGS. But that doesn't work on Linux. > > PS > The smallest WinBUGS program I have, essentially a t-test, still works. But > anything larger than that gets the error. > > Help. Thanks.