command log doesn't fully track the kpss command - Gretl-users - gretlml.univpm.it

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

command log doesn't fully track the kpss command

Data problem

translation problem in gretl 1.9.8

artur tarassow

Friday, 30 March 2012 Fri, 30 Mar '12

12:26 p.m.

Dear gretl developers, I just found that in current CVS (on windows) the command log doesn't track the kpss command properly. Typing kpss x --trend --verbose in the console, gives the following command log output: kpss x Best, Artur

Attachments:

attachment.html (text/html — 271 bytes)

Reply

Show replies by date

Allin Cottrell

Friday, 30 March Fri, 30 Mar

12:53 p.m.

On Fri, 30 Mar 2012, artur tarassow wrote:

I just found that in current CVS (on windows) the command log doesn't track the kpss command properly. Typing kpss x --trend --verbose in the console, gives the following command log output: kpss x

Hmm, for commands issued via the console, it appears that while the command itself is logged, no options are being recorded (it's the same for "ols ... --robust", or "print ... --byobs" and so on). I'll look into that. Allin

Reply

Allin Cottrell

4:48 p.m.

On Fri, 30 Mar 2012, artur tarassow wrote:

I just found that in current CVS (on windows) the command log doesn't track the kpss command properly. Typing kpss x --trend --verbose in the console, gives the following command log output: kpss x

That's now fixed in CVS. Allin

Reply

4712

days inactive

4712

days old

gretl-users@gretlml.univpm.it

Manage subscription

2 comments

2 participants

tags (0)

participants (2)

Allin Cottrell
artur tarassow