In versions prior to 13, there wasn't a clear distinction between the vector and rowvector types. In some places you could use a rowvector and in others you could use a vector. To make matters worse, there are instances where you could use both. This made EViews behavior ambiguous.
Case in point, is the usage of @convert. In versions prior EViews 13, while the command
would run and not error, if you opened M1 you will quickly notice M1 is actually a rowvector despite being declared as vector and the type listed at the top of the window as 'vector'.
In EViews 13, we have removed a lot of the ambiguous behavior. The rowvector type is now a separate type. Better error reporting and more stringent usage has been implemented when pertaining to rowvectors. Aesthetically speaking, rowvectors now have a unique icon in the workfile window and the type listed at the top of window is now 'rowvector'.
To resolve the reported issue and depending on whether you want M1 to be a vector or rowvector, you can either use SpanbergEriks suggestion of transposing the results returned by @convert or you can declare M1 as a rowvector.
Code: Select all
Vector M1 = @Transpose(@Convert(A))
or