#144: implement solve_algo=0 for Octave
--------------------------+-------------------------------------------------
Reporter: sebastien | Owner: sebastien
Type: feature | Status: new
Priority: major | Milestone: 4.2
Component: Core M-files | Version:
Keywords: |
--------------------------+-------------------------------------------------
fsolve() has a slightly different syntax under Octave
Need to adapt dynare_solve.m
--
Ticket URL: <https://www.dynare.org/trac/ticket/144>
Dynare <http://www.dynare.org>
The Dynare project
#11: Allow for the possibility of using the bytecode representation of the model
for any task
---------------------------+------------------------------------------------
Reporter: sebastien | Owner: ferhat
Type: enhancement | Status: reopened
Priority: major | Milestone: 4.2
Component: Preprocessor | Version:
Resolution: | Keywords:
---------------------------+------------------------------------------------
Comment(by sebastien):
Replying to [comment:7 sebastien]:
> Crashes in testsuite fixed as of
1aceb504fdd722c26697113be48ee541d9e09556
No, the crash is still here.
--
Ticket URL: <https://www.dynare.org/trac/ticket/11#comment:8>
Dynare <http://www.dynare.org>
The Dynare project
#130: Console mode
--------------------------+-------------------------------------------------
Reporter: stepan | Owner: sebastien
Type: feature | Status: new
Priority: major | Milestone: 4.2
Component: Preprocessor | Version:
Keywords: |
--------------------------+-------------------------------------------------
Add an option to the dynare command for the console mode. This option may
be called "console", "terminal" or "term", if used options_.console_mode
would be set to 1 and graphical waitbars are replaced by text waitbars.
The matlab code is ready (ie one can write options_.console_mode=1; in the
mod file before the estimation command), Sébastien only needs to add
something in the preprocessor.
--
Ticket URL: <https://www.dynare.org/trac/ticket/130>
Dynare <http://www.dynare.org>
The Dynare project
#11: Allow for the possibility of using the bytecode representation of the model
for any task
---------------------------+------------------------------------------------
Reporter: sebastien | Owner: ferhat
Type: enhancement | Status: reopened
Priority: major | Milestone: 4.2
Component: Preprocessor | Version:
Resolution: | Keywords:
---------------------------+------------------------------------------------
Comment(by sebastien):
Crashes in testsuite fixed as of 1aceb504fdd722c26697113be48ee541d9e09556
--
Ticket URL: <https://www.dynare.org/trac/ticket/11#comment:7>
Dynare <http://www.dynare.org>
The Dynare project
#11: Allow for the possibility of using the bytecode representation of the model
for any task
---------------------------+------------------------------------------------
Reporter: sebastien | Owner: ferhat
Type: enhancement | Status: reopened
Priority: major | Milestone: 4.2
Component: Preprocessor | Version:
Resolution: | Keywords:
---------------------------+------------------------------------------------
Comment(by sebastien):
Replying to [comment:5 sebastien]:
> - As of 5f0dac24bf0e7b65fdc43e21a5dc7eeb1ae92776, the test file
block_bytecode/ls2003.mod crashes under Octave
Fixed in 39718c86456246f0950080201e6ca910f47ba176
> - We should probably swap values 5 and 8 for solve_algo, for consistency
with Dynare 4.1
Fixed in 39718c86456246f0950080201e6ca910f47ba176
> - The new values for stack_solve_algo and solve_algo (in combination
with block/bytecode) need to be documented on the wiki and in the
reference manual (on the wiki, we should keep separate sections on Dynare
4.1 and Dynare 4.2)
Fixed in reference manual in 55c6089deb3873f5fdcb0874db076aac569b288c
Remains to be done:
- update wiki pages
- fix crash in new testsuite
--
Ticket URL: <https://www.dynare.org/trac/ticket/11#comment:6>
Dynare <http://www.dynare.org>
The Dynare project
#21: Add partial information
---------------------------+------------------------------------------------
Reporter: sebastien | Owner: george
Type: feature | Status: accepted
Priority: major | Milestone: 4.2
Component: Core M-files | Version:
Resolution: | Keywords:
---------------------------+------------------------------------------------
Comment(by sebastien):
I added qzcomplex Oct-file in 69fc0e320bab92ab423631168af4f40c1b038d86.
I decided to rewrite it from scratch, instead of re-using the one
distributed by Sims, because Sims did not write it. He is not completely
sure about who did. And it was a good opportunity to learn how to write
Oct-files.
The partial information routines now give the same result under MATLAB and
Octave.
--
Ticket URL: <https://www.dynare.org/trac/ticket/21#comment:8>
Dynare <http://www.dynare.org>
The Dynare project
Hi George,
George Perendia <george(a)perendia.orangehome.co.uk> writes:
> we explored alternative paths and it looks like we need to add a
> complex QZ on lines of the Matlab to Octave.
If I understand correctly, you need a complex QZ decomposition at line
156 of partial_information/PI_gensys.m, where you call the qz()
primitive (and only there).
Note for other developers: the qz() primitive under Octave delivers only
the *real* generalized Schur decomposition.
> C Sims' site provides such wrapper for octave version of gensys.m
> based on Lapack zgges.f:
> http://sims.princeton.edu/yftp/gensys/Octave/
>
> but that is using Octave specific mkoctfile compilation and octave specific .c interface.
>
> Considering we are not using mkoctfile, and it may not be acceptable
> within Dynare, would it be ok if we take up an alternative path to
> rewrite mjdgges.c as an additional qzzges.c (laving mjdgges as is of
> course) that returns complex on the same lines as Matalb qz() does,
> and add it to the e.g. qz subdirectory where mjdgges currenlty resides
> (though the zdgges.f still needs to be tested if it does the right
> trick but this would be the way to test it too)?
I think that the easiest way to go is to incorporate Sims' qzcomplex
oct-file into Dynare, provided that Sims agrees on putting it under the
GPL (which should probably not be a problem).
The fact that this uses mkoctfile is not a problem: it is possible to
emulate this command with the build system as we did for the mex
command.
The fact that it uses Octave specific Oct-interface is not a problem: we
can build this DLL only for Octave (and therefore with a ".oct"
extension), since it is useless under MATLAB.
And of course we would put it under mex/octave.
I agree with you that this will force users to have compiled DLLs in
order to use your code, but there are already many other features of
Dynare in that case (k-order, bytecode...).
If you agree with that line of work, I will contact Sims to ask for
permission of including his code under the GPL into Dynare, and then I
will make the necessary changes to the build system.
Best,
--
Sébastien Villemot
CEPREMAP — http://www.cepremap.ens.fr
Dynare project — http://www.dynare.org
Phone: +33 1 40 77 49 90
PGP Key: 0xA6C029B9D06B2913D71C105EBE37E801FB6EFF8B (http://pgp.mit.edu/)