runmlwin with starting values, with MLwiN 2.36

Welcome to the forum for runmlwin users. Feel free to post your question about runmlwin here. The Centre for Multilevel Modelling take no responsibility for the accuracy of these posts, we are unable to monitor them closely. Do go ahead and post your question and thank you in advance if you find the time to post any answers!

Go to runmlwin: Running MLwiN from within Stata >> http://www.bristol.ac.uk/cmm/software/runmlwin/
Post Reply
andrewjdbell
Posts: 16
Joined: Mon Jun 03, 2013 3:19 pm

runmlwin with starting values, with MLwiN 2.36

Post by andrewjdbell » Wed Apr 13, 2016 1:58 pm

Hi, I am running an MCMC model from runmlwin where I specify the parameter starting values in the stata code. However, with the new version of MLwiN, 2.36, I get a load of warnings when MLwiN opens, such as: "Column c1098 is protected, overwrite protected column ?" with a yes and no option.
My questions, then, are:
1. Am I right to click yes to to these? (presumably to allow MLwiN to accept the starting values specified in Stata)
2. Is there a way to override these warnings automatically? E.g. if I were running simulations (with potentially tens of thousands of model runs) I wouldn't want to have to keep clicking yes for every model....
Thanks!
Andy

ChrisCharlton
Posts: 1111
Joined: Mon Oct 19, 2009 10:34 am

Re: runmlwin with starting values, with MLwiN 2.36

Post by ChrisCharlton » Wed Apr 13, 2016 3:14 pm

1) Yes, you are right to click yes to these. MLwiN 2.36 now marks columns used by the system as protected to prevent accidental overwriting.

2) We have a workaround to these messages in the -runmlwin- development version, which we hope to release to ssc soon. In the mean time you can work around this by using the mlnscript version of MLwiN instead of mlwin.exe as this will not wait for an answer to these before continuing. For reference, you can turn off these warnings in your own macros by issuing the MARK 0 command.

andrewjdbell
Posts: 16
Joined: Mon Jun 03, 2013 3:19 pm

Re: runmlwin with starting values, with MLwiN 2.36

Post by andrewjdbell » Mon Apr 25, 2016 9:34 am

Great, thanks Chris :)
A

Post Reply