
Hello everyone,
I was trying to solve the steady state for the simple_SPBC example model using steady state files. When I compile the steady state object into the standalone mfile function, the command creates growth rates variables (like dA) for all variables that appear
with lags and/or leads. Is it possible to solve the steady state without having to declare these additional variables (with their corresponding equations and steady state equations ) ?
If I have a model that is is stationary form (but still has equations with lags and leads), is it possible to specify this in the sstatefile command (I don't want to write for each equation its steady state version) ?
Many thanks,
Cristian



Hi Cristian
I will look into this issues next week when back from my vacation. Could you please post the files in the meantime? It just helps to see what exactly you mean.
Best






Cristian
Before I dive into the issue, may I ask you first why you need a standalone steadystate file? This feature was designed a long while ago when the function sstate(...) itself was not that powerful, and the standalone steadystate files are now not considered
a standard way of doing things...
Is there a particular task that you, for some reason, cannot achieve (or a performence issue you bump into) when simply calling sstate(m,...)?
Jaromir



Hi Jaromir,
I am having problems when computing the steady state of a model originally written in Dynare and the standalone seemed to have the advantage of being less black box; however, I thought about it more and I think it has something to do with endogenising parameters
/ exogenising ss values. I will look into it more. If you say the standalone files are not considered a standard way anymore and sstate(...) is powerful enough ... I trust you :). Apart from writing the ss version of the equations and using the 'blocks' option,
what other tricks would you say I should use (generally speaking) ? Thanks again for your interest.
Best,
Cristian



A few tips:
 Make sure you use the option 'growth=' in models where there are nonzero deterministic growth rates.
 You can do the endogenise/exogenise swap using the options 'exogenise=' and 'endogenise='.
 Sometimes it helps to preassign and fix the known steadystate values using 'fix=', 'fixLevel=', and/or 'fixGrowth=' (i.e. for variables that have a trivial steady state, etc.)
 A similar thing can be achieved by using dynamic links. You can e.g link one variable's steady state to an expression involving parameters and other variables' steady states. This is defined in the model file in a section called !links.
 Furthermore, sometimes also helps to deliver initial values, especially for variables whose steady state is a (very) large or a small number  for instance, the stock of physical capital in the common variety of dsge models.
 In more complex cases, you can split the model file manually into blockrecursive files (blockrecursive in terms of steady state equations), and compute the steady state for each block separately, using the steadystate results from the previous block
as parameters entering the next block. For this, you will need to make use of the options 'declareParameters=' and 'sstateOnly='. I can prepare an example if you want to experiment with this. Afterwards, you simply combine all the model files in one (enter
a cell array of file names as the first input argument into the function model(...)) to build the final model object.
We can also look into that particular model from Dynare, and help you get it up and running.
Best,
Jaromir

