Re: [Gretl-users] Gretl-users Digest, Vol 117, Issue 6
by guido giaume
> > Hi all
> > I am unable to sort a matrix and sorting the same colname.
> >
> >
> > E.G.
> >
> > matrix M = {Class_A..Class_D}
> >
> > colnames(M, "Class_A Class_B Class_C Class_D")
> >
> > A = dsort(M)
> >
> > printing A I see the right numerbs but the wrong colnames and
> > despite my
> > research in the Gretl User?s Guide I was unable to find myself the
> > solution.
> Hi Guido,
>
> what gretl version are you using? According to the dsort()
> documentation
> it doesn't apply to a matrix that is not a vector (more than one
> column). And indeed here for me I get an (expected) error when I try
> dsort(m) where m has two columns.
>
> Also it is not clear to me what you want to achieve. Perhaps the
> msortby() function is right for you.
>
> cheers,
> sven
>
Dear Sven
thanks for your quick answer.
My Gretl version is 2016-c but it does not matter.
You are right, I didnt tell all the story. But was not for cheating. I
tried to cut short the description of the problem.
I mentioned a matrix, but indeed I was working with a 1 row "matrix".
My real problem is ranking some time series, day by day;
And the trouble is the sorting mismatch the names of the series with
their values.
(E.G.) If I have A, B, C, D daily series and I want (recursively) rank
their values at day t, and then at day t+1, and so on, I am in
trouble,
because all my attempt of sorting does not keep the values with the
original series names, while in Excel is trivial.
I tried in many ways, unsuccessfully.
My last attempt was
a) limiting the whole dataset to only 1 day, (by
smpl)
b) declaring it as a one row matrix
c) giving it the right names
(via colnames)
d) ranking the values
but as before, I got the (values) rank but I lost the match with the names of time series.
So any help, or reference to the User Guide, will be greatly appreciated.
Guido
9 years, 1 month
matrix sorting and "losing" colname
by guido giaume
Hi all
I am unable to sort a matrix and sorting the same colname.
E.G.
matrix M = {Class_A..Class_D}
colnames(M, "Class_A Class_B Class_C Class_D")
A = dsort(M)
printing A I see the right numerbs but the wrong colnames and despite
my research in the Gretl User’s Guide I was unable to find myself the
solution.
Any suggestion?
Thanks a lot
Guido
9 years, 1 month
Re: [Gretl-users] Version 2016d - git
by George Matysiak
On my initial installation, data files from Ramanathan, Wooldridge and
Greene were not included on the > Sample file tabs. I have now uninstalled
and re-installed gretl and all seems. Apologies for the minor panic.
9 years, 1 month
warning: gdt-reading bug
by Allin Cottrell
We've just noticed that a bug was introduced into our code for reading
native gretl .gdt data files in August of this year. The bug should be
triggered only rarely, but we thought it wise to issue a warning.
Description of bug: If a gdt file contains "subnormal" values (that
is, floating point values that are too close to zero to be represented
with the usual precision), then when such a file is read on Linux, the
first subnormal value to be found on a given row (observation) will be
incorrectly copied into the remaining columns (series) on that row.
Example: A gdt file containing 10 series has a subnormal for series
number 5 on row 25. Then when the file is read on Linux, that
subnormal will replace the correct values for series 6 to 10 for
observation 25.
Comment: This won't affect the reading of "primary" data (actual
micro- or macroeconomic measurements), which will never contain
subnormal values (we're talking about absolute values less than 10 to
the minus 307). And the bug is not triggered on MS Windows. However,
subnormal values may be produced by some data transformations (such as
squaring very small numbers, or computing the normal CDF of very big
negative values).
Fix: This is now fixed in the git source for gretl and also the
current snapshots. And we will put out a new release soon, gretl
2015d.
Diagnostic: If you think a dataset may suffer from this problem,
you can run the script checkdata.inp, from
http://ricardo.ecn.wfu.edu/pub/gretl/checkdata.inp
First load the dataset in question. Then open checkdata.inp and run
it. An affected dataset may produce something like this:
<script-output>
Total number of values examined: 164122
Check for subnormal floating-point values
-----------------------------------------
Total number found: 138
Longest (row) sequence: 138
(occurs at obs 210, starting series ID 461)
Number of sequences (of length >= 2): 1
</script-output>
The symptom of a problem is that we find a consecutive sequence of
subnormal values on one or more rows of the dataset. This could occur
for "natural" reasons but it may indicate corruption. Isolated
subnormals don't indicate the bug. And again, most datasets should
contain no subnormal values.
Allin Cottrell
9 years, 1 month
