29 Apr
2008
29 Apr
'08
4:02 p.m.
Dear Xiaobo,
For your first question, regarding updating to the latest version of Amelia II,
it looks like you are using R 2.5 (even if you are using the AmeliaView
version of Amelia, your most recently installed version of R on your
machine was version 2.5). Therefore, R is finding the last version of
Amelia created under R 2.5.
If you update R to the current R 2.7.0, and then type in exactly the same
install.packages() command you used, you will get the most recent version of
Amelia.
For your second question, set the argument p2s=2, which will give more screen
output and help us understand what is going on in your EM chain. Repost the
problem with the new screen output, or send it to me directly, and I should
have a more accurate diagnosis.
For your third question, this depends on whether you are using the GUI
AmeliaView, or calling Amelia from R directly. Which are you doing?
regards,
James Honaker
Hello all,
I have three questions concerning Amelia II, and I would greatly appreciate
any information you may provide.
First, I have been trying to install the updated version of Amelia II
(1.1-29) onto my computer today, but I keep getting the older version
(1.1-26). Could someone please point me to the right direction? Here is the
R command I used, and results shown in my R program:
**********************************************************************
-
Amelia mailing list served by Harvard-MIT Data Center
[Un]Subscribe/View Archive: http://lists.gking.harvard.edu/?info=amelia
install.packages("Amelia",repos="http://gking.harvard.edu")
trying URL
'http://gking.harvard.edu/bin/windows/contrib/2.5/Amelia_1.1-26.zip'
Content type 'application/zip' length 2148370 bytes
opened URL
downloaded 2098Kb
**********************************************************************
Second, I am trying to do some diagnostics on the imputed datasets. However,
the program is always idle at iteration 18 of the third imputed dataset. I
can tell that that the CPU of my computer is not working at at full speed,
as it drops down to 1% or 2% as opposed to 100% previously. I have tried to
modify the imputation code several times and this problem always exists.
Note that I don't have any problem when I imputed the same dataset with
fewer variables. Is this a bug?
Third, it seems that I have to conduct diagnostics immediately after the
imputation. Is there a way to call the imputed dataset and do diagnostics on
a later time without imputing the datasets all over again?
Thanks a lot in advance for your help.
Best,
Xiaobo
-
Amelia mailing list served by Harvard-MIT Data Center
[Un]Subscribe/View Archive: http://lists.gking.harvard.edu/?info=amelia