On Thu, 12 Oct 2006, Sven Schreiber wrote: With VARs, at present, the only values you can retrieve via the gui are the per-equation residuals (under the Save menu in the model window). Basically this is because all other available values are matrices, and there's no facility (yet) for handling matrices in the gui (only series and scalars). One other point: when you estimate a model via the gui (single equation or multiple) it does _not_ become the "last model", for data retrieval purposes, so far as the console is concerned. This is perhaps debatable, but it's by design. The idea was that things could get confusing. Suppose a user has one "thread" going in the console (estimate, retrieve values, calculate), and then, "on the side", estimates a model via point-and-click. Then where should, say, $uhat be drawn from in the next console command? At present the answer is, from the last model estimated via the console. Actually, the underlying assumption is that anyone doing anything at all complicated with retrieval of model data would write a script, in which case these issues don't arise. Allin.

On Fri, 13 Oct 2006, Sven Schreiber wrote: Yes. When you have a model window open, the window is "shadowed" by an in-memory copy of the model in question, so when you save data from a given model window you should always get data from that particular model, regardless of any other models that may have been estimated more recently. I can see a case for having the behaviour that you expected (i.e. estimating a model via the gui updates the "last model" as seen from the console). That wouldn't be difficult to do. There is such a mechanism on sourceforge. I haven't used it much to date, but it's there. There's some exploratory code in place, not activated yet. I'll get around to doing some more on that at some point. Allin.