On Sat, 19 Sep 2020, Riccardo (Jack) Lucchetti wrote:
I was thinking that there are quite a few things we should make a decision on
for the next version. One is exposing our time disaggregation apparatus
(currently hidden as the _tdisagg()) function.
I'm in favour of that, and it's next on my agenda after getting
regls squared away (almost there, I think). Exposing tdisagg
properly means writing a decent GUI for it: shouldn't be too hard
but it's always kinda time-consuming.
Another one is finally getting rid of tha arbond command.
I don't have strong feelings about that.
On a more general level, now that Allin has implemented elastic nets
should we have a "machine learning tools" submenu somewhere, with SVM, LASSO
Maybe so. I hesitate just because it's not clear to what extent
these things can be represented in the GUI. SVM has no GUI at all at
present. regls (LASSO/Ridge/Elastic net) has a rudimentary
GUI-in-progress, but in neither case can you make serious use of
these tools without scripting (and setting up cross validation).
There are too many intricate and cross-linked options.
Well, maybe that's too strong a statement. Perhaps what I'm really
saying is that I dread designing and coding the highly complex GUI
that would be needed to enable serious use of machine learning via
point-and-click. It's a bit like trying to do a GUI for the Kalman
filter. OTOH, I guess it would be a good selling point if we took
the (considerable) trouble.