www.cmm.bristol.ac.uk/forum

Unfortunately the current trial version of MLwiN is based on version 2.16, while runmlwin makes use of functionality added in version 2.22. I will look into updating the trial version to a compatible version in the near future. Having said that, if I am reading what you typed correctly I think that ...

Yes this is possible. You will need to create a file containing a series of MLwiN commands and then pass this an an argument to mlwin /run. In order to create the necessary file you will be need to become familiar with the MLwiN command language. Most of the documentation for the commands can be fou...

Have you checked that your data is sorted correctly (see http://www.cmm.bris.ac.uk/MLwiN/tech-su ... html#order)?

1) This error message usually indicates that not all the variables in your model are the same length. To check this choose: Data Manipulation->Names and check that the "n" column for all variables in your model (including cons) has the same value. 2) You can copy most MLwiN windows, including graphs...

I suspect that you are viewing the equation with general notation. To switch to simple notation click the "notation" button at the bottom of the equation and untick "general". Once you have done this the equation should match what you are expecting.

The macro that is generating this error message is called "ERRCHK" and can be found in the "discrete" folder of the MLwiN application. You might be able to work out what is causing the problem by looking through the commands that this is running. Another possible thing to try is to see if you can re...

The columns used for bootstrap estimation are as follows: C1105 - initial estimates C1106 - bias corrected estimates C1107 - previous set (parameters) C1108 - previous set (-2 loglikelihood) C1109 - current series C1111 - current population values to simulate from For these and other system reserved...

A common cause for the reported number of units to not match what is expected is if the data isn't sorted correctly. See http://www.cmm.bristol.ac.uk/MLwiN/tech ... html#order for further details. You can use Model->Hierarchy viewer to see which units MLwiN has identified.

My guess would be that this is either caused by a corrupted worksheet, or a bug in the software. If it is the former then clearing the model and setting it up again might fix it. If it is the latter then I suggest reporting it at the following address: http://www.cmm.bristol.ac.uk/MLwiN/tech-support...

You should be able to choose the missing value in the "Listwise" screen by clicking in the box to the right of "Listwise delete on value" and pressing the "m" key. Did you try this, and if so what was the error message/problem that you got?