www.cmm.bristol.ac.uk/forum

We have not had any reports of MLwiN working under Wine before, which is why we haven't created versions of the plugin for Linux or Mac. I would be very interested in hearing how well it runs in this environment.

If runmlwin is unable to find a particular plugin it should be able to fall back to ...

One possible reason for this behaviour is that the two models are converging from different directions and are considered to have converged before reaching exactly the same point.

The default tolerance in MLwiN (and runmlwin) is 10e-2, which corresponds to a 1% change in the value of the estimate ...

The negative binomial distribution is currently not implemented in MLwiN when using MCMC estimation. We will try to provide a better error message to indicate this in a later release of runmlwin.

Looking at your data it appears that none of your identifier variables contain a value of zero, so that bug isn't the cause of the difference that you are seeing.

A more likely cause of this issue is the change in starting values for the residuals in cross-classified models that was made in version ...

If you are experiencing this bug then adding one to the relevant classification columns should have fixed it. One other possibility is that because cross-classified models can't get starting residuals from a previously specified model that it is taking longer for the estimates to get into the right ...

There are some examples in section 4.2 of the User Guide (http://www.bristol.ac.uk/cmm/software/m ... man-09.pdf) and section 2 of the Manual Supplement (http://www.bristol.ac.uk/cmm/software/m ... 0-supp.pdf) that you might find useful.

As you have 158 origins I think that the command should be:

SETX 'CONSTANT' 3 'ORIGIN' C101-C 2 58 C50

If this still doesn't work could you confirm that the example on page 276 of the MLwiN user guide works for you. If it does then could you email me an example worksheet that demonstrates the ...

We have added a warning message for when the likelihood is missing. This will appear in the next release of runmlwin. If you could still send us an example of this we will be able to test that this works.

Columns in an MLwiN worksheet do not all have to be of the same length, only those used in the model. Because of this MLwiN does not know how many cases you are using until you have set up your model to a sufficient degree to be able to determine this. If you set up your model you should see the ...

I would just add that you may find the mcmcsum command that accompanies runmlwin useful for performing diagnostics on your MCMC runs.