I want to report a possible bug in saving script files on the latest snap shot win 7 64 bit. Sometimes when more that one script file is open with the editor in tab mode, the save command overwites both files with the script file in focus. Here is the big problem. I cannot figure out how to trigger the behavior. It just happens sometimes. So since I cannot replicate the problem this is officially the world's most useless possible bug report, apologies.
Sent from my T-Mobile 4G LTE Device
I'm going through the sourceforge tracker issues, and we need some input
from Allin regarding bug 174:
Ping -- the circular references between the User Guide and the Command
Ref. are still there.
I see two options / design decisions for the "modeltab":
- It's only made for OLS-estimated models, and that's the way it is.
- The plan is to extend it to (some) other estimators, but it's not
In any case IMHO the docs should be updated to communicate the situation.
Allin, could you announce your opinion on this? Otherwise eventually I
would try to add to the docs somewhere the statement that the modeltab
is only meant for OLS.
Here's a belated response to Sven's question in
To reprise his question: suppose we have matrices a and b as follows:
a (3 x 2)
b (1 x 3)
0 1 2
Now we do
c = a ~ b, and gretl gives us
c (3 x 3)
1 1 0
1 1 0
1 1 0
Is this a bug or a feature? I think it's a bug: this should provoke an
error. I believe the code in question (gretl_matrix_col_concat(), in
gretl_matrix.c) reflects the intent that if b were a 1 x 1 matrix we
would append to a column that repeats b's single element -- as an
acceptable generalization of columnwise concatenation -- but it fails
to determine whether b really is 1 x 1.
Jack, do you think that's right? If so I'll go ahead and fix it.
Dear gretl team,
from time to time I am using the "plot end plot" command block Allin and
Jack have introduced last year.
Typically it works fine but I obtain an error using gretl cvs from 5th of
March 2015 on Windows (64-bit version) now. The error "Data error" occurs
when trying to suppress the fitted line.
open denmark.gdt --quiet
list lplot = LRM LRY
options with-lines fit=none
end plot --output=display
There have been some developments in the realm of gretl function
packages lately. Jack and I plan to write up a proper guide to all
this, but in the meantime here are a few notes to be going on with.
(References to the gretl GUI below should be understood as valid for
current CVS and snapshots.)
1. The handling of function-package uploads has been revised
Up till now, uploaded packages (whether new ones or revisions of old
ones) have gone straight in to the "public area", where they're
accessible via the gretl GUI and also via the web interface at
Now, uploads will in the first instance go into a "staging"
directory for approval. When an upload is received, a notification
email gets sent to me. (Once this is tested a bit more I'll put some
more people on the notification list.) Right now, "approval" will
basically just be a matter of checking that the package's sample
script meets the requirements set out in
should not take long. The process may be made somewhat more rigorous
Note that you can see what's in "staging" at
2. Packages can now be uploaded in zip-file form
Until recently all regular packages (as opposed to "addons") had to
take the form of simple gfn (XML) files. Now they can be zip files,
allowing the possibility of including extra material in the package.
Examples on the server: HIP.zip (Jack Lucchetti and Claudia Pigini)
and almonreg.zip (not very exciting, written by me as a test case).
The "extra material" we have in mind may include
* PDF documentation
* Zero or more data files (gdt or gdtb)
* Zero or more matrix files
* Zero or more bundle (XML) files
If you include a data file with your package this can be opened in
your sample script using the new --frompkg option to "open", which
requires the name of the package as a parameter; for example
open almon.gdt --frompkg=almonreg
If you include a matrix file (perhaps to hold a bunch of critical
values for a specialized test) you can open it in your function code
using the built-in $pkgdir string variable, as in
string mname = sprintf("%s/critvals.mat", $pkgdir)
matrix C = mread(mname)
A zip-file package must have a definite structure. Let pkgname be a
variable representing the name of your package (e.g. pkgname =
"HIP", pkgname = "almonreg"), and suppose you're including PDF doc
and a data file. The structure must then look like this:
That is, all the files must be contained in a directory that bears
the name of your package. The name of the gfn file must be
pkgname.gfn, and the name of the PDF file (if present) must be
pkgname.pdf. Data and matrix files, however, can be named as you
The creation of a suitable zip file is handled by the package editor
in the gretl GUI. (There's also a non-interactive shell-based way of
doing this and uploading the file, but I won't get into that here.)
The trigger for creating a zip file to upload (when you check the
box "Upload package to server on save") is that you have (a)
specified PDF documentation by typing "pdfdoc:pkgname.pdf" into the
Help area in the package editor and/or (b) added the names of some
extra files to include, using the new "Data files" tab in the dialog
which appears when you click the "Extra properties" button in the
If you're building your package via a .spec file, the appropriate
magic to put into that file is (illustrating via almonreg):
help = almonreg.pdf
data-files = almon.gdt
(The "data-files" line can accommodate more than one filename,
separated by spaces.)
3. Easier access to sample scripts
In the gretl GUI, there's now an easy way for the "consumer" of a
given function package to bring up and execute its sample script.
When you open the listing of packages on the local machine, there's
both a toolbar button and a right-click (context) menu item, "Sample
script". In the first instance this opens the sample script as
executable but not editable. To make it editable, use the "Save
as..." button and give it a name of your choosing.
Recently Henrique Adrade suggested there should be a command-line
means of installing a function package. Now there is, in CVS and
snapshots: "install" (see the current command reference for help).
Right now it only works for function packages (regular packages, not
"addons"). It could be generalized to cover addons, databases, and
data-file collections if there's a demand.
When you right click on a time series in your dataset and select
'correlogram', the autocorrelations, partial autocorrelations, Q
statistic (Ljung-Box) and their pvalues are printed and these pvalues
are correctly obtained from a chi-square distribution with M degrees of
freedom being M the number of autocorrelations tested.
But when you estimate an ARIMA model and, in the model window, you
select Graphs->residual correlogram, I think gretl is applying the same
function so the output window is printing the pvalues obtained from a
chi-square (M) while now this should be (M-p-q). So the pvalues shown
are incorrect. In fact if, in the model window, you select
Tests->Autocorrelation, you may obtain the Ljung-Box statistic with the
pvalue obtained correctly from a chi-square (M-p-q)
*EKONOMIA APLIKATUA III SAILA (EKONOMETRIA ETA ESTATISTIKA)/
DEPARTAMENTO DE ECONOMÍA APLICADA III (ECONOMETRÍA Y ESTADÍSTICA)
Avda. Lehendakari Aguirre, 83 | 48015 BILBAO
*T.: +34 946013740* | *F.: +34 946013754*
ERNE! Baliteke mezu honen zatiren bat edo mezu osoa legez babestuta
egotea. Mezuak badu bere hartzailea. Okerreko helbidera heldu bada
(helbidea gaizki idatzi, transmisioak huts egin) eman abisu igorleari,
korreo honi erantzunda. Kontuz! Mezua ez bada zuretzat, ez erabili, ez
zabaldu beste inori, ez kopiatu eta ez baliatu.
¡ATENCIÓN! Este mensaje contiene información privilegiada o confidencial
a la que sólo tiene derecho a acceder el destinatario. Si usted lo
recibe por error le agradeceríamos que no hiciera uso de la información
y que se pusiese en contacto con el remitente.
E-mail hau inprimatu baino lehen egiaztatu inprimatzeko beharra.
Antes de imprimir este e-mail piense bien si es necesario hacerlo.
Dear Gretl Team,
I started analyzing the function packages looking for possible
bugs/problems/misbehavior. The first round of tests is very simple: check
if there is the developer's contact mail and check if the sample script is
working fine. I chose a test order classifying them by the author of each
package because I think it will be easier contact them just once to talk
about the problems. The first author is... Allin :-)
Dear Allin, take a look at you packages. It is almost everything working
Name Author Version Date
Contact mail Working example
addlist.gfn Allin Cottrell 1.1 19/08/2009
almonreg.zip Allin Cottrell 0.4 09/02/2015
bandplot.gfn Allin Cottrell 0.2 18/10/2014
criteria.gfn Allin Cottrell 1.1 02/07/2010
fe_stats.gfn Allin Cottrell 0.4 09/11/2014
lomackinlay.gfn Allin Cottrell 1.1 19/08/2009
lp-mfx.gfn Allin Cottrell 0.2 27/06/2013
matrix_perf.gfn Allin Cottrell 0.4 17/06/2014
oprobit_predict.gfn Allin Cottrell 1.0 14/09/2009
sols.gfn Allin Cottrell 1.4
26/01/2014 no yes
suradf.gfn Allin Cottrell 0.1 26/01/2011
tobit_y.gfn Allin Cottrell 0.1 13/07/2011