Dev September 2019

dev@dynare.org

4 participants
4 discussions

Windows packages built from Gitlab CI
by Sébastien Villemot 23 Sep '19

23 Sep '19

Hi all, Just to let you know that Windows packages of Dynare are now automatically built for each commit that is pushed to our Gitlab instance. This includes commits in your personal space (so you can easily test your modifications on Windows or create customized versions of Dynare). Technically, the executable installer and the zip archive are created as artifacts of the pkg_windows job of each pipeline. For example, the last commit on the main Dynare repository triggered this pipeline: https://git.dynare.org/Dynare/dynare/pipelines/1829 By clicking on the pkg_windows button, you end up on that job page: https://git.dynare.org/Dynare/dynare/-/jobs/6312 Then you can retrieve the packages by clicking on the “Browse” link on the upper-right corner: https://git.dynare.org/Dynare/dynare/-/jobs/6312/artifacts/browse And click on the windows directory, then on exe (to get the executable installer; alternatively you could have chose the zip): https://git.dynare.org/Dynare/dynare/-/jobs/6312/artifacts/browse/windows/e… Note those artifacts are deleted from the server one week after they have been generated, to save disk space. Best, -- Sébastien Villemot Economist at CEPREMAP Dynare developer http://sebastien.villemot.name

2 1

breaking changes for stoch_simul and discretionary policy
by Michel Juillard 13 Sep '19

13 Sep '19

Hello, Houtan's commit https://git.dynare.org/Dynare/preprocessor/commit/04b6a68aef1dea23f991e788a… alerts me to the fact that these changes break existing code where the Matlab function is called directly. Many people do that. I wonder if we should not instead rename the functions with the new interface and provide converted functions with the old interface Best -- Michel Juillard

3 4

Issue #1197
by Houtan Bastani 12 Sep '19

12 Sep '19

Hello, In working on https://git.dynare.org/Dynare/dynare/issues/1197 I came across a potential bug. As you can see from lines 22-24 & 39 of https://git.dynare.org/Dynare/dynare/blob/master/matlab/discretionary_polic…, upon exiting discretionary_policy(), `options_ `contains the original values it had upon entering the function with the field `discretionary_policy` set equal to 1. However, the call to stoch_simul potentially changes options_, as you can see on line 99 of https://git.dynare.org/Dynare/dynare/blob/master/matlab/stoch_simul.m. Here, the field `logged_steady_state` is set to 1 with the idea that this value should be preserved upon exit of the function. However, given the way discretionary_policy has been written above, it is not preserved. So the question is: is this a bug? If not, that would imply that discretionary_policy is incompatible with the loglinear option of stoch_simul: should I then end processing if the two hold simultaneously? If not, then we should only overwrite the `order` option in discretionary_policy with its original value. Best, Houtan

3 5

Dynare chat room
by Houtan Bastani 06 Sep '19

06 Sep '19

Hi, We have created a chatroom that you can use for group discussions or one-off discussions. If you'd like to use it, you can follow the link below, signing in with the same account you use at git.dynare.org: https://mattermost.dynare.org/signup_user_complete/?id=mza3tkpwfjdzdqzdkmkq… You can also download an app for your desktop and/or phone if you don't want to use a browser window. Links to download for your system are at the bottom of this page: https://mattermost.com/download/ Best, Houtan

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Dev September 2019