12:09 a.m.
Thanks Allin so much for such a quick response and fix to the crash report.
Relating to the coeffsum and restrict command block, however, I have a few questions.
1. In my script, I need to make the coeffsum be quiet, but that seems not to be an option.
Would it be hard to add one?
2. Coeffsum gives a t-test reading while the restrict gives an F-test result. I prefer the
t-test result for it gives me the sign of the sum, but shouldn’t both be an F-test?
Thanks,
Fred
On Mar 27, 2019, at 12:00 AM, gretl-users-request(a)lists.wfu.edu
wrote:
Send Gretl-users mailing list submissions to
gretl-users(a)lists.wfu.edu
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.wfu.edu/mailman/listinfo/gretl-users
or, via email, send a message with subject or body 'help' to
gretl-users-request(a)lists.wfu.edu
You can reach the person managing the list at
gretl-users-owner(a)lists.wfu.edu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gretl-users digest..."
Today's Topics:
1. Re: gretl crashed with a message of "Abort trap: 6 "
(Allin Cottrell)
----------------------------------------------------------------------
Message: 1
Date: Tue, 26 Mar 2019 09:51:31 -0400 (EDT)
From: Allin Cottrell <cottrell(a)wfu.edu>
To: Gretl list <gretl-users(a)lists.wfu.edu>
Subject: Re: [Gretl-users] gretl crashed with a message of "Abort
trap: 6 "
Message-ID: <alpine.LNX.2.21.1903260949320.16110@robroy>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On Tue, 26 Mar 2019, Fred Engst wrote:
> My beloved gretl crashed on me. (:
> My scrip was doing great for that last year until I added a line with the coeffsum
command.
> It repeatedly crashed over and over again.
> So I setup a small test dataset and invoked gretlcli, and it seems that coeffsum
worked the first time, and crashed the 2nd time with an error message of "Abort trap:
6?.
> What did I do wrong?
>
> Here are the files that you might need to replicate the situation and help me out:
> 1. a test dataset,
> 2. the scrip that crashes gretlcli
> 3. the log from gretlcli
> 4. two crash reports when I did run gretl & gretlcli.
Thanks, Fred, for the detailed report. The problem is now fixed in git
and snapshots. In "coeffsum" (and in "restrict" more generally) we
were not setting aside enough space for very long variable names.
Allin
------------------------------
_______________________________________________
Gretl-users mailing list
Gretl-users(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-users
End of Gretl-users Digest, Vol 146, Issue 20
********************************************
6:53 a.m.
Am 27.03.2019 um 01:09 schrieb Fred Engst:
Relating to the coeffsum and restrict command block, however, I have
a few questions. 1. In my script, I need to make the coeffsum be
quiet, but that seems not to be an option. Would it be hard to add
one?
I agree that would be useful, similar to what has been added to (almost)
all similar commands over the past years.
(According to the reference it seems that the following test commands
still do not have such an option: hausman, meantest, runs, vartest,
possibly vif.)
2. Coeffsum gives a t-test reading while the restrict gives an
F-test result. I prefer the t-test result for it gives me the sign
of
the sum, but shouldn’t both be an F-test?
The tests are totally equivalent since the F version has just 1 d.o.f.:
<hansl>
open hall
ols consrat const ewr vwr
coeffsum ewr vwr
eval $test^2 # the F version
restrict
b(ewr) + b(vwr) = 0
end restrict
</hansl>
Notice the identical p-values.
cheers
sven
9:57 p.m.
On Wed, Mar 27, 2019 at 2:54 AM Sven Schreiber <svetosch(a)gmx.net> wrote:
Am 27.03.2019 um 01:09 schrieb Fred Engst:
> Relating to the coeffsum and restrict command block, however, I have
> a few questions. 1. In my script, I need to make the coeffsum be
> quiet, but that seems not to be an option. Would it be hard to add
> one?
I agree that would be useful, similar to what has been added to (almost)
all similar commands over the past years.
That's now enabled in git and snapshots.
Allin
3:02 p.m.
Am 27.03.2019 um 22:57 schrieb Cottrell, Allin:
Am 27.03.2019 um 01:09 schrieb Fred Engst:
>> Relating to the coeffsum and restrict command block, however, I have
>> a few questions. 1. In my script, I need to make the coeffsum be
>> quiet, but that seems not to be an option. Would it be hard to add
>> one?
That's now enabled in git and snapshots.
Thanks Allin. Is there any deeper rationale for those (test) commands
that do not have the quiet option? (Well, apart from the fact and good
reason that it means more work for you right now.)
cheers
sven
4:03 p.m.
On Thu, 28 Mar 2019, Sven Schreiber wrote:
Am 27.03.2019 um 22:57 schrieb Cottrell, Allin:
> Am 27.03.2019 um 01:09 schrieb Fred Engst:
>>> Relating to the coeffsum and restrict command block, however, I have
>>> a few questions. 1. In my script, I need to make the coeffsum be
>>> quiet, but that seems not to be an option. Would it be hard to add
>>> one?
> That's now enabled in git and snapshots.
>
Thanks Allin. Is there any deeper rationale for those (test) commands
that do not have the quiet option? (Well, apart from the fact and good
reason that it means more work for you right now.)
No deeper rationale (for any test command that deposits $test and
$pvalue). It's just a matter of
* add an entry in the big options array in lib/src/options.c
* revise the underlying C function to respect OPT_Q
and, if the command in question doesn't currently accept any options,
* revise its entry in the commands array in lib/src/tokenize.c
* revise the signature of the underlying function
* revise all calls to the underlying function to pass a "gretlopt".
Allin
2114
days inactive
2115
days old
4 comments
4 participants
participants (4)
-
Allin Cottrell -
Cottrell, Allin
-
Fred Engst -
Sven Schreiber