No longer forbid bytecode with order=2 or k_order_solver

The two are now compatible, even though the bytecode representation will not be
used. Print a warning to make this explicit.
kalman-mex
Sébastien Villemot 2023-10-19 14:10:01 -04:00
parent 846ed7e829
commit a9c581e2bc
No known key found for this signature in database
GPG Key ID: 2CECE9350ECEBE4A
2 changed files with 8 additions and 6 deletions

View File

@ -85,6 +85,9 @@ if M_.maximum_endo_lead==0 && M_.exo_det_nbr~=0
end
if options_.k_order_solver
if options_.bytecode
warning('Option "bytecode" is ignored when computing perturbation solution at higher order')
end
orig_order = options_.order;
options_.order = local_order;
dr = set_state_space(dr,M_);
@ -112,12 +115,11 @@ if local_order == 1
end
elseif local_order == 2
if (options_.bytecode)
error('Option "bytecode" is incompatible with order = 2')
else
[~,jacobia_,hessian1] = feval([M_.fname '.dynamic'],z(iyr0),...
exo_simul, ...
M_.params, dr.ys, it_);
warning('Option "bytecode" is ignored when computing perturbation solution at order = 2')
end
[~,jacobia_,hessian1] = feval([M_.fname '.dynamic'],z(iyr0),...
exo_simul, ...
M_.params, dr.ys, it_);
[infrow,infcol]=find(isinf(hessian1));
if options_.debug
if ~isempty(infrow)

@ -1 +1 @@
Subproject commit f78c428d99884c4b336dba0a7df20c7ad41fb682
Subproject commit 6235e6907526d468e2c35f14c38db1e308698bc9