Search found 1344 matches
- Wed Oct 26, 2011 12:09 pm
- Forum: runmlwin user forum
- Topic: Error message: Could not load plugin
- Replies: 12
- Views: 18562
Re: Error message: Could not load plugin
That should be the only other place that plugin is used. Is it possible that you have forgotten to run the discard command after editing the ado file, to make Stata reload it with your changes?
- Wed Oct 26, 2011 11:16 am
- Forum: runmlwin user forum
- Topic: Error message: Could not load plugin
- Replies: 12
- Views: 18562
Re: Error message: Could not load plugin
You can work around this second plugin issue by replacing all references of runmlwin_quietshell with shell . This will however mean that runmlwin can't be run in Stata batch mode. The final plugin that might cause an issue is the MCMC diagnostics plugin. Unfortunately there is currently no workaroun...
- Wed Oct 26, 2011 9:24 am
- Forum: runmlwin user forum
- Topic: Error message: Could not load plugin
- Replies: 12
- Views: 18562
Re: Error message: Could not load plugin
I am still not sure what is causing this as we have run this on a similar setup without issues. It possible that it can't find the correct C runtime library. We should be using the one that comes with Stata, however if not you could install this from http://www.microsoft.com/download/en/details.aspx...
- Tue Oct 25, 2011 4:11 pm
- Forum: runmlwin user forum
- Topic: Error message: Could not load plugin
- Replies: 12
- Views: 18562
Re: Error message: Could not load plugin
This message is a little puzzling. Could you try the following and let us know the results: 1) Make sure that the file has downloaded correctly. To do first run the following Stata command: checksum "c:\ado\plus\r\runmlwin_getversion.plugin" Assuming that you're running on a 32-bit system,...
- Sun Oct 23, 2011 9:43 pm
- Forum: runmlwin user forum
- Topic: Error message regarding level 1 ID variable - Obsno is held
- Replies: 8
- Views: 11282
Re: Error message regarding level 1 ID variable - Obsno is h
This appears to be a bug, and will be fixed in the next released version of runmlwin. In the mean time you can work around it by running the following in Stata prior to calling runmlwin: recast float obsno Alternatively if you are comfortable editing the runmlwin.ado file you can change the lines: i...
- Mon Oct 17, 2011 3:32 pm
- Forum: runmlwin user forum
- Topic: How do I stop MLwiN setting residuals to missing?
- Replies: 4
- Views: 6295
Re: How do I stop MLwiN setting residuals to missing?
runmlwin does not currently allow this to be set, however we could look into adding it as an option in a future release.
- Mon Oct 10, 2011 8:31 pm
- Forum: runmlwin user forum
- Topic: 3-level multinomial error:'illegal op: v_block:: mult_add()'
- Replies: 17
- Views: 20913
Re: 3-level multinomial error:'illegal op: v_block:: mult_ad
At what point did you get the message 'Obey command is not available when batch excecution is PAUsed'? I would only expect this message to occur if you tried to run another macro while MLwiN was waiting for you to choose the "resume macro" or "abort macro" buttons. If you are doi...
- Thu Oct 06, 2011 10:47 am
- Forum: Realcom user forum
- Topic: Problem in getting started
- Replies: 5
- Views: 10089
Re: Problem in getting started
I'm not sure whether it's related, but there are a couple of errors in your input. In the first attempt you appear to have an extra quote at the beginning of the ISAV command. In the second version you appear to be defining school twice in the auxiliary variables (this may be due to selecting it as ...
- Tue Oct 04, 2011 8:09 pm
- Forum: MLwiN user forum
- Topic: Print window image
- Replies: 4
- Views: 9209
Re: Print window image
This was removed a few versions ago for technical reasons. You can find more details here: http://www.bristol.ac.uk/cmm/software/s ... html#print
- Mon Oct 03, 2011 3:52 pm
- Forum: runmlwin user forum
- Topic: Error message: invalid variable names
- Replies: 3
- Views: 8153
Re: Error message: invalid variable names
I have just checked the Stata manual and it turns out that a few of the reserved variable names that MLwiN checks for are wrong (for example it should check for _pi instead of pi). This will be fixed in the next release of MLwiN.