Skip to content
This repository has been archived by the owner. It is now read-only.

Investigate issue with disp_dr>subst_auxvar (line 248) #1367

Closed
JohannesPfeifer opened this issue Jan 1, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@JohannesPfeifer
Copy link
Contributor

commented Jan 1, 2017

When M_.aux_vars(i).type = 0 (lead>1), a crash happens. But it is not clear in which case this happens as leads should not be present on the right-hand side of decision rules. See http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=12593

@JohannesPfeifer

This comment has been minimized.

Copy link
Contributor Author

commented Jan 2, 2017

#773 needs to be done to fix this, because otherwise the information to trace the auxililiary variables back to the original ones is missing (M_.aux_vars.orig_index is empty for type=0).

@MichelJuillard

This comment has been minimized.

Copy link
Member

commented Jan 2, 2017

@JohannesPfeifer we need the mod file to be able to replicate the problem. This seems a very peculiar case involving local variables

@MichelJuillard

This comment has been minimized.

Copy link
Member

commented Jan 2, 2017

Complicated nonlinear expression involving leads of different length can generate AUX_ENDO_LEAD variables with lags appearing among the state variables of the model. This could probably be avoided but would require another layer of complexity in the preprocessor. For the time being, when an AUX_ENDO_LEAD variable appears among the state variable, I suggest to use just that name and not to try to substitute it

JohannesPfeifer added a commit to JohannesPfeifer/dynare that referenced this issue Jan 4, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.