2547 days ago, 563 views
PowerPoint PPT Presentation
WinBUGS (Bayesian derivation Using Gibbs Sampling) is moderately easy to use PC programming for Bayesian investigation utilizing Markov Chain Monte Carlo (MCMC) techniques. WinBUGS actualizes both Gibbs and Metropolis-Hastings calculations. It was created and is bolstered mutually between Medical Research Council (UK) Biostatistics Unit and the Imperial College School of Medicine at St Mary\'s, London. The

Presentation Transcript

Slide 1

More BUGS "You can, for instance, never anticipate what any one man will do, however you can state with accuracy what a normal number will be doing. People fluctuate, however rates stay steady. So says the analyst." Sherlock Holmes The Sign of Four James B. Elsner Department of Geography, Florida State University Portions of this introduction are taken from Implementing MCMC Models in WinBUGS , Jim Peterson, September 6, 2004.

Slide 2

WinBUGS ( B ayesian deduction U sing G ibbs S ampling) is generally easy to use PC programming for Bayesian investigation utilizing Markov Chain Monte Carlo (MCMC) strategies. WinBUGS actualizes both Gibbs and Metropolis-Hastings calculations. It was produced and is upheld mutually between Medical Research Council (UK) Biostatistics Unit and the Imperial College School of Medicine at St Mary's, London. The product is at present free and can be downloaded at the BUGS site . Be that as it may, clients must enlist at the site to acquire a permit to run the product. While at the BUGS site, clients are urged to download CODA- - a suite of Splus/R capacities for merging diagnostics. WinBUGS accompanies broad documentation and various cases, principally from restorative applications. Measurable demonstrating frequently starts by building a graphical portrayal of competitor models. WinBUGS can be utilized to construct graphical models utilizing a specific drawing apparatus DoodleBUGS . The graphical models then can be fit in WinBUGS or on the other hand, WinBUGS will consequently compose the content based WinBUGS dialect code. While graphical models are without a doubt helpful, we think that its simpler to work specifically in the WinBUGS dialect code design. Take note of that WinBUGS permits clients to spare models in WinBUGS ".odc" and different arrangements. It may be a superior thought to spare projects in plain content ".txt" arrange.

Slide 3

Model and information structure in WinBUGS We represent the WinBUGS dialect design utilizing the straightforward case of assessing a mean and fluctuation of 20 perceptions utilizing a diffuse earlier for the mean and difference (accuracy), beneath. # the model { # Prior on typical mean mu ~ dnorm(0,0.00001) # Prior on ordinary exactness tau ~dgamma(0.01, 0.01) # fluctuation = 1/accuracy sigma2 <- 1/tau # probability take note of that tau is accuracy not difference for (i in 1:N) { y[i] ~ dnorm(mu,tau)} } # the information list(N=20, Y=c(98,160,136,128,130,114,123,134,128,107,123,125,129,132,154,115,126,132,136,130))

Slide 4

Models are outlined utilizing sections "{}" and are going by the model proclamation. Remarks are delimited utilizing "#". Irregular factors (additionally called stochastic hubs) are spoken to by the variable name (Note: WinBUGS is case touchy.) trailed by a twiddle "~", the dissemination name, and a comma-isolated rundown of parameters encased in brackets "( )". For the above illustration, the parameter mu is ordinarily conveyed "dnorm" with a mean of zero and exactness 0.00001, though the parameter tau is circulated as a gamma "dgamma" with shape 0.01 and reverse scale 0.01. Consistent assignments are spoken to by the variable name took after by a left directing bolt "<- " and the legitimate expression. For instance, sigma2 (i.e., the fluctuation) is computed as one isolated by tau . As we should see, a connection work additionally can be determined on the left hand side of a coherent task, for example, a logit interface utilized as a part of the calculated relapse display: logit(p[i]) <- beta0 + beta1 * x[i] Arrays are listed utilizing sections "[ ]" and are in the shape [row, column]. Essential whole number operations, for example, expansion, subtraction and increase are permitted inside the sections, e.g., [(i +1), j]. Other cluster traditions include: i:j incorporates the qualities, i, i + 1, ..., j. x[] incorporates all estimations of vector x. x[,2] incorporates all estimations of the second segment of a two-dimensional cluster x. For the above illustration, Y [ i ] speaks to the i th esteem in the vector Y .

Slide 5

Loops are utilized for an assortment of undertakings including, above all, perusing in information. They are indicated utilizing the for-circle structure "for (j in a:b)" delimited utilizing sections "{}". For the above case, a for-circle is utilized to peruse a column vector (length N ) of information Y for refreshing the mean mu and exactness tau . There are a few worthy information designs for WinBUGS. Here we will talk about most regularly utilized, information records. Information list design for the most part takes after that of Splus and can comprise of scalars, column vectors, and exhibits. Finish information records are portrayed utilizing brackets "( )" and are going by the rundown explanation. The components of the information rundown are isolated by a comma. The configuration of the information list relies on upon the kind of information and different information sorts (scalar, vector, exhibit) can be contained inside a solitary information list. For scalars , the configuration comprises of the variable name, an equivalent sign, and the estimation of the variable. For the above case, the quantity of perceptions N is a scalar with an estimation of 20. Push vectors are distinguished utilizing the variable name, an equivalent sign, and the vector values isolated by commas and contained inside "c( comma isolated values here )." The organization for information clusters is more confused and comprises of the variable name, an equivalent sign, and exhibit values isolated by commas and contained with the revelation of the exhibit arrange. For instance, underneath is a case of information in a 4 push, 3 segment exhibit X . The announcement " structure(.data = c( " pronounces that the accompanying information will be in a cluster design and the last proclamation ".Dim = c(4, 3)) " proclaims a 4 push by 3 segment exhibit. X = structure(.Data = c(1, 199, 61, 3, 199, 29, 9, 180, 19, 13, 200, 44), .Dim = c(4, 3)) Referencing vector and exhibit information inside the WinBUGS demonstrate takes after an indistinguishable configuration from the information list. For instance, the fourth component in the vector y above is 128 and is distinguished as Y [4]. Additionally, the estimation of the variable in the second line, third section of the cluster X is 29 and is recognized as X [2,3].

Slide 6

Commonly utilized WinBUGS disseminations r ~ dbin( p , n ) Binomial with n trials and likelihood of achievement p r ~ dpois( lambda ) Poisson with mean lambda p ~ dbeta( a , b ) Beta with parameters a , b x ~ dgamma( a , b ) Gamma with shape an and reverse scale b x ~ dnorm( mu , tau ) Normal with mean mu and exactness (1/difference) tau Commonly utilized WinBUGS capacities + expansion, - subtraction, * increase,/division abs( x ) outright estimation of x, exp( x ) example, log( x ) regular logarithm, ln( x ) logit( p ) logit interface, ln( p/(1 - p )) max( x 1, x 2) returns x 1 if x 1 > x 2; x 2 generally mean( v ) mean of segments in vector v, min( x 1, x 2) returns x 1 if x 1 < x 2; x 2 generally sqrt( x ) square foundation of x, round( x ) round x to closest whole number, sd( v ) standard deviation of segments of vector v, aggregate( v ) entirety of segments in vector v trunc( x ) returns most prominent whole number not exactly or equivalent to x.

Slide 7

Compiling and fitting a model in WinBUGS Once the model is composed (or doodled then changed over) and information are designed, the model must be arranged. Models are gathered in WinBUGS utilizing the accompanying 5 stages: Step 1: Select "Model" and "Detail" from the WinBUGS menu. The Specification Tool window ought to show up. Step 2: Highlight the model proclamation toward the start of the model (e.g., by double tapping on the announcement) and tap on "check demonstrate" in the Specification Tool window. On the off chance that there are any issues with the model linguistic structure, a message will be shown at the base of model window. Step 3: Highlight the rundown proclamation toward the start of information rundown and tap on "load information." Step 4: Click on "arrange." If there are any issues with the model, a message will be shown at the base of model window. Frequently it is extremely helpful to run various MCMC chains all the while utilizing distinctive introductory qualities for the parameters. To determine different chains, enter the quantity of chains in the area showed in the Specification Tool window before clicking "assemble." Step 5: Load beginning qualities (a) by tapping on the "gen inits," which haphazardly creates starting qualities or (b) by entering particular qualities utilizing information records and by highlighting the proper rundown articulations. Now and again WinBUGS will choose an awful starting quality when utilizing the "gen inits" alternative. To dodge these issues, we suggest picking (a few) conceivable starting qualities.

Slide 8

Model yield and checking in WinBUGS Parameter appraisals might be accommodated the parameters that are expressly distinguished before model-fitting. Once a model has been aggregated, we then need to distinguish the parameters of intrigue and indicate different considers, for example, smolder and diminishing. This can be proficient by choosing "Deduction" and "Tests… " from the WinBUGS menu. The Sample Monitoring Tool will then show up. Sort the name of the parameter in the "hub" window (recall: case touchy), pick the blaze in by entering the incentive in the "ask" window, enter the coveted diminishing in the "thin," select the measurements fancied (e.g., mean, middle, and so on.), and tap on "set". Rehash the procedure for extra parameters. To screen the advance of each chain, enter a reference mark "*" in the hub window and tap on "follow." To start display fitting, select "Model" and "Refresh" from the WinBUGS menu and the Update Tool will show up. Enter the quantity of MCMC emphasess in the "refreshes" window and diminishing (if craved) and tap on "refresh." The follow will uncover the advance of each MCMC chain. After the emphasess are finished, tap on "thickness" to look at the back dissemination of the parameter assessments and "details" to inspect the parameter measurements.

Slide 9

Example #1: Inference is re