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

Clarify and potentially disentangle role played by conf_sig #338

Closed
JohannesPfeifer opened this issue Mar 21, 2013 · 4 comments

Comments

Projects
None yet
3 participants
@JohannesPfeifer
Copy link
Contributor

commented Mar 21, 2013

According to the manual, conf_sig by default is 0.9 for forecast, but after global_initialization, it is 0.6. conditional_forecast has an option with the same name and default 0.8 according to the manual.

@JohannesPfeifer

This comment has been minimized.

Copy link
Contributor Author

commented Mar 27, 2013

When doing the IRC chat, we should also decide on whether to disentangle the conf_sig-options of different commands and harmonize the naming with #238 and #262

@JohannesPfeifer

This comment has been minimized.

Copy link
Contributor Author

commented Jun 15, 2015

This also affects the bvar-a-la-sims, see http://www.dynare.org/phpBB3/viewtopic.php?f=1&t=6939

@MichelJuillard

This comment has been minimized.

Copy link
Member

commented Oct 12, 2015

Proposed decision: unify the default to 0.8 and correct the manual

@stepan-a stepan-a modified the milestones: 5.0, 4.5 Mar 22, 2016

@stepan-a

This comment has been minimized.

Copy link
Member

commented Mar 22, 2016

We should have separate options (even if the default value is the same)

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.