EViews 9 copy bug? - (c=c) i.e. cubic spline interpolation

[hgrah]

I was pleased to hear that with EViews 9 support was said to be added for interpolation that allowed matches to "first" to complement the existing "last" option for cubic spline

However, I cannot see the option available in the copy command documentation, and when I use "last" now it seems to produce an interpolation based upon "first". If I use EViews 8 I get the correct lineup.
e.g.

Code: Select all

copy(c=c) QCPI\iaupcz real\iaupcz

last_appears_to_be_first.png (30.37 KiB) Viewed 9385 times

as per attachments.

It would be great if both options could be made to work for cubic spline

Thanks
Graham

[EViews Steve]

This was actually fixed in the April 27 patch (released 2 days ago). Please update to that version and let me know if it works for you...

Steve

[rousing]

Hi

has this really been fixed? and what are the correct commands since i don't find this in the documentation c=cl, c=cf?

Best regards
Rasmus
Sep 2 2016 build

[EViews Steve]

Not sure how we missed this in our documentation, but here's the info you asked for:

For cubic spline match first, use the following:

Code: Select all

c=cubicf

For cubic spline match last, you can use either

Code: Select all

c=cubicl

or

Code: Select all

c=c

I'll notify our documentation team about the missing info.

[rousing]

great thanks a lot

[EViews Steve]

Oh, one other note.

If you see that our documentation is missing something, with EViews 9 you can simply refer to the captured command after going thru the associated dialog. In this example, if you performed a manual copy operation and chose Cubic Match First for the up conversion, you'd see the c=cubicf option in the captured command.

I'll make sure our documentation is updated. Thanks for the heads up.

[rousing]

that was also a problem (otherwise i would not have written in the forum), when I converted the db linked series manually (to cubic first) - this did not reveal the code in the capture window...

[EViews Steve]

Were you performing a fetch when you did the conversion, or were you converting a series object already in your workfile to another page with a higher frequency?

[rousing]

i did a linked fetch with no other inputs ("fetch(d="db",link) seriresname") and then manually the frequency conversion afterwards

[EViews Steve]

Sorry, but I need a few more details.

When you performed the fetch, did you do it to a workfile with a matching frequency or did you do it to a higher frequency workfile?

Then how did you manually do the frequency conversion afterwards? Was there another workfile page with the target frequency involved or did you try to change the frequency conversion type in the fetch link?

[EViews Steve]

Well I looked into the FETCH captured command and it wasn't generating the correct conversion option.

I've changed this so the next patch should fix it. This means if you manually COPY an object in the database window, then do a PASTE special into a workfile window, then in the dialog select a specific conversion option, the resulting FETCH command should now reflect the proper c= option.

If you manually change a linked series' conversion option after doing the FETCH, we currently don't have a programmatic way of doing this (at least not directly) so there's no command to capture.

Thanks again.

[rousing]

great, thanks a lot for your help