Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#178 Unable to print OLS, ARIMA model output

v1.0_(example)
closed-fixed
None
5
2013-05-04
2013-05-02
Good_Newz
No

Trying to print an OLS, ARIMA model estimates produces the following output: "Invalid byte sequence in conversion input". Consequently the output is never printed.

The error appear to be in OLS models and ARIMA models. AR(1) models print fine. I have only tested those 3 scenarios.

Gretl version 1.9.12, System - Windows XP.

Attaches is a sample file that produces an error. The error is not specific to this file it happens with any gretl file.

1 Attachments

Discussion

  • Allin Cottrell
    Allin Cottrell
    2013-05-02

    • assigned_to: Allin Cottrell
     
  • Allin Cottrell
    Allin Cottrell
    2013-05-02

    By "printing" you mean doing File/print in the model window?

    What language are you using when running gretl?

    Does this happen only when one or more negative values appear
    in the printout (and hence minus signs are displayed)?

     
  • Good_Newz
    Good_Newz
    2013-05-02

    Yes, printing is File/print. The error appears after I press OK in the printing dialog.

    I am running Gretl in English.

    So far I haven't encountered a situation where I was able to print the the output (the log-likelihoods are always negative)

     
  • Allin Cottrell
    Allin Cottrell
    2013-05-02

    I believe this should now be fixed in CVS and the Windows snapshot.
    Certainly, it works OK on Windows 7.

     
  • Good_Newz
    Good_Newz
    2013-05-02

    I can confirm that printing OLS works without a hitch.

    However printing an ARIMA model produces a print out but gretl crashes with the following error (see attachment)

     
    Attachments
  • Allin Cottrell
    Allin Cottrell
    2013-05-02

    Can you please post a session file containing the ARIMA
    model in question? Thanks.

     
  • Good_Newz
    Good_Newz
    2013-05-02

    Here it is. The model number is 2. The error occurs after printing has completed.

     
    Attachments
  • Allin Cottrell
    Allin Cottrell
    2013-05-03

    Thanks. I think this should now be OK in today's snapshot.

     
  • Good_Newz
    Good_Newz
    2013-05-03

    I just tested it with today's build. I still have the crash with error message.

     
  • Allin Cottrell
    Allin Cottrell
    2013-05-03

    Oof, yes, there was still a bug. Should really be fixed now.

     
  • Good_Newz
    Good_Newz
    2013-05-03

    It looks fixed to me too.

     
  • Allin Cottrell
    Allin Cottrell
    2013-05-04

    • status: open --> closed-fixed