2:02 p.m.
Regarding the new modprint command...
Rlease
1. Document it in the user's manual.
2. Add it as a recognised highlighted command in script files (e.g. mark it
with brown just as the print and printf commands).
Best regards
Andreas
11:13 p.m.
On Wed, 28 Jan 2009, andreas.rosenblad(a)ltv.se wrote:
Regarding the new modprint command...
Rlease
1. Document it in the user's manual.
A brief description is already in the reference manual and in the online
help. But you're right, an example would be helpful.
2. Add it as a recognised highlighted command in script files (e.g.
mark it
with brown just as the print and printf commands).
Hmmm... this should already happen. It does work here.
Riccardo (Jack) Lucchetti
Dipartimento di Economia
Università Politecnica delle Marche
r.lucchetti(a)univpm.it
http://www.econ.univpm.it/lucchetti
11:37 p.m.
On Thu, 29 Jan 2009, Riccardo (Jack) Lucchetti wrote:
On Wed, 28 Jan 2009, andreas.rosenblad(a)ltv.se wrote:
>
>
> Regarding the new modprint command...
>
> Rlease
> 1. Document it in the user's manual.
A brief description is already in the reference manual and in the online
help. But you're right, an example would be helpful.
Have a look here:
<script>
set echo off
set messages off
function my_own_ols(series y, series x)
s2 = 1
b0 = 0
b1 = 0
mle ll = -0.5*(ln(s2) + e^2/s2)
series e = y - b0 - b1*x
params b0 b1 s2
end mle -q
printf "\n ------ My own ols (via ML!) --------------------------"
table = $coeff ~ $stderr
table = table[1:2,]
names = "constant,x,sigma"
matrix sigma = sqrt(s2)
modprint table names sigma
end function
nulldata 10
set seed 12345
x = normal()
y = normal()
ols y 0 x --simple-print
my_own_ols(y,x)
</script>
Is this too silly to package as a practice .inp file? Or maybe it could
find its way to the User's Manual?
Riccardo (Jack) Lucchetti
Dipartimento di Economia
Università Politecnica delle Marche
r.lucchetti(a)univpm.it
http://www.econ.univpm.it/lucchetti
1:37 a.m.
On Thu, 29 Jan 2009, Riccardo (Jack) Lucchetti wrote:
On Wed, 28 Jan 2009, andreas.rosenblad(a)ltv.se wrote:
>
> Regarding the new modprint command...
>
> Rlease
> 1. Document it in the user's manual.
A brief description is already in the reference manual and in the online
help. But you're right, an example would be helpful.
> 2. Add it as a recognised highlighted command in script files (e.g. mark it
> with brown just as the print and printf commands).
Hmmm... this should already happen. It does work here.
And it works here too. Andreas, what version of gretl are you
running?
Allin.
9:22 a.m.
gretl-devel-bounces(a)lists.wfu.edu skrev 2009-01-29 02:37:38 :
On Thu, 29 Jan 2009, Riccardo (Jack) Lucchetti wrote:
> On Wed, 28 Jan 2009, andreas.rosenblad(a)ltv.se wrote:
> >
> > Regarding the new modprint command...
> >
> > Rlease
> > 1. Document it in the user's manual.
>
> A brief description is already in the reference manual and in the
online
> help. But you're right, an example would be helpful.
>
> > 2. Add it as a recognised highlighted command in script files
(e.g. mark it
> > with brown just as the print and printf commands).
>
> Hmmm... this should already happen. It does work here.
And it works here too. Andreas, what version of gretl are you
running?
Version 1.8.0 build date 2009-01-26 on Windows XP.
Andreas
10:18 p.m.
On Thu, 29 Jan 2009 andreas.rosenblad(a)ltv.se wrote:
> And it works here too. Andreas, what version of gretl are you
> running?
Version 1.8.0 build date 2009-01-26 on Windows XP.
Ah, I see: the modprint help item is there OK, but the Windows
version of the XML file that causes commands to be highlighted in
the script window was not up to date (the mechanism for
auto-updating that file was not working). Now fixed.
Allin.
5564
days inactive
5565
days old
5 comments
3 participants
participants (3)
-
Allin Cottrell -
andreas.rosenblad＠ltv.se -
Riccardo (Jack) Lucchetti