Jack and I have recently been working on a new accessor. It's named "$result" (so far) and it gets you a matrix after execution of commands that don't have specific accessors of their own but whose output can reasonably be represented as a matrix.

On Sat, 16 Feb 2019, Sven Schreiber wrote: > Am 15.02.2019 um 22:10 schrieb Allin Cottrell: >> Jack and I have recently been working on a new accessor. It's named >> "$result" (so far) and it gets you a matrix after execution of >> commands that don't have specific accessors of their own but whose >> output can reasonably be represented as a matrix. >> > > If it's really just for a matrix, why not call it $mresult or > $matresult or $outmatrix or something? In fact, $mresult was Allin's original idea. I like $result better, but I'm not putting up a fight on this.

Drawing the connection to the vif-related feature request (https://sourceforge.net/p/gretl/feature-requests/101/), does this new $result bundle contain everything wanted in that request? Which basically means the VIFs and then the BKW table I guess.

That would be great of course, because it would solve that ticket (and by implication, probably would make the bkw.gfn package obsolete).

Am 13.03.2019 um 23:34 schrieb Riccardo (Jack) Lucchetti: > On Wed, 13 Mar 2019, Sven Schreiber wrote: >> Drawing the connection to the vif-related feature request >> (https://sourceforge.net/p/gretl/feature-requests/101/), does this new >> $result bundle contain everything >> That would be great of course, because it would solve that ticket (and by >> implication, probably would make the bkw.gfn package obsolete). > > Yes, I suppose it does. Well, it's looking good already (tried with the latest snapshot on Windows), but there's one thing that the bkw.gfn package covers and the 'vif' command doesn't, namely nonlinear models. I got an error trying out 'vif' after an 'nls' block. In the doc for 'vif' this limitation doesn't seem to be mentioned. I guess the VIFs themselves do not make much sense outside of ols (or do they?), but these days the vif command also gives you the BKW table, of course. So perhaps could 'vif' be activated for nonlinear models, and give only the BKW table?

Am 15.03.2019 um 07:27 schrieb Riccardo (Jack) Lucchetti: > On Thu, 14 Mar 2019, Sven Schreiber wrote: >> the 'vif' command doesn't, namely nonlinear models. I got an error trying >> out 'vif' after an 'nls' block. In the doc for 'vif' this limitation >> doesn't seem to be mentioned. >> So perhaps could 'vif' be activated for nonlinear models, and give only >> the BKW table? > > It happens already: > probit LFP const WA WE --quiet OK, good to know, but then what about the 'nls' case I mentioned?

Am 15.03.2019 um 10:48 schrieb Riccardo (Jack) Lucchetti: > > Oh, sorry, I had read your message to superficially, sorry. I thought > you meant "non-linear" as in "non-OLS". Yes, I think we could enable > that. I did indeed mean non-OLS, nls was just an example, as was your probit example. So sometimes it works and sometimes it doesn't, it's not clear to me by what criterion. The aim would be to enable that always, except when there are intrinsic reasons not to do it.

Am 15.02.2019 um 22:10 schrieb Allin Cottrell: > Jack and I have recently been working on a new accessor. It's named > "$result" (so far) and it gets you a matrix after execution of commands > that don't have specific accessors of their own but whose output can > reasonably be represented as a matrix. > If it's really just for a matrix, why not call it $mresult or $matresult or $outmatrix or something?