Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default acceptance Parameter probably wrong in dual annealing #11298

Open
echo5india opened this issue Dec 31, 2019 · 1 comment
Open

Default acceptance Parameter probably wrong in dual annealing #11298

echo5india opened this issue Dec 31, 2019 · 1 comment

Comments

@echo5india
Copy link

Hello,

I think the parameter 'accept' in the dual annealing function has a wrong default value and wrong acceptable bounds. As explained in this paper Tsallis C, Stariolo DA. Generalized Simulated Annealing. Physica A, 233, 395-406 (1996), the acceptance parameter should be above 1 (probably slightly above to be close to classic simulated annealing).

The descrition for this parameter is actually :

"""Parameter for acceptance distribution. It is used to control the probability of acceptance. The lower the acceptance parameter, the smaller the probability of acceptance. Default value is -5.0 with a range (-1e4, -5]."""

Without an acceptable parameter here the algorithms never accepts states of higher energy and the algorithms does not behave as expected.

many thanks

@leostimpfle
Copy link

leostimpfle commented May 22, 2020

The paper does not state that the acceptance parameter qA should be larger than 1. In fact, on p. 402 the authors state that

it is found that the convergence is faster for values of qA < I

and on p. 403 that

the best performing cases are those with visiting parameter qv ~- 2.7 and the acceptance parameter qA as negative as possible.

However, it would be useful to include documentation on how the range (-5, -1e4] of the acceptance parameter has been chosen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants