Dev

dev@dynare.org

3402 discussions

[Trac] #262: unify names for maxit options
by Trac Dynare 05 Dec '12

05 Dec '12

#262: unify names for maxit options ---------------------------------+------------------------------------------ Reporter: michel | Owner: michel Type: enhancement | Status: new Priority: major | Milestone: 5.0 Component: Block decomposition | Version: Keywords: | ---------------------------------+------------------------------------------ Several functions need an optional maximum number of iterations. There is currently no unified name style for these options. Until now, we tried to have exactly the same name for the option in the language and the options_ fieldname. In that case, I wonder if we should not have always maxit in the language and specialized the fieldname with a reference to the function. For example maxit in steady -> options_.solve_maxit -- Ticket URL: <https://www.dynare.org/trac/ticket/262> Dynare <http://www.dynare.org> The Dynare project

1 1

[Trac] #293: bug: maxit option in steady
by Trac Dynare 05 Dec '12

05 Dec '12

#293: bug: maxit option in steady ---------------------+------------------- Reporter: houtanb | Owner: Type: bug | Status: new Priority: major | Milestone: Component: General | Version: 4.3.1 Keywords: | ---------------------+------------------- Currently, the preprocessor assigns the maxit option for the steady command to options_.maxit_ and it is used in dynare_solve_block_bytecode.m for finding the steady state; dynare_solve.m, on the other hand, uses options_.solve_maxit (i.e. an option not passed to steady) for solve_algo = 1 or 2, whereas for solve_algo = 0 or 3 the values are hard-coded. This needs to be made uniform. Stephane suggests assigning maxit to options_.solve_maxit in the preprocessor, changing dynare_solve_block_bytecode.m to use options_.solve_maxit, and replacing the hard-coded values in dynare_solve.m with this option as well. -- Ticket URL: <https://www.dynare.org/trac/ticket/293> Dynare <http://www.dynare.org> The Dynare project

1 2

Status of testsuite in 4.3 branch
by sebastien＠dynare.org 05 Dec '12

05 Dec '12

*************************************** * DYNARE TEST RESULTS * * for make check-matlab * *************************************** 192 tests PASSED out of 192 tests run *************************************** *************************************** * DYNARE TEST RESULTS * * for make check-octave * *************************************** 190 tests PASSED out of 190 tests run *************************************** A full log can be found on karaba in '/tmp/dynare-4.3-check-bAEyHXYxJb.log'.

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 05 Dec '12

05 Dec '12

1 0

Status of testsuite in 4.3 branch
by sebastien＠dynare.org 04 Dec '12

04 Dec '12

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 04 Dec '12

04 Dec '12

1 0

Status of testsuite in 4.3 branch
by sebastien＠dynare.org 03 Dec '12

03 Dec '12

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 03 Dec '12

03 Dec '12

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 02 Dec '12

02 Dec '12

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 01 Dec '12

01 Dec '12

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Dev