dynare issueshttps://git.dynare.org/Dynare/dynare/-/issues2013-05-30T13:36:10Zhttps://git.dynare.org/Dynare/dynare/-/issues/367parallel preprocessor for hybrid clusters2013-05-30T13:36:10ZMarco Rattoparallel preprocessor for hybrid clustersCurrently the pre-processor does not allow to define unix nodes from a windows master, without entering dummy entries for the drive and password fields, which could be empty for the unix machine.
I would suggest that the pre-processor ...Currently the pre-processor does not allow to define unix nodes from a windows master, without entering dummy entries for the drive and password fields, which could be empty for the unix machine.
I would suggest that the pre-processor checks for the field OperatingSystem and issue the error only
if OperatingSistem= windows
or
if OperatingSistem is empty and we are in windows environment (master is windows)
thanks
4.4Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/308add reporting routines for creating PDF reports2013-05-30T13:46:36ZSébastien Villemotadd reporting routines for creating PDF reports4.4Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/389parallel option for user defined files needed by the DYNARE project2013-05-31T13:09:43ZMarco Rattoparallel option for user defined files needed by the DYNARE projectWe should allow users to declare non standard files needed to run the projects, e.g. subroutines possibly called within the _steadystate file.
In these cases, remote threads crash since the steady state cannot be run (only threads run lo...We should allow users to declare non standard files needed to run the projects, e.g. subroutines possibly called within the _steadystate file.
In these cases, remote threads crash since the steady state cannot be run (only threads run locally would work).
I have already written a fix to this in masterParallel.m which uses a new field local_files of parallel_info
options_.parallel_info.local_files
we need an interface to fill this field.
We have some options:
1)use the configuration file, but I do not think this would be a great idea since those cases are specific for individual dynare projects and not for general configurations of dynare.
2) use a new option local_files of the dynare command, triggered as follows, assuming a dynare project called mymodel.mod, where the files file1.m, file2.mat, myfolder/file3.txt in the project directory are needed by, e.g., the steady state file:
dynare mymodel parallel local_files=(file1.m)
this would trigger the following entry in options_.parallel_info:
options_.parallel_info.local_files = {'', 'file1.m'};
where the empty element indicates that the file is in the project directory and not in a subdirectory.
Another example:
dynare mymodel parallel local_files=(file1.m, file2.mat, myfolder/file3.txt)
this would trigger the following entry in options_.parallel_info (we need to parse and separate the subfolder from the name of the file)
options_.parallel_info.local_files = {
'', 'file1.m';
'', 'file2.mat';
'myfolder/', 'file3.txt'
};
3) use the option local_files inside, e.g., the estimation command:
estimation(datafile=mydata,mode_compute=0, ..., local_files=(file1.m, file2.mat, myfolder/file3.txt))
which would trigger in the same way the entry in options_.parallel_info.local_files
Which option would be best for you?
4.4Marco RattoMarco Rattohttps://git.dynare.org/Dynare/dynare/-/issues/362Add an option for making the stochastic draws truly pseudo-random (for exampl...2013-05-31T14:36:00ZSébastien VillemotAdd an option for making the stochastic draws truly pseudo-random (for example setting the seed with the clock)4.4Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/342Better documentation of parser error messages (line and column numbers)2013-05-31T17:28:42ZJohannes PfeiferBetter documentation of parser error messages (line and column numbers)Currently, we have error messages like this:
`ERROR: final.mod:201.1-3: syntax error, unexpected NAME`
The reason usually is that a semicolon is missing in the previous line, but people only look in the current line. If the error starts...Currently, we have error messages like this:
`ERROR: final.mod:201.1-3: syntax error, unexpected NAME`
The reason usually is that a semicolon is missing in the previous line, but people only look in the current line. If the error starts at 1, we might want to change the error message to
`ERROR: final.mod:201.1-3: syntax error, unexpected NAME. Please also check whether the previous line was terminated correctly with a semicolon.`
Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/259Shock decomposition on calibrated models fails2013-06-03T14:47:59ZSébastien VillemotShock decomposition on calibrated models failsThe bayestopt_ structure is uninitialized.
The bayestopt_ structure is uninitialized.
4.4MichelJuillardMichelJuillardhttps://git.dynare.org/Dynare/dynare/-/issues/303Improve Forecast Documentation2013-06-10T08:01:58ZJohannes PfeiferImprove Forecast DocumentationJudging from the number of questions relating to forecasting, the documentation is insufficient. In particular, the recursive forecasting option and the fields it creates (e.g. oo_.RecursiveForecast) are undocumented.
Judging from the number of questions relating to forecasting, the documentation is insufficient. In particular, the recursive forecasting option and the fields it creates (e.g. oo_.RecursiveForecast) are undocumented.
4.4https://git.dynare.org/Dynare/dynare/-/issues/152Stochastic Extended path2013-06-10T12:35:45ZSébastien VillemotStochastic Extended pathSome code already exists, it is mainly a matter of creating an interface.
Some code already exists, it is mainly a matter of creating an interface.
4.4Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/351Transformation of variables for imposing terminal condition in terms of growt...2013-06-12T15:57:48ZSébastien VillemotTransformation of variables for imposing terminal condition in terms of growth ratesThe object of the task will be to define a new option for the Dynare preprocessor for deterministic simulations. The convergence of deterministic simulations is sometimes hindered by sub-optimal use of terminal conditions. Especially for...The object of the task will be to define a new option for the Dynare preprocessor for deterministic simulations. The convergence of deterministic simulations is sometimes hindered by sub-optimal use of terminal conditions. Especially for level variables and Lagrange multipliers, bad values for terminal conditions in the case of very persistent dynamics or permanent shocks can hinder correct solutions or any convergence. To this end, it will be useful to consider an option for the Dynare preprocessor that defines auxiliary forward looking variables expressed in first differences or growth rates of the actual forward looking variables defined in the model. These new variables have obvious zero terminal conditions whatever the simulation context and this in many cases helps convergence of simulations. Allowing the preprocessor to automatically define these auxiliary variables would avoid modelers to modify/edit the model for simulation purposes.
The specific objectives for the deliverables will be:
1. define the specifications and preprocessor options that trigger the definition of auxiliary forward looking variables with zero terminal conditions;
2. the default behavior of this new option will be to transform all forward looking variables in the model: a further option will be to allow the modeler to explicitly define the list of variables to be transformed. This may be useful in the case some forward looking variables in the model (like inflation in Phillips curve) have already the trivial zero terminal condition, thus reducing the number of new variables defined by the preprocessor (namely only Lagrange multipliers and level variables).
4.4Sébastien VillemotSébastien Villemothttps://git.dynare.org/Dynare/dynare/-/issues/348Add the possibility to instantiate dynSeries objects from an xls file.2013-09-11T15:26:00ZStéphane Adjemianstepan@adjemian.euAdd the possibility to instantiate dynSeries objects from an xls file.This feature is necessary to replace all the existing code related to the datasets by the dynSeries class.
This feature is necessary to replace all the existing code related to the datasets by the dynSeries class.
Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/313shock decomposition crashes after an estimation restricted to some endogenous...2013-09-18T10:05:38ZSébastien Villemotshock decomposition crashes after an estimation restricted to some endogenous variablesThe following code crashes:
```
estimation(...) y W R;
shock_decomposition y W R;
```
This is because the `shock_decomposition` command makes the assumption that all endogenous have their smoothed values in `oo_.SmoothedVariables`.
Th...The following code crashes:
```
estimation(...) y W R;
shock_decomposition y W R;
```
This is because the `shock_decomposition` command makes the assumption that all endogenous have their smoothed values in `oo_.SmoothedVariables`.
This should be fixed either by giving a more explicit error message or, better, by doing the right thing™.
4.4MichelJuillardMichelJuillardhttps://git.dynare.org/Dynare/dynare/-/issues/195histval+stoch_simul2013-09-30T09:24:22ZSébastien Villemothistval+stoch_simulContrary to what is explained in the documentation, the stochastic simulations are systematically initialized at the deterministic steady state. The histval block does not affect the way the simulations are initialized, and, worse, the p...Contrary to what is explained in the documentation, the stochastic simulations are systematically initialized at the deterministic steady state. The histval block does not affect the way the simulations are initialized, and, worse, the preprocessor crashes if option periods is used (with an error message).
The error message should be removed and the preprocessor should define a flag (options_.histval=1) whenever the block histval is used.
4.3https://git.dynare.org/Dynare/dynare/-/issues/131histval is broken in models with lag > 12013-09-30T09:24:22ZSébastien Villemothistval is broken in models with lag > 1initialization doesn't take auxiliary variables into account
initial matrix has wrong dimension
initialization doesn't take auxiliary variables into account
initial matrix has wrong dimension
4.2https://git.dynare.org/Dynare/dynare/-/issues/112Metropolis: add the possibility for the user to give an arbitrary matrix for ...2013-11-05T16:17:59ZSébastien VillemotMetropolis: add the possibility for the user to give an arbitrary matrix for the variance of the jump proposalFeature suggested by Fabio Canova at the Dynare Conference 2010.
Feature suggested by Fabio Canova at the Dynare Conference 2010.
https://git.dynare.org/Dynare/dynare/-/issues/302dynSeries: enable excel files to be read in2013-11-12T09:14:03ZSébastien VillemotdynSeries: enable excel files to be read increate load_xls_file_data.m like load_csv_file_data.m
create load_xls_file_data.m like load_csv_file_data.m
4.5Houtan BastaniHoutan Bastanihttps://git.dynare.org/Dynare/dynare/-/issues/361Document the fact that MCMC is deterministic and what are the possible conseq...2013-12-04T09:12:12ZSébastien VillemotDocument the fact that MCMC is deterministic and what are the possible consequences of thatSee the discussion in #85
See the discussion in #85
4.4Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/182Document DSGE-VAR in the ref manual2013-12-04T14:23:30ZSébastien VillemotDocument DSGE-VAR in the ref manual4.4Stéphane Adjemianstepan@adjemian.euStéphane Adjemianstepan@adjemian.euhttps://git.dynare.org/Dynare/dynare/-/issues/166fix computation of the planner objective under Ramsey policy2013-12-13T09:55:28ZSébastien Villemotfix computation of the planner objective under Ramsey policyThe call to "evaluate_planner_objective" was commented out in f36247ceedb73ebab6be0bbc736fc6f5ce3f3bb1.
The call to "evaluate_planner_objective" was commented out in f36247ceedb73ebab6be0bbc736fc6f5ce3f3bb1.
4.5MichelJuillardMichelJuillardhttps://git.dynare.org/Dynare/dynare/-/issues/87fix order of integration in univariate filter/smoother2014-01-22T13:21:56ZSébastien Villemotfix order of integration in univariate filter/smoother4.2https://git.dynare.org/Dynare/dynare/-/issues/142Integrate ACES Linear Quadratic approximation toolbox2014-01-28T15:12:00ZSébastien VillemotIntegrate ACES Linear Quadratic approximation toolboxAnalysis is on:
http://www.dynare.org/DynareWiki/AcesLqImplementationRequirements
Analysis is on:
http://www.dynare.org/DynareWiki/AcesLqImplementationRequirements