On Tue, 20 Mar 2018, oleg_komashko(a)ukr.net wrote:
> Dear all,
> The topic name borrowed from Xavier Sala-i-Martin
> (I JUST RAN FOUR MILLION REGRESSIONS )
> myfilem4em.zip contains auto_arima output with "-a"
> myfilem4em2.zip contains auto_arima output without "-a"
> 792 series: monthly
In current git and snapshots there's a "secret" option for the arma
command, --as197 or just -a, which invokes new code using Melard's
algorithm AS 197 in place of the default Kalman-based code when
estimation is via native exact ML.
The hope -- borne out by our testing to date -- is that AS
On Thu, 15 Mar 2018, Henrique Andrade wrote:
> I've found a new string not translated: "Result too large". It appears
> in this case:
>
>
> eval log(0)
>
For basic mathematical problems of this sort, the error message
comes from the C library, not from gretl. On some systems such
messages
On Thu, 15 Mar 2018, oleg_komashko(a)ukr.net wrote:
> Dear all,
> Today's git help entry for max
> does not mention matrix argument
> But
>
> set seed 13
> matrix a_matrix = mnormal(10^4,10^4)
>
> set stopwatch
> ma1 = max(vec(a_matrix))
> eval $stopwatch
>
>
> set stopwatch
> ma2 =
On Thu, 15 Mar 2018, oleg_komashko(a)ukr.net wrote:
> I did not mean LaTex:
>
> set seed 13
> nulldata 10
> y = normal()
> x = normal()
> ols y 0 x
> # −0.0648094 is $coeff("0")
> eval −0.0648094
> /*
> ? eval −0.0648094
> Unexpected byte 0xe2
> Syntax error
> */
>
> While it is not very natural
On Wed, 14 Mar 2018, Sven Schreiber wrote:
> Am 14.03.2018 um 19:33 schrieb Allin Cottrell:
>> On Wed, 14 Mar 2018, Sven Schreiber wrote:
>
>> I agree. This is a legacy thing -- accepting a column vector as if it were
>> a series. But since maxc and maxr are available f
On Wed, 14 Mar 2018, Sven Schreiber wrote:
> Am 14.03.2018 um 19:14 schrieb Allin Cottrell:
>> On Wed, 14 Mar 2018, Sven Schreiber wrote:
>
>>> eval max(deflist(1,2,3))
>>>
>>
>> Yes, should work according to the doc. This usage is an exception t
On Wed, 14 Mar 2018, Sven Schreiber wrote:
> Hi,
> shouldn't this work? Getting an unmatched data types or something error.
> thanks,
> sven
>
>
> nulldata 2
> series a = 10 # ID 2 (1 is index)
> series b = 11 # ID 3
>
> eval max(deflist(1,2,3))
>
Yes, should work according to the doc. This
On Wed, 14 Mar 2018, Sven Schreiber wrote:
> Hi,
> this is about string slicing, with snapshot March 9th:
>
>
> string sf = sprintf("123\n456")
> print sf # correct
> eval sf[1:7] # correct
>
> sf = sprintf("123\n456§")
> print sf # correct
> eval strlen(sf) # correct
> eval sf[1:8] #
On Tue, 13 Mar 2018, Sven Schreiber wrote:
> Am 13.03.2018 um 00:13 schrieb Summers, Peter:
>
>> If you mean being able to do something like (assuming m has been
>> defined)
>>
>>
>> rows(m)
>>
>> instead of
>>
>> r = rows(m)
>> r
>>
>
> Exactly.
Though of course you don't have to
Try
https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/
Or if you have a back-up of your local copy of po/zh_CN.po you could
1. make sure the back-up is somewhere safe, outside of the git po
directory
2. rm po/zh_CN.po && git checkout po/zh_CN.po
3. git pull
On Mon, 12 Mar 2018, Sven Schreiber wrote:
> Am 12.03.2018 um 17:50 schrieb Riccardo (Jack) Lucchetti:
>> On Mon, 12 Mar 2018, Allin Cottrell wrote:
>
>>>> (which can now be accomplished in git via instring(s1, s2)). As you say
>>>> the FEP GUI seems to be
On Mon, 12 Mar 2018, Allin Cottrell wrote:
> Ah, good, getting rid of strings-as-booleans shouldn't be too painful then.
> I've found lots of tests involving strstr in StrucBreak, cointARDL, PTconf,
> ADMBP, johansensmall, a_eff, margeff_el, FEP, waldTest and lagreg. But in
> almo
On Mon, 12 Mar 2018, Sven Schreiber wrote:
> Am 12.03.2018 um 16:44 schrieb Allin Cottrell:
>> On Mon, 12 Mar 2018, Sven Schreiber wrote:
>
>>>> Yes, I think that s the conclusion we’ve reached as well. And because
>>>> it was undocumented “if foo” will
On Mon, 12 Mar 2018, Sven Schreiber wrote:
>> Am 12.03.18 um 08:30 schrieb Riccardo (Jack) Lucchetti
>>
>> > I'm sorry I'm chiming in only at this stage, but I find the whole issue
>> > quite confusing. In my view, Hansl should not aim at being too clever with
>> > strings. There already are
On Sun, 11 Mar 2018, Sven Schreiber wrote:
> Am 11.03.18 um 15:42 schrieb Allin Cottrell
>
>> On Sun, 11 Mar 2018, Sven Schreiber wrote:
>
>> On checking the current code, I'm reminding myself that strlen()
>> does in fact count UTF-8 code points, so "a" and
On Sun, 11 Mar 2018, Sven Schreiber wrote:
> Am 11.03.2018 um 01:02 schrieb Allin Cottrell:
>> On Sat, 10 Mar 2018, Sven Schreiber wrote:
>
>>> Of course, for bundles, arrays, and matrix we have nelem(). I was also
>>> wondering why nelem() isn't working fo
On Sat, 10 Mar 2018, Sven Schreiber wrote:
> Am 09.03.2018 um 23:47 schrieb Allin Cottrell:
>
>> So I guess in the long run I'd be inclined to disallow using
>> strings as booleans in hansl,
>
> Yeah, let's clean that up and make it easy to understand by having
> c
On Fri, 9 Mar 2018, Sven Schreiber wrote:
> Am 08.03.2018 um 23:37 schrieb Allin Cottrell:
>> On Thu, 8 Mar 2018, Sven Schreiber wrote:
>>
>>> Am 08.03.2018 um 22:07 schrieb Allin Cottrell:
>
>>>> Actually I'm quite happy with the strstr() case,
>
>&
On Mon, 5 Mar 2018, oleg_komashko(a)ukr.net wrote:
> Dear all,
>
> If I do not a mistake, weekly and
> daily data as year:number (2017:40, etc)
> can not be saved to a .bin database
> There are several formats for weekly/daily data
> Is there any possibility to save weekly/daily data
> into
On Thu, 8 Mar 2018, Sven Schreiber wrote:
> Am 08.03.2018 um 22:07 schrieb Allin Cottrell:
>
>> Since a release is imminent I think it's better to go with fixing
>> up what we have, at least for now.
>
> Hm, or for the release maybe just leave things as they are, and
On Thu, 8 Mar 2018, Sven Schreiber wrote:
> Am 08.03.2018 um 20:04 schrieb Allin Cottrell:
>> On Thu, 8 Mar 2018, Sven Schreiber wrote:
>>
>>> Am 08.03.2018 um 10:23 schrieb oleg_komashko(a)ukr.net:
>
>>>> It looks like 'if' can evaluate non-empty st
On Thu, 8 Mar 2018, Sven Schreiber wrote:
> Am 08.03.2018 um 10:23 schrieb oleg_komashko(a)ukr.net:
>> It seems, there is nothing special
>> about strstr:
> ...
>> It looks like 'if' can evaluate non-empty string
>> alone as 1 but can't evaluate logical expressions
>> with string input
>
> OK,
On Tue, 6 Mar 2018, Henrique Andrade wrote:
> Em 6 de março de 2018, Jack escreveu:
>
> On Tue, 6 Mar 2018, Henrique Andrade wrote:
>>
>> Dear Allin and Jack,
>>>
>>> I think there is a little mistake in chapter 33 of the Gretl's User Guide.
>>> It states that x_t is a (k x 1) matrix on page 273
Thanks, Yi-Nung, I will try to see what's going wrong.
Allin
On Tue, 6 Mar 2018, yinung at Gmail wrote:
> Dear Allin
>
> I tested the Chinese (simplified) translation. It does not work. After some
> further testings, I found the grel.mo file under "locale/zh_CN/" has not
> been carried out with
Hello all,
Now that sourceforge seems to be in full swing again, my thoughts
are returning to the delayed 2018a release.
There are new snapshots in place today; I'd be grateful if people
could give them a go and check that nothing has gone badly wrong.
Since we've had a flurry of bug reports
On Sun, 4 Mar 2018, Sven Schreiber wrote:
> Am 04.03.2018 um 16:35 schrieb Allin Cottrell:
>> There's a function I wanted in the context of svm() -- to get all the keys
>> from a bundle in the form of an array of strings -- and I thought it might
>> be useful to have it e
On Fri, 2 Mar 2018, Sven Schreiber wrote:
> Am 02.03.2018 um 18:15 schrieb Allin Cottrell:
>> Not so long ago I tightened up on potential trampling of reserved words in
>> hansl, one effect being that you can no longer define a variable with the
>> same name as a built-in f
Not so long ago I tightened up on potential trampling of reserved
words in hansl, one effect being that you can no longer define a
variable with the same name as a built-in function.
I now notice that this provokes an error in the gig printout function,
which defines a scalar named "nobs". At
On Fri, 2 Mar 2018, Sven Schreiber wrote:
> Hi,
>
> when trying to package a gfn I got the following error message:
>
> Value "stringref" for attribute type of param is not among the enumerated set
>
> Indeed I have four helper functions that work on an arg like: string *s
> The functions work
On Fri, 2 Mar 2018, Sven Schreiber wrote:
> am I right in assuming that the following is supposed to work after a while
> ago arbitrary "element-of-nesting" was enabled?
>
>
> bundle b = null
> strings b.ss = defarray("a", "b")
> scalar b.a = 2
>
> eval b.ss[1] # works, "a"
> eval b["a"] #
On Sat, 24 Feb 2018, oleg_komashko(a)ukr.net wrote:
> ## this crushes gretl on my Ubuntu 17.10, 64
> open bjg.m
Ah, contrary to what I said earlier, I see we do have a special
import mechanism for .m files in place, from many years ago. I guess
it hasn't been used in a long time, because the
On Sat, 24 Feb 2018, oleg_komashko(a)ukr.net wrote:
> Dear all,
>
> Below is the script to illustrate the problem:
>
> run in 2 chunks
> open bjg.gdt
> store "bjg.m" --gnu-octave
> ma = mread("bjg.m")
> eval ma[1:3,]
> ## why only g?
bjg.m is not a gretl matrix file; it's an octave file
On Fri, 23 Feb 2018, Sven Schreiber wrote:
> If [vname] is already a variable, you can define a function with
> the same name, but then you cannot call it. Wouldn't it be better
> if gretl already complained when it encounters the function
> definition?
Agreed, and it now does complain, in
On Fri, 23 Feb 2018, Sven Schreiber wrote:
> Hi,
>
> another question on whether it's intended (or wise...) or not:
>
>
> clear
> for = 1 # works
> print for # prints out 1
>
> function void for(void) # gretl doesn't complain
> print "ouf"
> end function
>
> for() # error
On Sat, 24 Feb 2018, Artur Tarassow wrote:
> Am 24.02.2018 um 11:50 schrieb Sven Schreiber:
>> Am 24.02.2018 um 09:00 schrieb Artur Tarassow:
>>> Hi,
>>>
>>> I just tried to download the following document through gretl:
>>> Help-->"Command reference" (pdf)
>>> but the downloaded document is
On Fri, 23 Feb 2018, Sven Schreiber wrote:
> not sure if this is intended (probably), or just an oversight from
> 0-based to 1-based indexing:
>
> string ss = "abc"
> eval ss + 1 # gives "bc"
>
> The doc (ch. 14) says: " ...starting at the given character offset." Normally
> I would interpret
On Wed, 21 Feb 2018, Sven Schreiber wrote:
> Am 20.02.2018 um 17:11 schrieb Sven Schreiber:
>
>> So Allin had the great idea to enable binary-mode transfer between Python
>> and Gretl, and I tried it. [...]
One more follow-up on this. We should probably aim to extend the
binary matrix transfer
On Wed, 21 Feb 2018, Sven Schreiber wrote:
> Am 20.02.2018 um 17:11 schrieb Sven Schreiber:
>
>> So Allin had the great idea to enable binary-mode transfer between Python
>> and Gretl, and I tried it.
>
>> Python / Numba pure calculation
>> This took = 1.887286 sec.
>
>> Python / Numba with
On Wed, 21 Feb 2018, Artur T. wrote:
> Dear all,
>
> I just wanted to compile a fresh version of gretl but I've obtained the
> following error after "git pull"
>
>
> at(a)ati7:~/git/gretl-git$ git pull
> Aktualisiere 53f234b8a..74367f589
> error: Ihre lokalen Änderungen in den folgenden Dateien
On Wed, 21 Feb 2018, Sven Schreiber wrote:
> (on Windows) I did "show data" with two series selected. In the output window
> there's a copy button, followed by a window with option radio buttons.
> Choosing "simple text" works fine, but after choosing any other option
> (RTF/Tab/comma) I
On Wed, 21 Feb 2018, oleg_komashko(a)ukr.net wrote:
> when mle block fails to compute hessian it tries to compute opg
> arima fails in such situations one should input --opg by hand
Thanks for pointing this out.
The intended behavior of "arma" is that we fall back to OPG for the
covariance
On Wed, 21 Feb 2018, Riccardo (Jack) Lucchetti wrote:
> On Tue, 20 Feb 2018, Allin Cottrell wrote:
>
>> On Wed, 21 Feb 2018, oleg_komashko(a)ukr.net wrote:
>>
>>> It was on the previous message , greene5_1
>>
>> I'm going to press my point: your previous
On Wed, 21 Feb 2018, oleg_komashko(a)ukr.net wrote:
> It was on the previous message , greene5_1
I'm going to press my point: your previous message did _not_ refer
to any data file and so was equally incomprehensible. Please, if you
post hansl code that is supposed to be runnable, include a
On Tue, 20 Feb 2018, oleg_komashko(a)ukr.net wrote:
> Dear all,
>
> An example to reproduce
>
> function void arma11_via_kalman (series y)
> /* listing 33.1 with '--hessiaan' dropped */
> /* parameter initialization */
> scalar phi = 0
> scalar theta = 0
> scalar sigma = 1
> /* state-space model
On Wed, 21 Feb 2018, oleg_komashko(a)ukr.net wrote:
> The bug is very small, run
>
> ma = {0.1,0.1}
> set initvals ma
> catch arma 1 1; pop --nc --opg
>
> ma = {-0.9,-0.9}
> set initvals ma
> catch arma 1 1; pop --nc --opg
>
> ma = {0,0}
> set initvals ma
> catch arma 1 1; pop --nc
On Mon, 19 Feb 2018, Sven Schreiber wrote:
> Am 14.02.2018 um 02:03 schrieb Allin Cottrell:
>> Thanks go to Sven for persevering in testing the Windows build process; as
>> a result we've fixed several little glitches lately. So I'd encourage
>> anyone else who's in
On Tue, 20 Feb 2018, Sven Schreiber wrote:
> Am 19.02.2018 um 21:14 schrieb Allin Cottrell:
>
>> disk space, it will slow down the data transfer. In an effort to speed it
>> up I've also implemented support for binary-format matrices.
>
> I was able to test now, bu
I made a couple of mentions today of being unable to push changes in
my working copy of the gretl sources to sourceforge. I've now been
able to push, though I'm sure that everything is back to normal
there. The GUI git interface seems currently slow-to-unusable;
hopefully things will stabilize
On Sun, 18 Feb 2018, Sven Schreiber wrote:
> Am 17.02.2018 um 19:26 schrieb Sven Schreiber:
>
>> Instead I'd suggest to go back to numpy's savetxt, because it offers gzip
>> compression "for free", whenever a 'gz' extension is given.
>>
>> Does that sound like a good idea? I could send a
On Mon, 19 Feb 2018, Allin Cottrell wrote:
> On Mon, 19 Feb 2018, Sven Schreiber wrote:
>
>> this is with yesterday's snapshot, but it's probably a little older than
>> that. I think it's pretty severe, because it distorts data and is not
>> always obvious [...]
>
>
On Mon, 19 Feb 2018, Sven Schreiber wrote:
> this is with yesterday's snapshot, but it's probably a little older than
> that. I think it's pretty severe, because it distorts data and is not always
> obvious.
>
> To start with, run this code (in the GUI):
>
>
> open denmark
> smpl 1979:1 1985:4
On Sun, 18 Feb 2018, Sven Schreiber wrote:
> Am 16.02.2018 um 23:46 schrieb Sven Schreiber:
>> Am 16.02.2018 um 23:05 schrieb Allin Cottrell:
>
>>> fix in git now. The wait-loop in the console code was, as it now seems to
>>> me, an artifact associated with my att
On Fri, 16 Feb 2018, Riccardo (Jack) Lucchetti wrote:
> On Wed, 14 Feb 2018, Allin Cottrell wrote:
>
>> On Wed, 14 Feb 2018, Sven Schreiber wrote:
>>
>>> we have vaguely mentioned some slowness of (GUI) gretl, but we (or I)
>>> haven't been able to pin thi
On Wed, 14 Feb 2018, Sven Schreiber wrote:
> we have vaguely mentioned some slowness of (GUI) gretl, but we (or I) haven't
> been able to pin things down. Maybe I now have something reproducible (on
> Windows 7 here, latest snapshot):
>
> 1) start gretl
> 2) open a dataset (don't know whether
Thanks go to Sven for persevering in testing the Windows build
process; as a result we've fixed several little glitches lately. So
I'd encourage anyone else who's interested to have a go.
Documentation is at
http://ricardo.ecn.wfu.edu/pub/gretl/winbuild/
Besides fixing glitches, however,
On Tue, 13 Feb 2018, Sven Schreiber wrote:
> Am 13.02.2018 um 18:33 schrieb Allin Cottrell:
>> On Tue, 13 Feb 2018, Sven Schreiber wrote:
>
>>> catch scalar sc = sum(1) # error: "data types not matched"
>>> catch scalar sc = sum(djclose) # OK
>>>
On Tue, 13 Feb 2018, Sven Schreiber wrote:
> Hi, here's something that I find puzzling (snapshot Feb 7):
>
>
> clear
> catch eval sum(1) # error: "no dataset active"
> catch scalar sc = sum(1) # ditto
>
> open djclose.gdt
> catch eval sum(djclose) # OK
> catch eval sum(1) # weird printout of all
On Fri, 9 Feb 2018, Sven Schreiber wrote:
> Am 09.02.2018 um 14:48 schrieb Allin Cottrell:
> ...
>
> OK, so I have started over again (apart from the installed packages in
> mingw/msys, which I have left in place). The automatic setup now _almost_
> works, but I got an error a
Sorry, we've timed out for a 2018a release this week (I'm about to
head off for the weekend). Hopefully we should be able to get a
release out on Monday.
Allin
On Fri, 9 Feb 2018, Sven Schreiber wrote:
>
> Am 09.02.2018 um 14:06 schrieb Allin Cottrell:
>> On Fri, 9 Feb 2018, Sven Schreiber wrote:
>
>>>>> Warnung: libxslt-1.1.32-1 ist aktuell # meaning: ... is up to date
>>>>>
>>>>> Any hints
On Fri, 9 Feb 2018, Sven Schreiber wrote:
> Hm, I'm still having no luck. Perhaps it has to do that newly downloaded .sh
> files get a number extension and thus the correct files are not being
> executed. I will try to clean up everything and start more or less from
> scratch.
That behavior
On Fri, 9 Feb 2018, Sven Schreiber wrote:
> Am 09.02.2018 um 12:19 schrieb Riccardo (Jack) Lucchetti:
>> On Fri, 9 Feb 2018, Sven Schreiber wrote:
>
>>> The strange thing is that gretl's configure step reports this:
>>>
>>> checking for libxslt >= 1.0.15... no
>>>
>>> But when I try to install
On Wed, 7 Feb 2018, Sven Schreiber wrote:
> Am 05.02.2018 um 18:09 schrieb Allin Cottrell:
>> On Mon, 5 Feb 2018, Sven Schreiber wrote:
>
>>> Finally, if we could wait with the release for a few days such that the
>>> updated translations can be briefly tested
On Wed, 7 Feb 2018, Sven Schreiber wrote:
> Am 07.02.2018 um 11:58 schrieb Sven Schreiber:
>
>> However, configuring via the conf.sh mentioned in section 3.6, I got the
>> message that documentation couldn't be built because xslt and/or pdflatex
>> was missing.
>
> Perhaps I should add, I did
On Wed, 7 Feb 2018, Sven Schreiber wrote:
>> Am 30.12.2017 um 18:30 schrieb Sven Schreiber:
>>
>>> Then the setup.sh script said it was satisfied.
>
> Today I've tried a somewhat different attempt, invoking your (Allin's)
> automated setup.sh. (I think I followed a more manual approach the
On Mon, 5 Feb 2018, Sven Schreiber wrote:
> the doc for lrvar() says that a certain default is used when the second param
> is set to a negative value. Why not make the second param optional then (and
> treat it as -1 when it's omitted)?
OK, that's in git.
Allin
On Mon, 5 Feb 2018, Sven Schreiber wrote:
> Hi,
>
> I'm attaching the German translation update de.po. I don't have a read-write
> git checkout here right now, sorry, so could someone commit this for me?
> Thanks.
OK, that's now done.
> And a question: Is "Working directory tooltip" really a
On Mon, 5 Feb 2018, Allin Cottrell wrote:
> On Mon, 5 Feb 2018, Sven Schreiber wrote:
>
>> Hm, I've just tested current git (on Linux), and your example from this
>> thread now fails, gretl is saying that the parser doesn't recognize
>> 'rownames'. So the old na
On Mon, 5 Feb 2018, Sven Schreiber wrote:
> Am 03.02.2018 um 18:54 schrieb Allin Cottrell:
>> On Sat, 3 Feb 2018, Sven Schreiber wrote:
>>
>>> Am 03.02.2018 um 18:40 schrieb oleg_komashko(a)ukr.net:
>>>> Does it mean in all packages colnames() a
On Sun, 4 Feb 2018, Sven Schreiber wrote:
> Am 03.02.2018 um 15:41 schrieb Allin Cottrell:
>> On Sat, 3 Feb 2018, Riccardo (Jack) Lucchetti wrote:
>
>>>> On Sat, 3 Feb 2018, Sven Schreiber wrote:
>
>>>>> --and now also rowname-- *gets* the names, w
On Sat, 3 Feb 2018, Sven Schreiber wrote:
> Am 03.02.2018 um 18:40 schrieb oleg_komashko(a)ukr.net:
>> Does it mean in all packages colnames() and rownames()
>> should be renamed?
>
> No, I cannot imagine such a thing. Perhaps at some point in the future, but
> first any deprecated functions
On Sat, 3 Feb 2018, Riccardo (Jack) Lucchetti wrote:
> On Sat, 3 Feb 2018, Allin Cottrell wrote:
>
>> On Sat, 3 Feb 2018, Sven Schreiber wrote:
>>
>>> Am 03.02.2018 um 03:33 schrieb Allin Cottrell:
>>>> On Sat, 3 Feb 2018, oleg_komashko(a)ukr.net wrote:
&g
On Sat, 3 Feb 2018, Sven Schreiber wrote:
> Am 03.02.2018 um 03:33 schrieb Allin Cottrell:
>> On Sat, 3 Feb 2018, oleg_komashko(a)ukr.net wrote:
>
>>> Is there a less roundabout way to extract row names
>>> of a matrix
>>
>> OK, alright! By popular deman
On Sat, 3 Feb 2018, Sven Schreiber wrote:
> Am 03.02.2018 um 03:33 schrieb Allin Cottrell:
>> On Sat, 3 Feb 2018, oleg_komashko(a)ukr.net wrote:
>
>>> Is there a less roundabout way to extract row names
>>> of a matrix
>>
>> OK, alright! By popular deman
I think we've now accumulated enough bug fixes and refinements to
make it worth hoisting 2017e out of limbo as release 2018a.
http://gretl.sourceforge.net/ChangeLog.html
Are there any issues that people would really like to see addressed
before we do that?
Allin
On Sat, 3 Feb 2018, oleg_komashko(a)ukr.net wrote:
> function string get_rnames(matrix M)
> string s = sprintf("%d",M)
> nss = nlines(s)
> string line
> scalar i = 1
> strings S = array(nss)
> loop while getline(s, line) -q
> S[i]= sprintf("%s", line)
> i++
>
On Thu, 1 Feb 2018, Sven Schreiber wrote:
> Hi,
> some colleagues have suggested that it would be useful if the help (plain
> text or pdf) of the many contributed function packages were also available on
> the web. That way it would also be found by search engines.
>
> I think the most natural
I've just realized that the Windows snapshots put in place over the
last couple of days are problematic, in particular the 64-bit version,
with potential crashes on start-up in debugging mode, and in
initializing R support. Sorry about that!
I think these things are now fixed in the very latest
On Fri, 26 Jan 2018, Artur Tarassow wrote:
>> Here's a somewhat more minimal version of your test case:
>> >
>> >
>> > foreign language=R
>> > rm(list=ls(all=T))
>> > ma<-matrix(c(-0.25,0,1.2,0,0,0.5),nr=3,byrow=T)
>> > ma
>> > gretl.export(ma)
>> > end foreign
>> >
>> > matrix
On Thu, 25 Jan 2018, Sven Schreiber wrote:
> in git I see that a new function linesplit() is coming: "Returns an array of
> strings, one per line in the argument"
>
> Could this get a second optional argument that would override the newline
> character for splitting?
In a word, no: linesplit
On Wed, 24 Jan 2018, Summers, Peter wrote:
>> Footnote on Rlib use from gretl. How do you call an R function from within
>> gretl if that function requires a library that's not loaded by default?
>>
> ... version with R wrapper function
>>
>>
>> foreign language=R --quiet
>> skewness_R <-
On Thu, 25 Jan 2018, Artur Tarassow wrote:
> Please find attached a minimal test case (tested on latest git on ubuntu
> 17.10). In this example I just call R via the foreign-block and want to
> export some matrix. The error I obtain is
> "Error in gretl.export(ma) : could not find function
On Wed, 24 Jan 2018, Sven Schreiber wrote:
> Hi,
> example:
>
>
> function void checkp(matrix *hey[null])
> print "yo"
> end function
>
> bundle b = null
> matrix b.man = {}
>
> checkp()
>
>
> gives a funny error with BMEMB being not allowed.
It may be funny (the message could be improved),
On Wed, 24 Jan 2018, Riccardo (Jack) Lucchetti wrote:
> I tried to reproduce [Artur's] problem here on Debian (and I spent
> quite a long time wondering what was wrong with your example before
> I realised I hadn't the "moments" R library installed. Oh well).
Footnote on Rlib use from gretl.
On Wed, 24 Jan 2018, Artur T. wrote:
> Let's take [Allin's] example for the moment (see below).
>
>>
>> nulldata 100
>> set verbose off
>> set R_functions on
>>
>> foreign language=R --quiet
>> moments_R <- function(x) {
>> library(moments)
>> s <- skewness(x)
>> k <- kurtosis(x)
, or to all,
> observations in a X-Y scatter plot, but I do not see how to do the
> same with X-Y with control.
That's not enabled at present but it could be -- not too difficult, I
think.
For future reference this sort of question is more suitable for the
gretl-users list than for gretl-devel.
Allin Cottrell
On Tue, 23 Jan 2018, Artur Tarassow wrote:
> Dear all,
>
> I am facing the following problem. I am calling via the foreign-environment
> R-code from inside gretl/hansl, compute some matrices and use the
> gretl.export() function to export these matrices. This works fine even though
> the
On Thu, 18 Jan 2018, Sven Schreiber wrote:
> Hi,
>
> I observe the following problem (also with today's snapshot). Right now I
> don't have the time to try to create a minimal-example script, but I can
> follow up on that. And perhaps the verbal explanation already helps.
>
> In a quarterly
Thanks to Sven for getting me going on this. The "join" command now
supports the "spreading" of high-frequency series (as wanted by our
MIDAS apparatus) in a single operation. This requires use of the
--aggr option with parameter "spread". There are two acceptable
forms of usage, illustrated
On Tue, 16 Jan 2018, Sven Schreiber wrote:
> Am 16.01.2018 um 17:33 schrieb Allin Cottrell:
>
>> It seems that daily series in gretl databases was an idea that was only
>> partially implemented and then never really developed. In today's git and
>> snapshots there are so
On Mon, 15 Jan 2018, Sven Schreiber wrote:
> About databases:
>
>> Hmm, not sure. I think that daily series (at least) are supposed to be
>> supported in gretl databases. [Allin]
>
> Yes as per appendix A.3 of the guide. (Weekly isn't mentioned there.)
>
>> But I can't remember if there's any
On Mon, 15 Jan 2018, Marcin Błażejowski wrote:
> why this code:
>
> set echo off
> mpi
> matrix FOO
> if $mpirank == 0
> FOO = ones(3,1)
> endif
> mpibcast()
> eval $mpirank * FOO
> end mpi
>
> in most cases produces an error? (MPI_ABORT was invoked on rank...)
I
On Mon, 15 Jan 2018, Marcin Błażejowski wrote:
> Hi,
>
> why this code:
>
> set echo off
> mpi
> matrix FOO
> if $mpirank == 0
> FOO = ones(3,1)
> endif
> mpibcast()
> eval $mpirank * FOO
> end mpi
>
> in most cases produces an error? (MPI_ABORT was invoked on
On Sun, 14 Jan 2018, Sven Schreiber wrote:
> Am 12.01.2018 um 21:21 schrieb Allin Cottrell:
>
>> In addition, however, join works pretty nicely without the help of a
>> temporary datafile, provided the high-frequency data start in the first
>> sub-period
>
>>
On Fri, 12 Jan 2018, Sven Schreiber wrote:
> Am 11.01.2018 um 22:44 schrieb Allin Cottrell:
>> On Thu, 11 Jan 2018, Riccardo (Jack) Lucchetti wrote:
>>> On Thu, 11 Jan 2018, Sven Schreiber wrote:
>
>>>> or perhaps the 'append' command is better suited than join
On Thu, 11 Jan 2018, Riccardo (Jack) Lucchetti wrote:
> On Thu, 11 Jan 2018, Sven Schreiber wrote:
>
>> Hi,
>>
>> I will be working with Midas in gretl again soon, and I've just reread (or
>> let's say, re-browsed) the midas_gretl.pdf guide.
>> Looking at the section "importation via join", it
On Wed, 10 Jan 2018, Schaff, Frederik wrote:
> it would be nice if the script editor would provide in its header
> the name of the gretl instance it belongs to. I sometimes have
> multiple instances open... The same accounts for other gretl
> windows, I guess.
Feasible, I guess, but it would
On Tue, 9 Jan 2018, Schaff, Frederik wrote:
>> But one (somewhat relevant) point is that it's now OK (in recent
>> git) to skip one or more optional arguments altogether, provided
>> one inserts commas to preserve the argument count where
>> necessary. (Commas are not required if only trailing
On Mon, 8 Jan 2018, Sven Schreiber wrote:
> Am 08.01.2018 um 10:21 schrieb Schaff, Frederik:
>>
>> Hi there, I pose this question & suggestion here instead the
>> users list, I hope that is fine in this context.
>
> Yes, perfect.
>>
>> It is currently not possible to use „null“ as a default
1001 - 1100 of 3780 matches
Mail list logo
