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?