On Fri, 23 Oct 2009, Riccardo (Jack) Lucchetti wrote: > On Thu, 22 Oct 2009, Allin Cottrell wrote: > > What I'm aiming to implement is: > > > > * the ability to save a named model within a loop; > > > > * the ability to add the last model to the "model table" within a > > loop; plus > > > > * the corresponding functionality for graphs within loops (save > > named graph; add graph to the GUI "graph page"). > > > > So this is something that, hopefully, should be available before > > too long. > > FWIW, I'm not entirely enthusiastic about this kind of thing. Sure, the > more you can do (especially in a script), the better. But my spider sense > is tingling --- there are many many things that can go wrong with this > apparatus.
You may well be right, but what sort of going-wrong do you have in mind? > By the way, what's the point of storing models in a loop? The only > situation I can think of is when you have to apply the same estimation > method over and over again and need to compare the results at the end. > Except when you have very few of them, you probably won't want to compare > them by clicking on each model in turn and having a gazillion windows open > on your desktop. What you probably want to do is store the relevant > quantities (coefficients, residuals, information criteria) somewhere (in a > matrix, a text file, whatever) and start from there. I agree, that will often be a smarter thing to do. I was thinking of the case where you're estimating relatively few models (maybe the same model on different samples), and you'd like to be able to compare the models side by side. Of course in such a case it shouldn't be too burdensome to "unroll" the loop, yet in some contexts there may be a fair amount of setup to be repeated each time, so that a loop might be noticeably more convenient. Allin.
