www.cmm.bristol.ac.uk/forum

The first thing to check would be that your command is conceptually on one line. You can split it across several lines to aid readability, however you would need to put /// at the end of each line to indicate a line continuation.

You can only specify each level once in runmlwin, so you can't have ...

These two approaches should also work with runmlwin, so it is probably worth trying both ways and then comparing with the results that you had previously from gsem.

Assuming that the data sample you provided is representative of the rest of the data I think that your problem may be that your data is not sorted by the model hierarchy. Rather than using unique values of ID codes to determine the units MLwiN instead calculates this on when the ID code changes as ...

runmlwin should (more or less) work like any other Stata command, so you should be able to use the standard Stata facilities to create the required dummies. I think that the example we provide only does it manually to make the process more explicit (and give the generated dummies names of our ...

Could you provide any further information about what your time variable represents? E.g., Is it the occasion on which a measurement was taken, as in the example in chapter 13 of the MLwiN manual ( https://www.bristol.ac.uk/cmm/media/software/mlwin/downloads/manuals/3-13/manual-web.pdf ), or is it a ...

lc1 lc2 and lc3plus are dummy variables that were created from the categorical variable lc . You can see the code that was used to create them at the beginning of the replication example for chapter 10 of the MLwiN user's guide ( https://www.bristol.ac.uk/cmm/media/runmlwin/10_Multinomial_Logistic ...

Are you able to provide any information about your data and its structure? For example, does it contain missing values, does it have particularly large/small clusters, does it contain some extreme values, etc? Can you try fitting simpler versions of the model (e.g. with only the intercept) to see if ...

Discrete response models fitted via (R)IGLS in MLwiN are often compared using a Wald test. For details of how to do this test see the MLwiN manual, for example on pages 125, 131 and 138.

I believe that you should be able to manually allow the application to run by following the steps in this article: https://support.apple.com/en-gb/guide/m ... b3a043/mac. For a more detailed description of the cause of this warning see https://support.apple.com/en-gb/102445.

This sounds like an error is occurring within MLwiN, so the best way to find the cause would be to add the option debugmode=TRUE to the list in estoptions .

Looking at the syntax that you provided I think that the problem may be that you need to extend the Model1_MultiMembers list with another NA ...