estimation: support additional_optimizer_steps

Closes #1573 (closed)

added estimation label

added 1 commit

• af652923 - estimation: support additional_optimizer_steps

Compare with previous version

mentioned in merge request !2179 (merged)

added 1 commit

• 04ad9370 - estimation: support additional_optimizer_steps

Compare with previous version

added 13 commits

• 04ad9370...e335fed2 - 12 commits from branch Dynare:master
• 5a5bc0de - estimation: support additional_optimizer_steps

Compare with previous version

This syntax suggests that at least two integers are required in the vector. Is this the case?

Actually there should be no comma to be consistent with the manual syntax

It should be with three options as above, I think

Actually we already have an INTEGER_VECTOR syntax in the manual that is supposed to cover this case, but it is not well-documented and is under-used. So I’m giving up on this specific issue, it should probably be dealt with in another MR.

Same question here

changed this line in version 5 of the diff

I actually think it must be like the new version.

Actually could you separate the bugfix into another commit? (since I closed !2179 (merged))

added 1 commit

• f040f8d4 - estimation: support additional_optimizer_steps

Compare with previous version

I split it off

I don’t see the other commit

I put it into !2184 (merged) as it has nothing to do with the MR, strictly speaking.

added 1 commit

• 53c65ae2 - estimation: support additional_optimizer_steps

Compare with previous version

added 1 commit

• 5a8c5bdb - estimation: support additional_optimizer_steps

Compare with previous version

added 1 commit

• f6a84731 - estimation: support additional_optimizer_steps

Compare with previous version

merged

mentioned in commit 14a71a6d