EViews.com

Strange that it is really unfixable in an easy way. I guess the 'used objects name list' is just some data structure that can be simply deleted. Maybe as a workaround only after it gets a thousand elements or something. This really might deserve some more attention, especially now that the 64-bit ve...

That's a fantastic example program. Thanks! The issue is with the creation and deletion of objects with different names. A single EViews program keeps track of all named objects that get created, even if they are deleted. You're creating tens of thousands of named objects (with different names) and...

I did some more testing on this. It appears that the combination of creating objects together with performing some operation on them causes the process to take more and more time, if done in a single program. The attached programs allow you to see the issue. The program iteratively creates new objec...

Thanks!

Okay, a pity though!

Is there a way to resize (enlarge) a vector or matrix and initialise the new elements to NA instead of zero, without the use of cumbersome for-loops and helping variables?

What is the difference between @isna(a) and a=na in if statements? Which one would be better or faster? The result is the same.

Thanks for reconsidering building this. It is true that using delete a* is 'an alternative method of achieving the same thing', but this is not true for the @keeplist option, though maybe you could copy the objects to keep to a new workfile and use copy a* to keep only those objects...

Okay, it is going to take some time though to abridge the code and make up something presentable for you. I'll get back to this.

Is there any reason why this loop's iterations, for !i=1 to 100 [do something] next would require increasing amounts of time when there is no reason for that in the code? Perhaps due to some memory quirk? Iteration 100 is a several orders of magnitude slower than the 1st iteration. The statements be...

When copying estimated state space objects (by dragging them, copy/pasting or the copy command), the information criteria fields are not copied along. That is, the new object does not have a BIC, AIC, etc.

Thanks for the prompt reply. Why would this not be made possible to work with normal work files though? Also, I searched for it but I must admit I cannot find any reference for this in the Eviews Command and Programmming Reference manual (the latest version from April 2013). In fact, the example und...

Maybe I am missing the obvious here, but this program saves all variables instead of dropping them: What am I doing wrong?

Reproduce using the following program.

Thanks a lot, I wasn't entirely sure whether you meant if any errors during initial starting estimates are handled (the amount of which is controlled by startiter) or also the errors during final estimations (controlled by startnum). A little more information on how the randomization works might be ...