Hi Sébastien,
I dont know if you were able to find the source of my last runtime error. Here is a similar case you should take a look at:
http://www.dynare.org/phpBB3/viewtopic.php?f=1 http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=4066 &t=4066
Dynare 4.2.5 still reports that there are 5 endogenous variables and 4 equations while 4.3 and the snapshot crash with the following output:
Configuring Dynare ...
[mex] Generalized QZ.
[mex] Sylvester equation solution.
[mex] Kronecker products.
[mex] Sparse kronecker products.
[mex] Local state space iteration (second order).
[mex] Bytecode evaluation.
[mex] k-order perturbation solver.
[mex] k-order solution simulation.
[mex] Quasi Monte-Carlo sequence (Sobol).
[mex] Markov Switching SBVAR.
Starting Dynare (version 2012-09-17).
Starting preprocessing of the model file ...
Found 4 equation(s).
Evaluating expressions...done
Computing static model derivatives:
- order 1
Computing dynamic model derivatives:
- order 1
- order 2
Computing static model derivatives:
- order 1
- order 2
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Processing outputs ...terminate called after throwing an instance of 'SymbolTable::UnknownTypeSpecificIDException'
--
Johannes Pfeifer
Haußerstr. 29
72076 Tübingen
Tel.: +49-(0)7071-6396184
Mobil.: +49-(0)170-6936820
Germany
"Johannes Pfeifer " jpfeifer@gmx.de writes:
I don’t know if you were able to find the source of my last runtime error.
No, unfortunately.
Here is a similar case you should take a look at:
See my answer in that post. I can't replicate the crash. Which version of Windows are you using? I guess I will have to install a Windows 7 in a VM…
I am using Windows 7 64bit.
It may be normal to have less equations with Ramsey. But something must be wrong with the mod-file. Dynare 4.2.5 complains
Configuring Dynare ... [mex] Generalized QZ. [mex] Sylvester equation solution. [mex] Kronecker products. [mex] Sparse kronecker products. [mex] Bytecode evaluation. [mex] k-order perturbation solver. [mex] k-order solution simulation.
Starting Dynare (version 4.2.5). Starting preprocessing of the model file ... ERROR: There are 4 equations but 5 endogenous variables!
Error using dynare (line 114) DYNARE: preprocessing failed
And Dynare 4.3 crashes with the error message I sent you yesterday.
What does Dynare 4.3 say on your machine?
-- Johannes Pfeifer Haußerstr. 29 72076 Tübingen Tel.: +49-(0)7071-6396184 Mobil.: +49-(0)170-6936820 Germany
-----Ursprüngliche Nachricht----- Von: dev-bounces@dynare.org [mailto:dev-bounces@dynare.org] Im Auftrag von Sébastien Villemot Gesendet: Dienstag, 18. September 2012 11:09 An: List for Dynare developers Betreff: Re: [DynareDev] Runtime error
"Johannes Pfeifer " jpfeifer@gmx.de writes:
I don’t know if you were able to find the source of my last runtime error.
No, unfortunately.
Here is a similar case you should take a look at:
See my answer in that post. I can't replicate the crash. Which version of Windows are you using? I guess I will have to install a Windows 7 in a VM…
-- Sébastien Villemot Researcher in Economics http://www.dynare.org/sebastien Phone: +33-1-40-77-84-04
"Johannes Pfeifer " jpfeifer@gmx.de writes:
I am using Windows 7 64bit.
It may be normal to have less equations with Ramsey. But something must be wrong with the mod-file. Dynare 4.2.5 complains
We changed a lot of things in the optimal policy engine between 4.2 and 4.3, so I am not sure the MOD file is wrong. It may just be trying to do things that were not implemented in 4.2.
What does Dynare 4.3 say on your machine?
It seems to work fine and creates a meaningful output.
Sébastien Villemot sebastien.villemot@ens.fr writes:
"Johannes Pfeifer " jpfeifer@gmx.de writes:
It may be normal to have less equations with Ramsey. But something must be wrong with the mod-file. Dynare 4.2.5 complains
We changed a lot of things in the optimal policy engine between 4.2 and 4.3, so I am not sure the MOD file is wrong. It may just be trying to do things that were not implemented in 4.2.
Yes indeed it is using discretionary_policy which was nonexistent in 4.2. Hence the error message with 4.2.5