Dev

dev@dynare.org

3402 discussions

Status of testsuite in master branch
by sebastien＠dynare.org 06 Jan '13

06 Jan '13

1 0

Status of testsuite in 4.3 branch
by sebastien＠dynare.org 05 Jan '13

05 Jan '13

*************************************** * 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-nyVyf5UTmF.log'.

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 05 Jan '13

05 Jan '13

1 0

Status of testsuite in 4.3 branch
by sebastien＠dynare.org 04 Jan '13

04 Jan '13

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 04 Jan '13

04 Jan '13

1 0

[Trac] #294: rework option handling
by Trac Dynare 03 Jan '13

03 Jan '13

#294: rework option handling --------------------------+----------------------- Reporter: houtanb | Owner: sebastien Type: bug | Status: new Priority: major | Milestone: Component: Preprocessor | Version: Keywords: | --------------------------+----------------------- It's desirable at times to know whether or not a user has set an option in the .mod file. To do this, we can hack the preprocessor to maintain a separate cellarray, that it would assign to every time it encounters an option. Something to the effect of: {{{ {'option' , assigned , default_val} {<<string>>, <<0 or 1>>, <<general>>} }}} This can be done in the preprocessor without changing the backend matlab code. It would thereby provide the possibility, when needed, to check whether or not an option was assigned by the user, allowing us to know whether or not we can change the value. In addition to this, we need to think of a better solution than sharing options across commands. This will probably entail a renaming of options. -- Ticket URL: <https://www.dynare.org/trac/ticket/294> Dynare <http://www.dynare.org> The Dynare project

1 1

Status of testsuite in 4.3 branch
by sebastien＠dynare.org 03 Jan '13

03 Jan '13

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 03 Jan '13

03 Jan '13

1 0

Status of testsuite in 4.3 branch
by sebastien＠dynare.org 02 Jan '13

02 Jan '13

1 0

Status of testsuite in master branch
by sebastien＠dynare.org 02 Jan '13

02 Jan '13

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Dev