Dev

dev@dynare.org

3402 discussions

Status of testsuite in 4.4 branch
by sebastien＠dynare.org 02 Feb '14

02 Feb '14

28054c46dc2f379a502a7c9f82d4d897f4513b48 removed useless test with exist() that is very expensive in Octave (but apparently not in Matlab) ================================ DYNARE MAKE CHECK MATLAB RESULTS ================================ | TOTAL: 417 | PASS: 415 | FAIL: 0 | XFAIL: 2 | XPASS: 0 ================================ DYNARE MAKE CHECK OCTAVE RESULTS ================================ | TOTAL: 415 | PASS: 413 | FAIL: 0 | XFAIL: 2 | XPASS: 0 A full log can be found on karaba in '/tmp/dynare-4.4-check-J9B5bzzclt.log'.

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 02 Feb '14

02 Feb '14

c1e0d68351527153960a988087abcc316e2b17ff removed useless test with exist() that is very expensive in Octave (but apparently not in Matlab) ================================ DYNARE MAKE CHECK MATLAB RESULTS ================================ | TOTAL: 430 | PASS: 428 | FAIL: 0 | XFAIL: 2 | XPASS: 0 ================================ DYNARE MAKE CHECK OCTAVE RESULTS ================================ | TOTAL: 428 | PASS: 426 | FAIL: 0 | XFAIL: 2 | XPASS: 0 A full log can be found on karaba in '/tmp/dynare-master-check-J8gmeTU9TB.log'.

1 0

Status of testsuite in 4.4 branch
by sebastien＠dynare.org 01 Feb '14

01 Feb '14

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 01 Feb '14

01 Feb '14

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 31 Jan '14

31 Jan '14

2 1

Status of testsuite in master branch
by sebastien＠dynare.org 30 Jan '14

30 Jan '14

1 0

Treatment of constant-option
by Johannes Pfeifer 29 Jan '14

29 Jan '14

Dear all, the preprocessor currently allows setting ```constant``` and ```noconstant```-options (although they are not fully documented yet). But in ```dynare_estimation_init.m``` any such setting is automatically overwritten by: if all(abs(oo_.steady_state(bayestopt_.mfys))<1e-9) options_.noconstant = 1; else options_.noconstant = 0; end I don't really see the point of keeping the option. Rather the user should specify a correct observation equation. In that case, the current treatment should assure correct results. Best, Johannes

3 2

Upgrading MATLAB requirement to R2007b?
by Sébastien Villemot 29 Jan '14

29 Jan '14

Dynare 4.4 (and unstable) currently require MATLAB >= 7.3 (R2006b), which means that we support MATLAB versions less than 7 years old. I would like to raise the requirement in unstable (and therefore for 4.5) to MATLAB >= 7.5 (R2007b). That would save us various tweaks in the build system, packaging and in the compatibility code. Also, assuming that we release 4.5 one year after 4.4, that means that we would maintain the policy of supporting MATLAB versions less than 7 years old. Is there any objection? -- Sébastien Villemot Researcher in Economics Dynare developer http://www.dynare.org/sebastien

3 2

Status of testsuite in master branch
by sebastien＠dynare.org 29 Jan '14

29 Jan '14

66c1aa78f0fef4472081414e377a32939339aa5c Move add_auxiliary_variables_to_steadystate to partial_information directory. ================================ DYNARE MAKE CHECK MATLAB RESULTS ================================ | TOTAL: 420 | PASS: 418 | FAIL: 0 | XFAIL: 2 | XPASS: 0 ================================ DYNARE MAKE CHECK OCTAVE RESULTS ================================ | TOTAL: 418 | PASS: 416 | FAIL: 0 | XFAIL: 2 | XPASS: 0 A full log can be found on karaba in '/tmp/dynare-master-check-RoIy9Ty0MX.log'.

1 0

Dealing with GitHub issues
by Sébastien Villemot 28 Jan '14

28 Jan '14

Hi, I am getting concerned about the number of outstanding GitHub issues against Dynare. As of now, there are 133 outstanding issues, and this number is following an upward trend. I think that having the number of issues growing too big has a negative impact, because it makes it more difficult to figure out what are the really relevant issues and act on them. It also diminishes the perceived usefulness of filing an issue, since there is a significant probability that there will be no follow up. I am therefore wondering what would be the possible solutions to bring down the number of opened issues. I can see at least: 1. Have developers deal more diligently with issues that are assigned to them (or otherwise mark them as unassigned) 2. Have developers pick up more unassigned issues 3. Hold meetings (as we did last year on IRC) to discuss issues for which a collective decision is needed 4. Acknowledge that we do not have enough resources to deal with some issues, and close them (this probably also needs collective decisions) 5. Organize bug squashing parties Obviously items 1 and 2 are not something that we can decide as a group, but I included them for completeness and as a reminder for everyone. What is your opinion on items 3, 4 and 5? Do you have other ideas? Best, -- Sébastien Villemot Researcher in Economics Dynare developer http://www.dynare.org/sebastien

3 7

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Dev