Make default jscale depend on number of estimated parameters

Related to #1849 (closed)

added estimation label

assigned to @JohannesPfeifer

The mh_init_scale_factor will supersede the current mh_init_scale. How shall we deal with this? Simply replace the old by the new option? Or should we filter out that old option and provide an explicit error message pointing to the new one?

requested review from @stepan-a

added 188 commits

• 227744c6...755c5645 - 187 commits from branch Dynare:master
• 04c4fb1d - Make default jscale depend on number of estimated parameters

Compare with previous version

@stepan-a Any news on this?

assigned to @sebastien and unassigned @JohannesPfeifer

@JohannesPfeifer Can you rebase this?

added 107 commits

• 04c4fb1d...595f3d1d - 106 commits from branch Dynare:master
• 4be693ab - Make default jscale depend on number of estimated parameters

Compare with previous version

@sebastien I rebased. Should I make a proposal for the preprocessor part?

Yes please.

mentioned in merge request preprocessor!73 (merged)

added 1 commit

• f8faa808 - Make default jscale depend on number of estimated parameters

Compare with previous version

I amended the commit and did a PR in preprocessor!73 (merged)

added 1 commit

• 94adc82b - Make default jscale depend on number of estimated parameters

Compare with previous version

added 1 commit

• 17a34aee - Make default jscale depend on number of estimated parameters

Compare with previous version

There is a merge conflict. I guess it’s because of the preprocessor, because you did not rebase on the latest update.

added 1 commit

• a0fb223b - Make default jscale depend on number of estimated parameters

Compare with previous version

added 6 commits

• a0fb223b...6185767f - 5 commits from branch Dynare:master
• f0732f2b - Make default jscale depend on number of estimated parameters

Compare with previous version

Now it should be fixed.