Dear Mr. Rosenblum,
Unfortunately, _AMvarnm can not be set in the windows version of Amelia,
or the solution that Gary gives, and that from your note you probably
have already looked to try, would be the short cut around this problem.
I have not been able to replicate your problem, but have been working on
it. Are you setting other globals at the same time? Could you give me a
list of what gloabls in Amelia you are setting?
Regardless of which combinations of variables is causing this problem, the
solution is fairly simple.
If you are curious, this is what is causing your problem:
The problem you have is one that has come up before. Because of the
interface we use for the windows version, it is not possible to produce
error messages during the actual running of Amelia as they occur.
Threfore all the checks that occur during the running of Amelia have to be
moved into the front end and run before any processing in Amelia can
occur. Sometimes sets of globals (both the ones the user can set, the
internal ones used for reordering and scaling the dataset for
computational efficiency) are valid in combination when they are not
individually. Once the computation has begun, all the globals are set, so
it is easier to check they are jointly valid, whereas at the point of the
front end, the code sometimes prematurely challenges the validity of
globals because not all user globals have been set yet, or internal
globals have not yet had a chance to be changed. The routines that check
the validity of globals were written to help the user from making common
mistakes, but sometimes they trip up (as here) and prevent the user from
doing valid things simply because the routines that check don't see the
full picture yet.
I hope to give you a new version of Amelia for windows with the check
routines corrected on Thrusday,
sincerely,
James Honaker
On Wed, 26 Jun 2002, Gary King wrote:
why don't you set _AMvarnm to missing values (a dot). then Amelia will
name the variables for you and this error shouldn't occur.
THe other problem I think is with the operating system.
Gary King
: Gary King, King(a)Harvard.Edu
http://GKing.Harvard.Edu :
: Center for Basic Research Direct (617) 495-2027 :
: in the Social Sciences Assistant (617) 495-9271 :
: 34 Kirkland Street, Rm. 2 HU-MIT DC (617) 495-4734 :
: Harvard U, Cambridge, MA 02138 eFax (928) 832-7022 :
On Tue, 25 Jun 2002 mrosenbl(a)uno.edu wrote:
I am getting the following response when I try to
run Amelia for windows:
_AMvarnm has too many variable names to match each variable
in the dataset. Delete variable names, or set _AMvarnm=.
for default variable names (default = var1 var2 ... ).
I have cut the dataset down to 20 variables, 8 of which are fully observed, and
none of which is missing more than 85 or so out of N=586. It is TCSC data w/ 15
countries, 39 years.
Any suggestions?
I previously ran into a separate problem on a different computer of Amelia
crashing after saying that it was unable to save window size and font size.
there was a message about this on the listserv, but I never did solve that
problem (do not know yet whether it will pop up now that I am back on my own
computer; was using a colleague's before.)
Thanks so much for any insight.
Marc Rosenblum
Assistant Professor of Political Science
University of New
Orleans
-
amelia mailing list served by Harvard-MIT Data Center
List Address: amelia(a)latte.harvard.edu
Subscribe/Unsubscribe:
http://lists.hmdc.harvard.edu/?info=amelia
-
amelia mailing list served by Harvard-MIT Data Center
List Address: amelia(a)latte.harvard.edu
Subscribe/Unsubscribe:
http://lists.hmdc.harvard.edu/?info=amelia