Re: st: for Red Owl: assertion is false error: mvencode

[Nick Cox <njcoxstata@gmail.com>]

To get good answers from people willing to advise, please specify what
you typed on the command line as well as the error messages you
receive.

Nick
njcoxstata@gmail.com


On 31 July 2013 10:09, O'Keeffe, Linda <L.OKeeffe@ucc.ie> wrote:
> Thanks very much Red Owl! That worked!
>
> One more question for you- its now running but I am getting the following errors:
>
>  matrix r (gammaSTD) not found &
>
>  matrix r (rhoSTD) not found with the following message
>
> error . . . . . . . . . . . . . . . . . . . . . . . .  Return code 111
>         __________ not found;
>         no variables defined;
>         The variable does not exist.  You may have mistyped the
>         variable's name.
>         variables out of order;
>         You specified a varlist containing varname1-varname2, yet
>         varname1 occurs after varname2.  Reverse the order of the
>         variables if you did not make some other typographical error.
>         Remember, varname1-varname2 is taken by Stata to mean varname1,
>         varname2, and all the variables in dataset order in between.
>         Type describe to see the order of the variables in your dataset.
>         __________ not found in using data;
>         You specified a varlist with merge, but the variables on which
>         you wish to merge are not found in the using dataset, so the
>         merge is not possible.
>         __________ ambiguous abbreviation;
>         You typed an ambiguous abbreviation for a variable in your data.
>         The abbreviation could refer to more than one variable.  Use a
>         nonambiguous abbreviation, or if you intend all the variables
>         implied by the ambiguous abbreviation, append a `*' to the end
>         of the abbreviation.
>
> Many Thanks for your help
> Linda
> ________________________________________
> From: owner-statalist@hsphsun2.harvard.edu [owner-statalist@hsphsun2.harvard.edu] on behalf of Red Owl [rh.redowl@liu.edu]
> Sent: 30 July 2013 18:59
> To: statalist@hsphsun2.harvard.edu
> Subject: st: RE: assertion is false error: mvencode
>
> Linda (and other who may be interested),
>
> I believe this error occurs when you try to run the LCA Stata Plugin from The Methodology Center at Penn State (http://methodology.psu.edu/downloads/lcastata) on binary variables that are coded as 0/1.  The data must be positive integers, so you might try to add 1 to any binary variables coded as 0/1 and then attempt to rerun your analysis.
>
> Also, if you are using Stata/IC (not recommended by the plugin authors but possible with some data and problems), you need to include the option maxiter(800) in the LCA code.  That is necessary due to the maximum matrix size limitations of Stata/IC.  If you are using a higher version of Stata, you should set maxiter(5000) or higher.
>
> Red Owl
>
>
>>> O'Keeffe, Linda" <L.OKeeffe@ucc.ie<mailto:L.OKeeffe%40ucc.ie>>
>>>
>>> I am using Penn State University doLCA command. I keep getting an error after some of the code has run saying
>>>
>>> "389 contradictions in 708 observations"
>>>
>>> assertion if false
>>>
>>> r (9)
>>>
>>> r (9) error code says "   error . . . . . . . . . . . . . . . . . . . . . . . . .  Return code 9
>>>
>>>         assertion is false;
>>>
>>>         no action taken;
>>>
>>>         Return code and message from assert when the assertion is false;
>>>
>>>         see [D] assert.
>>>
>>>         Or, you were using mvencode and requested Stata change `.' to #
>>>
>>>         in the specified varlist, but # already existed in the varlist,
>>>
>>>         so Stata refused; see [D] mvencode.
>>>
>>> (end of search)
>>>
>>> I assume this is a problem with my data but I don't know what. Any assistance would be most greatly appreciated!

*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/faqs/resources/statalist-faq/
*   http://www.ats.ucla.edu/stat/stata/