EViews.com

Use @stdevs rather than @stdev

Easiest way, if the series don't have interior missings, is to just do:

(or in a loop).

If there are interior missings, then something like:

The "C" object in the workfile is the coefficient vector. It contains the results of the last estimation performed. In a new workfile, if you haven't run any regressions yet, it will be full of zeroes. As soon as you estimate something, it will become populated. The values in the "C&q...

No.

I still don't see what you're trying to do. If you just want a count,why do you need to see the series?

For that specific case, I'd do:

I don't follow.

where time is the date you are interested in.

Yes

Either that or a specific date.

Regarding the first issue, my example programs suggest that structure-consistent wf2db-referencing works well. Therefore, it seems that some relevant pieces of information about the data structure of the series are stored in a db. They're just stored as undated series. No date or crossid informatio...

It is not built in.

Not without more details.

No, databases don't support panels properly. Specifically, although they store the data, they do not store date/cross-section information. So when you do the "show", it ignores dates: close @wf !ncrossids=1 'number of crosssections wfcreate(wf=f1) a 2000 2002 !ncrossids series x=(@trend+1)...

Not really a bug per se, just the results of abusing the EViews programming language :D You are not really supposed to be able to access objects from another workfile using the show wf:: syntax. The :: syntax is only supposed to be used for databases. Luckily EViews will interpret a workfile as a da...

@makevalidname might be useful too (quicker to inplement, not as nice output).

http://www.eviews.com/help/helpintro.ht ... dname.html