stata14.key

是一个经济学管理应用软件 很难找的 但是经济学学生又必须用到

	Your ^test^ command refers to a term that was not contained
	in your ^anova^ model.

.e [P] error
.c error
.t Return code 148
.k rc 148 r(148)
.x
	^too few categories^;
	You attempted to estimate a model such as ^mlogit^, ^ologit^, or
	^oprobit^ when the number of outcomes is smaller than 3.  Check
	that the dependent variable is the variable you intend.  If
	it takes on exactly two values, use ^logit^ or ^probit^.

.e [P] error
.c error
.t Return code 149
.k rc 149 r(149)
.x
	^too many categories^;
	You attempted to estimate a model such as ^mlogit^, ^ologit^, or
	^oprobit^ with a dependent variable that takes on more than 50
	outcomes (Intercooled Stata) or 20 outcomes (Small Stata).

.e [P] error
.c error
.t Return code 151
.k rc 151 r(151)
.x
	^non r-class program may not set r()^;
	Perhaps you specified ^return local^ in your program, but
	forgot to declare the program ^rclass^ in the ^program define^
	statement.

.e [P] error
.c error
.t Return code 152
.k rc 152 r(152)
.x
	^non e-class program may not set e()^;
	Perhaps you specified ^estimates local^ in your program, but
	forgot to declare the program ^eclass^ in the ^program define^
	statement.

.e [P] error
.c error
.t Return code 153
.k rc 153 r(153)
.x
	^non s-class program may not set s()^;
	Perhaps you specified ^sreturn local^ in your program, but
	forgot to declare the program ^sclass^ in the ^program define^
	statement.

.e [P] error
.c error
.t Return code 161
.k rc 161 r(161)
.x
	^ado-file has commands outside of program define ... end^;
	All commands in ado-files must be part of Stata programs.
	That is to say, all commands must be between a ^program define^
	that begins a program definition, and an ^end^ that concludes
	a program definition.  The command you typed automatically
	loaded an ado-file that violates this rule.

.e [P] error
.c error
.t Return code 162
.k rc 162 r(162)
.x
	^ado-file does not define command^;
	The first program in any ado-file must be named the same as
	the ado-file name.  For example, ^xyz.ado^ must begin with
	^program define xyz^.  The command you typed has loaded an
	ado-file that violates this rule.

.e [P] error
.c error
.t Return code 170
.k rc 170 r(170)
.x
	^unable to chdir^;
	(Unix and Macintosh.)  ^cd^ was unable to change to the directory
	you typed because either it does not exist, it is protected, or
	it is not a directory.

.e [P] error
.c error
.t Return code 180
.k rc 180 r(180)
.x
	^invalid attempt to modify label^;
	You are attempting to modify the contents of an existing value
	label using the ^label define^ command.  If you mean to completely
	replace the existing label, first ^label drop^ it and then ^label
	define^ it.  If you wish to modify the existing label, be sure to
	specify either the ^add^ or the ^modify^ option on the ^label define^
	command.  ^add^ lets you add new entries but not change existing
	ones, and ^modify^ lets you do both.  You will get this error if
	you specify ^add^ and then attempt to modify an existing entry.
	In that case, edit the command and substitute ^modify^ for the ^add^
	option.

.e [P] error
.c error
.t Return code 181
.k rc 181 r(181)
.x
	^may not label strings^;
	You attempted to assign a value label to a string variable,
	which makes no sense.

.e [P] error
.c error
.t Return code 182
.k rc 182 r(182)
.x
	^__________ not labeled^;
	The indicated variable has no value label, yet your request
	requires a labeled variable.  You may, for instance, be
	attempting to ^decode^ a numeric variable.

.e [P] error
.c error
.t Return code 190
.k rc 190 r(190)
.x
	^request may not be combined with by^;
	Certain commands may not be combined with ^by^, and you constructed
	such a combination.  See the syntax diagram for the command.
	^in may not be combined with by^;
	^in^ may never be combined with ^by^.  Use ^if^ instead;
	see ^[U] 11.5 by varlist: construct^.

.e [P] error
.c error
.t Return code 191
.k rc 191 r(191)
.x
	^request may not be combined with by() option^;
	Certain commands that produce graphs may not be combined with ^by()^,
	and you constructed such a combination.  See the syntax diagram for
	the command.
	see ^[G] by_option^.

.e [P] error
.c error
.t Return code 196
.k rc 196 r(196)
.x
	^nl___________ refused query, rc= ___________^;
	^error # _________ occurred in program nl_________^;
	Your ^nl^func program did not work properly with the ^nl^ command.

.e [P] error
.c error
.t Return code 197
.k rc 197 r(197)
.x
	^invalid syntax^;
	This error is produced by ^syntax^ and other parsing commands when
	there is a syntax error in the use of the command itself rather
	than in what is being parsed.

.e [P] error
.c error
.t Return code 198
.k rc 198 r(198)
.x
	^invalid syntax^;
	^__________ invalid^;
	^range invalid^;
	^__________ invalid obs no^;
	^invalid filename^;
	^__________ invalid varname^;
	^__________ invalid name^;
	^multiple by's not allowed^;
	^__________ found where number expected^;
	^on or off required^;
	All items in this list indicate invalid syntax.  These errors are
	often, but not always, due to typographical errors.  Stata attempts
	to provide you with as much information as it can.  Review the
	syntax diagram for the designated command.
	In giving the message "invalid syntax", Stata is not very helpful.
	Errors in specifying expressions often result in this message.


.e [P] error
.c error
.t Return code 199
.k rc 199 r(199)
.x
	^unrecognized command^;
	Stata failed to recognize the command, program, or ado-file name,
	probably because of a typographical or abbreviation error.

.e [P] error
.c error
.t Return code 301
.k rc 301 r(301)
.x
	^last estimates not found^;
	You typed an estimation command such as ^regress^ without arguments
	or attempted to perform a ^test^ or typed ^predict^, but there were no
	previous estimation results.

.e [P] error
.c error
.t Return code 302
.k rc 302 r(302)
.x
	^last test not found^;
	You have requested the redisplay of a previous ^test^, yet
	you have not run a ^test^ previously.

.e [P] error
.c error
.t Return code 303
.k rc 303 r(303)
.x
	^equation not found^;
	You referred to a coefficient or stored result corresponding to
	an equation or outcome that cannot be found.  For instance, you
	estimated a ^mlogit^ model and the outcome variable took on the
	values 1, 3, and 4.  You referred to ^[2]_b[var]^ when perhaps you
	meant ^[#2]_b[var]^ or ^[3]_b[var]^.

.e [P] error
.c error
.t Return code 304
.k rc 304 r(304)
.x
	^ml model not found^;
	You have used ^mleval^, ^mlsum^, or ^mlmatsum^ without having
	first used the other ^ml^ commands to define the model.

.e [P] error
.c error
.t Return code 305
.k rc 305 r(305)
.x
	^ml model not found^;
	You have used ^mleval^, ^mlsum^, or ^mlmatsum^ without having
	first used the other ^ml^ commands to define the model.

.e [P] error
.c error
.t Return code 399
.k rc 399 r(399)
.x
	^may not drop constant^;
	You issued a ^logistic^ or ^logit^ command and the constant was
	dropped.  Your model may be underidentified; try removing one
	or more of the independent variables.

.e [P] error
.c error
.t Return code 401
.k rc 401 r(401)
.x
	^may not use noninteger frequency weights^;
	You specified an ^fweight^ frequency weight with noninteger
	weights, telling Stata your weights are to be treated as
	replication counts.  Stata encountered a weight that was
	not an integer, so your request	made no sense.  You probably
	meant to specify ^aweight^ analytic weights; see ^[U] 11.1.6 weight^.

.e [P] error
.c error
.t Return code 402
.k rc 402 r(402)
.x
	^negative weights encountered^;
	^negative weights not allowed^;
	You specified a variable that contains negative values
	as the weighting variable, so your request made no sense.
	Perhaps, you meant to specify another variable.

.e [P] error
.c error
.t Return code 403
.k rc 403 r(403)
.x
	^may not specify norobust with pweights^;
	You specified one of Stata's estimation commands with
	both the ^norobust^ and the ^pweights^ options.  You cannot
	do this since ^robust^ is a request that ^pweights^ be used.
	See ^[U] 20.14 Obtaining robust variance estimates^.

.e [P] error
.c error
.t Return code 404
.k rc 404 r(404)
.x
	^not possible with pweighted data^;
	You requested a statistic which Stata cannot calculate
	with ^pweight^ed data either because of a shortcoming in
	Stata or because the statistics of the problem have not
	been worked out.  For example, perhaps you requested the
	standard error of the survival curve, and you had previously
	specified ^pweight^ when you ^stset^ your data (a case where no
	one has worked out the statistics).

.e [P] error
.c error
.t Return code 406
.k rc 406 r(406)
.x
	^not possible with analytic weights^;
	You specified a command that does not allow analytic weights.
	See the syntax diagram for the command to see which types of
	weights are allowed.

.e [P] error
.c error
.t Return code 407
.k rc 407 r(407)
.x
	^weights must be the same for all observations in a group^;
	^weights not constant for same observation across repeated variables^;
	For some commands, weights must be the same for all observations
	in a group for statistical or computational reasons.  For the
	^anova^ command with the ^repeated()^ option, weights must be constant
	for an observation across the repeated variables.

.e [P] error
.c error
.t Return code 409
.k rc 409 r(409)
.x
	^no variance^;
	You were using ^lnskew0^ or ^bcskew0^, for instance, but the
	exp that you specified has no variance.

.e [P] error
.c error
.t Return code 411
.k rc 411 r(411)
.x
	^nonpositive values encountered^;
	^__________ has negative values^;
	^time variable has negative values^;
	For instance, you have used ^graph^ with the ^xlog^ or ^ylog^ options,
	requesting log scales, and yet some of the data or the labeling
	you specified is negative or zero.
	Or, perhaps you were using ^ltable^ and specified a time variable
	that has negative values.


.e [P] error
.c error
.t Return code 412
.k rc 412 r(412)
.x
	^redundant or inconsistent constraints^;
	For instance, you are estimating a constrained model with
	^mlogit^.  Among the constraints specified is at least one
	that is redundant or inconsistent.  A redundant constraint
	might constrain a coefficient to be zero that some other
	constraint also constrains to be zero.  An inconsistent
	constraint might constrain a coefficient to be 1 that some
	other constraint constrains to be zero.  List the constraints,
	find the offender, and then reissue the ^mlogit^ command omitting it.

.e [P] error
.c error
.t Return code 416
.k rc 416 r(416)
.x
	^missing values encountered^;
	You were using a command which requires that no values
	be missing.

.e [P] error
.c error
.t Return code 420
.k rc 420 r(420)
.x
	^__________ groups found, 2 required^;
	You used a command (such as ^ttest^) and the grouping variable
	you specified does not take on 2 unique values.

.e [P] error
.c error
.t Return code 421
.k rc 421 r(421)
.x
	^could not determine between-subject error term; use bse() option^;
	You specified the ^repeated()^ option to ^anova^, but Stata could
	not automatically determine certain terms that are needed in the
	calculation; see ^[R] anova^.

.e [P] error
.c error
.t Return code 422
.k rc 422 r(422)
.x
	^could not determine between-subject basic unit; use bseunit() option^;
	You specified the ^repeated()^ option to ^anova^, but Stata could
	not automatically determine certain terms that are needed in
	the calculation; see ^[R] anova^.

.e [P] error
.c error
.t Return code 430
.k rc 430 r(430)
.x
	^convergence not achieved^;
	You have estimated a maximum-likelihood model and Stata's
	maximization procedure failed to converge to a solution;
	see ^[R] maximize^.  Check if the model is identified.

.e [P] error
.c error
.t Return code 450
.k rc 450 r(450)
.x
	^__________ is not a 0/1 variable^;
	^number of successes invalid^;
	^p invalid^;
	^__________ takes on __________ values, not 2^;
	You have used a command, such as ^bitest^, that requires the
	variable take on only the values 0, 1, or missing, but the
	variable you specified does not meet that restriction.  (You
	can also get this message from, for example, ^bitesti^, when
	you specify a number of successes greater than the number of
	observations or a probability not between 0 and 1.)

.e [P] error
.c error
.t Return code 451
.k rc 451 r(451)
.x
	^invalid values for time variable^;
	For instance, you specified ^mytime^ as a time variable and
	^mytime^ contains noninteger values.

.e [P] error
.c error
.t Return code 459
.k rc 459 r(459)
.x
	^something that should be true of your data is not^;
	This is the generic form of this message; more likely, you
	will see messages such as "y must be between 0 and 1" or
	"x not positive".  You have attempted to do something that,
	given your data, does not make sense.

.e [P] error
.c error
.t Return code 460
.k rc 460 r(460)
.x
	^only one cluster detected^;
	^only one PSU detected^;
	^stratum with only one PSU detected^;
	^stratum with only one observation detected^;
	You were using the ^cluster ()^ option and you had only one cluster;
	you must have at least two clusters -- preferably much more than two.
	Or, you were using an ^svy^ command, and you had only one PSU in one
	stratum; the ^svydes^ command will determine which stratum and the
	^[SVY] svydes^ entry shows how to deal with the situation.

.e [P] error
.c error
.t Return code 461
.k rc 461 r(461)
.x
	^number of obs must be greater than # for robust variance computation^;
	^number of obs in subpopulation must be greater than #^;