"Johannes Pfeifer" jpfeifer@gmx.de writes:
When looking at the history of prior_bounds in Tortoise Git it showed that the Octave error message was added. But it also showed that the order had been changed. However, I am not sure that the display of diff was correct. It may have been introduced in a different commit.
Looking closely at the diff, I see no change in order. So I think it is a different commit which introduced the bug.
Are you aware of a previous version of Dynare that was not affected by the bug? We could then use git-bisect to quickly find the culprit.
-----Ursprüngliche Nachricht----- Von: dev-bounces@dynare.org [mailto:dev-bounces@dynare.org] Im Auftrag von Sébastien Villemot Gesendet: Freitag, 14. September 2012 12:01 An: List for Dynare developers Betreff: Re: [DynareDev] prior_bounds
"Johannes Pfeifer" jpfeifer@gmx.de writes:
it seems as if commit e95defd117b03fe175fbd8d41b17b435457671e5 introduced a bug into priorbounds. If prior_trunc~=0, the first output argument contains the lower bound of the priors, while if prior_trunc==0 it contains the upper bound, i.e. the order is switched. See http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=4067
I don't understand how the commit that you point at can trigger such a bug. The commit just adds an error message under Octave, but I don't see how it can possibly switch the order of output arguments. Which test did you perform to arrive at the conclusion that this commit is the culprit?
-- Sébastien Villemot Researcher in Economics http://www.dynare.org/sebastien Phone: +33-1-40-77-84-04
Dev mailing list Dev@dynare.org https://www.dynare.org/cgi-bin/mailman/listinfo/dev