On Sun, 27 Sep 2015, Schaff, Frederik wrote:
Ok. Here is the "script output" and also a part of one file
that is
problematic. The "observation" in the script-out refers to the
"config" variable (first column)-1 (because configs range from 0 to
...), there are three problematic values in the file.
Thanks. The correct fix here it to edit the data file to turn the
uninitialized values into NAs (or perhaps 0s, depending on how they
came about?). Or better, to fix the process that produced the data
file and re-run it.
Note that whether such values are taken as "numeric" or not will in
general depend on the C library in use. But either way they're wrong
and have to be changed. _If_ you can get such values into gretl as
numeric, you could fix them via something like:
foo = (abs(foo) > 0 && abs(foo) < 1.0e-100)? NA : foo
where "foo" is the name of the series to be fixed and we're assuming
that non-zero observations with absolute value less than 10^{-100} are
garbage. This is not very reliable, however, as it's _possible_ that
some uninitialized doubles happen to fall in the "normal" range and so
escape correction. The only truly reliable procedure is to fix the
process that generated the data in the first place.
Allin Cottrell