First difference of a constant
by Henrique Andrade
Dear Gretl Team,
Today I've found a very strange problem on Gretl. Please take a look at the
following *hansl* code:
<hansl>
*open* hamilton.gdt
*series* x = PC6IT
*series* y = PZUNEW
*series* z = EXRITL
*series* teste = ((x[1989:01]/y[1989:01]) * z)/z * 100
*diff* teste
*gnuplot* teste d_teste *--time-series --with-lines --output*=display
</hansel>
I think that mathematically the "teste" expression is a constant. So, the
first difference of a constant variable is equal to zero.
Am I missing something?
Um abraço,
*Henrique Coêlho de Andrade*
15 years
some feedback on system estimation
by Sven Schreiber
Hi,
here's some suggestions for how to improve (IMHO) system estimation in
gretl (or hansl for that matter):
1) The basic system spec syntax is a bit awkward:
'system ... end system'
should be like a parenthesis, as in 'if ... endif', 'loop ... endloop'
etc. Hence the keyword 'system' should be at the beginning of the line.
So instead of:
mysysname <- system
...
end system
it would be better to have:
system -> mysysname
...
end system
or something like that. (Of course such a syntax reform would be
something for gretl 2.0.)
2) It would be nice if the system spec could be built programatically in
a script,
e.g. something like:
<hansl>
mysysname <- system
loop foreach i myendoglist
equation $i myregressorlist
endloop
end system
</hansl>
3) And finally a general (and old) topic: I thought variable identifiers
could now be longer than 15 chars in a script, but I get an error with
list names that become longer than that. As I keep repeating every once
a while (now's a good opportunity) I still find that restrictive, makes
scripts harder to read because we have to use less descriptive,
self-explanatory names.
Cheers,
sven
15 years
out of memory with large lists
by Sven Schreiber
Hi,
today I got an "out of memory" error from gretl, I think it's the first
time for me...
It happened when I did something like:
list L1 = L2 - L3
where L2 has 63 elements, and L3 has 13800 elements. That's because L3
has lots of duplicates -- this is of course a bug in my script and I
have corrected that. Nevertheless, given modern computers with Gigabytes
of memory, it still seems strange that gretl shouldn't be able to handle
that, no? Or am I missing something?
cheers,
sven
15 years
Current CVS status
by FEDERICO LAMPIS
Dear all
Today I've installed the last snapshot of gretl from the cvs and I
checked the function "SETAR" I uploaded in the past.
There are some things that want comment whatever I'm not sure they
could be usefull to the developpers
First of all, now it seems that gretl it is more sensitive to the wrong
presence of semicolons.
I know that in gretl the semicolon at the end of the line are useless,
but anyway I had some of them in the function and gretl worked well.
With the new version gretl crashes. So I put away and uploaded the
correct version of the function.
Another thing. Reviewing the function I noted that if I want see the
code of the function from the button "view code" of the function menu
I can see the command of gretl with different colors. But when I go to
the button "Edit" and after to "Edit function code" the commands of
gretl are not different colored.
All has the same black color. It seems to me that in the previous
version it was possible to see the gretl commands with different colors
when I edited the function.
The last thing. I can't download the add-on SVAR from the command
"Check for addons" in the main menu of gretl I get this message:
"Couldn't find SVAR for gretl 1.9.6"
I forget it, I use Ubuntu 11.04.
Greetings
Federico
--
University Carlos III of Madrid
Department of Business Administration
c/ Madrid, 126, 28903 Getafe (Madrid), Spain
Phone: +34 91 624 98 17/ Fax: +34 91 624 96 07
15 years
doc for $fcast and $fcerr
by Sven Schreiber
Hi,
in the help for 'fcast' it says "...can be retrieved using the accessor
$fcast, and the standard errors, if available, via $fcerr.", but in the
function reference (help menu) these two entries are missing.
Haven't checked whether the accessors work, but will do that soon, since
I'm about to start some serious forecasting with gretl :-)
cheers,
sven
15 years
Error: compat2 undefined
by Allin Cottrell
This is just to report that the issue noted recently by Hélio
Guilherme -- that is, the gretl pdf docs do not compile -- should
now be fixed in CVS. You need to re-run ./configure to activate the
fix.
The problem was that an option we were using with the "geometry"
package has been removed from the latest release of that package. We
now have in place a workaround which I believe should be OK
with both older and newer versions of geometry.sty.
Allin
15 years
gretl 1.9.6?
by Allin Cottrell
I think that we getting overdue for a 1.9.6 release (the change log
is bulging).
If people agree, I'll send out a note to the translators and also a
note to the users list (as suggested by Ignacio Diaz-Emparanza at
this year's gretl conference) announcing a "bug-fix week" before
release.
But does anyone have a reason to prefer holding back on a release?
If so, please say.
Allin
15 years
Suggestion for Makefile.in and news about my compiling problem
by Hélio Guilherme
Hi Allin, Jack and other developers :)
I have been unable to get CVS gretl running on my Linux for some time now,
but recently I have made some progress.
I solved the problem of gretl looking for the old library by deleting .gretl
directory.
Now I have gretl_x11 running, working well all menu entries except when I
need to open a file. The program crashes (with Bugzilla window appearing)
after loading the file (yes, I can see the variables list and info at shell
window). I am sorry to say but I have not tried to open a file in gretlcli.
I have messed around by having set main directory other than
/usr/local/share/gretl (got report of bad directory). Also solved by
deleting .gretl directory.
I solved the problem of gretl looking for the old library by deleting .gretl
directory.
Well, there are some unwarned problems in the compilation process, because
to have gretl_x11 compiled I must cd to gui2 and do a make there. The
configure script reports all OK.
I still have to make buildstamp manually to proceed with compilation. This
happens because of plugins requiring build.h. So, my suggestion is to add
builstamp before lib at the plugins entry:
plugin: buildstamp lib
This solved my problem (but since it calls a perl script would it be harmful
for Windows/OS X?).
Sorry for any incorrections, I am writing by memory. Thanks for your
support.
Hélio
OpenSUSE 11.3 x86_64
15 years, 1 month
