Dev January 2012

dev@dynare.org

5 participants
137 discussions

Status of testsuite in 4.2 branch
by Sébastien Villemot 11 Jan '12

11 Jan '12

*************************************** * DYNARE TEST RESULTS * * for make check-matlab * *************************************** 150 tests PASSED out of 150 tests run *************************************** *************************************** * DYNARE TEST RESULTS * * for make check-octave * *************************************** 148 tests PASSED out of 148 tests run *************************************** A full log can be found on karaba in '/tmp/dynare-4.2-check-Mj5Nz2cV2p.log'.

1 0

Status of testsuite in master branch
by Sébastien Villemot 10 Jan '12

10 Jan '12

*************************************** * DYNARE TEST RESULTS * * for make check-matlab * *************************************** 166 tests PASSED out of 166 tests run *************************************** *************************************** * DYNARE TEST RESULTS * * for make check-octave * *************************************** 164 tests PASSED out of 164 tests run *************************************** A full log can be found on karaba in '/tmp/dynare-master-check-uFiCIMW9Nd.log'.

1 0

Status of testsuite in 4.2 branch
by Sébastien Villemot 10 Jan '12

10 Jan '12

1 0

persistent 'penalty'
by Michel Juillard 09 Jan '12

09 Jan '12

In my yesterday message on this subject, my understanding of the initialization of persistent variable 'penaly' in dsge_likelihood.m and dsge_likelihood_hh.m was wrong. I reverted my addition of explicit initialization and added the following comment in both functions. I also added a call to dsge_likelihood_hh() in initial_estimation_check.m to make sure that penalty was correctly iniitialized in this function as well. In the present case, the difficulty with persistent variables is compounded by the fact that penalty is not used in all contexts, only when dsge_likelihood() or dsge_likelihood_hh() is called by an optimizer. Comment added: % Persistent variable 'penalty' is used to compute an endogenous penalty to % the value 'fval' when various conditions are encountered. These conditions % set also 'exit_flag' equal to 0 instead of 1. It is only when % dsge_likelihood() is called by an optimizer called by % dynare_estimation_1() that 'exit_flag' is ignored and penalized 'fval' is % actually used. % In that case, 'penalty' is properly initialized, at the very end of the % present function, by a call to dsge_likelihood() made in % initial_estimation_checks(). If a condition triggers exit_flag == % 0, initial_estimation_checks() triggers an error. % In summary, an initial call to the present function, without triggering % any condition, guarantees that 'penalty' is properly initialized when needed. Best Michel

1 0

[Trac] #173: fix license problems in GSA
by Trac Dynare 09 Jan '12

09 Jan '12

#173: fix license problems in GSA --------------------------+------------------------------------------------- Reporter: sebastien | Owner: Type: bug | Status: new Priority: critical | Milestone: Component: Core M-files | Version: Keywords: | --------------------------+------------------------------------------------- Some files in the {{{matlab/gsa}}} subdirectory have copyright status incompatible with inclusion in Dynare. At least: {{{ fdjac.m LPTAU.m optget.m Sampling_Function_2.m }}} Other files do not have any copyright notice, their status should be checked. The copyright status of the GSA manual is not explicited. Once these issues are fixed, the license.txt file should be updated accordingly. -- Ticket URL: <https://www.dynare.org/trac/ticket/173> Dynare <http://www.dynare.org> The Dynare project

1 5

[Trac] #235: passing MEXEXT to compile MEX files
by Trac Dynare 09 Jan '12

09 Jan '12

#235: passing MEXEXT to compile MEX files --------------------------------------+------------------------------------- Reporter: michel | Owner: sebastien Type: enhancement | Status: new Priority: critical | Milestone: 4.3 Component: Build system / Packaging | Version: Keywords: | --------------------------------------+------------------------------------- In Matlab, the extension name of the MEX file varies accross plateform. When we use USE_DLL and call the model file DLL in another DLL (it is the case for estimation, for example) we need to know this extension. Currently, the Matlab calling program use mexext() to get a string and passes this string to the, say, estimation DLL. This is very roundabout, because mexext() makes a system call to evaluate a batch file to learn the name of the MEX extension of a given system. I would prefer to know the extension name at the time of compilation of the DLL and hard code it in the DLL. Currently, the build system already puts the extension name in environment variable MEXEXT. I suggest the following modification to the Makefile: from MATLAB_DEFS = -D_GNU_SOURCE -DNDEBUG -DMATLAB_VERSION=0x0713 to MATLAB_DEFS = -DMEXEXT=${MEXEXT} -D_GNU_SOURCE -DNDEBUG -DMATLAB_VERSION=0x0713 Then, we can just use macrovariable MEXEXT in the C++ code when necessary. The same can be used for OCTAVE but I expect the name of the extension to be always the same. -- Ticket URL: <https://www.dynare.org/trac/ticket/235> Dynare <http://www.dynare.org> The Dynare project

1 1

Status of testsuite in master branch
by Sébastien Villemot 09 Jan '12

09 Jan '12

1 0

Status of testsuite in 4.2 branch
by Sébastien Villemot 09 Jan '12

09 Jan '12

1 0

Status of testsuite in master branch
by Sébastien Villemot 08 Jan '12

08 Jan '12

1 0

Status of testsuite in 4.2 branch
by Sébastien Villemot 08 Jan '12

08 Jan '12

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Dev January 2012