www.cmm.bristol.ac.uk/forum

This message usually indicates that MLwiN has encountered a problem creating the file in the chosen directory, this could happen for example if the location where you chose to save to was read-only or didn't exist. You could check this by choosing a location with the browse button that is definitely ...

The only reshape command that I can find in realcomImputeLoad.ado is:
quietly reshape long v, i(id)
This would match with the error message that you are getting as this refers to a variable starting with v.

I would firstly suggest that you look to see whether there is anything obviously wrong ...

You should be able to calculate this from the variance matrix, e(V). The following is an example of how to do this is:

matrix stderr = vecdiag(e(V))
forvalues i = 1/`=colsof(stderr)' {
matrix stderr[1,`i'] = sqrt(stderr[1,`i'])
}

This should give you a matrix with the same dimensions as e(b ...

From the output that you have provided it looks like it's having a problem in the following section of code:

*save file ready for REALCOM to load
local stoppos = strpos("`using'",".")
if `stoppos'==0 {
local savename `using'.txt
}
else {
local savename `using'
}
file open myFile using `savename ...

Thanks for letting us know about this. You cannot recast __000003 because it is a temporary variable that is only created for the duration that runmlwin is running. We have now added code to ensure that these generated variables are kept to the correct precision for MLwiN in our development version ...

You should be able carry on with the loop by either putting a capture in front of the post command so that it carries on with the loop when it fails, or by only calling post when runmlwin succeeds by putting it in an if !c(rc) statement.

Thanks for reporting this, it appears to be a bug. The contents of the global macro and the command option should be stored in a local macro, and then this used within the command. It appears that in some places, such as discrete models, we are using the global macro directly. I will fix this for ...

MLwiN works out that it is a level 2 variable from the fact that its value is constant within each level 2 identifier. This can be demostrated by modifying the data prior to adding the variable to the model so that this is no longer the case. If you do this the subscript will then be ij instead of j.

Since your initial post we have done some testing and as a result have updated the FAQ on running MLwiN on non-Windows systems ( http://www.bristol.ac.uk/cmm/software/mlwin/features/sysreq.html#unix ).

Once we have a package that is confirmed to work we also intend to provide an FAQ on using ...

You can prevent Stata giving a 'more' prompt with the command:

set more off

For more information see http://www.stata.com/help.cgi?more .

You can turn off the output from runmlwin by either prefixing it with quietly (see http://www.stata.com/help.cgi?quietly ), or you can turn off individual ...