> I don't know if this is a high enough priority to try fixing
before
> then, but I've had an issue executing a Julia script from within
> gretl.
[...]
<Allin>
(But it turned out that the issue was just that the Julia program didn't call for any
output.)
[...]
A brief follow-up, since I realize this could be a bit confusing.
When you execute third-party code via gretl's "foreign" block apparatus, by
default (without the --quiet flag) we give the user some notice of how things are going.
But if you execute a "foreign"
script directly via the gretl GUI, we just show you exactly the visible output produced by
the foreign program -- which might be nothing at all (as in this case) if no print
statements are included.
</Allin>
Thanks for the clarification, it works as expected now (ie, using "print(2+2)"
instead of just "2+2").
<Allin>
Perhaps, if we detect no error condition but get no output, we should put a statement into
the output window instead of leaving it empty -- something like
"Executed sucessfully, no visible output produced"
</Allin>
That seems useful to me.
<Allin>
Second point: our Julia support seems OK to me, but right now it's a bit lacking in
motivation since nobody has yet come up with an example where it's actually useful to
pass some task to Julia for execution. If anyone's able to come up with such an
example I'll be glad to put it into the gretl doc on Julia interaction.
</Allin>
My goal with all of this is to experiment with some Bayesian MCMC stuff using (Julia-)
Stan (
mc-stan.org). I'm happy to play in that sandbox for a bit and report back on
what I find out.
Thanks again!
PS