Re: [Gretl-devel] gretl bug: ordered probit model
On Mon, 9 Oct 2017, Artur T. wrote:
Dear all,
just by chance I've found a bug (at least realized using 4-day old git on
ubuntu). When adding a lagged intercept to the ordered probit model, gretl
gets captured in infinite computation (I would call this a 'crash'):
<hansl>
open ooballot -q
smpl Status > 0 --restrict
# works
probit Vote 0 CPI
# crashes (infinite computation)
series const_1 = const(-1)
probit Vote 0 const_1 CPI
</hansl>
The problem lies in the function we use for removing the constant from a
list (list_purge_const in discrete.c), which doesn't handle well the
"lagged constant" case.
However, I was thinking: can lagging the constant ever make sense, in any
situation? Shouldn't const(-1) be a no-op?
-------------------------------------------------------
Riccardo (Jack) Lucchetti
Dipartimento di Scienze Economiche e Sociali (DiSES)
Università Politecnica delle Marche
(formerly known as Università di Ancona)
r.lucchetti(a)univpm.it
http://www2.econ.univpm.it/servizi/hpp/lucchetti
-------------------------------------------------------