Adding a scout-PSO option #893
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds the Scout machanisme to the PSO algorithm to enhance the volatility of the process and avoid particles that cannot updates their pbest for some time.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solves JuliaNLSolvers/NLSolvers.jl#8
This adds the Scout machanisme to the PSO algorithm to enhance the volatility of the process and avoid particles that cannot updates their pbest for some time.
The algorithm is based on this paper, and aims at regenerating via a Scout phase (inspired by bee colony optimisations routines) the particles that are 'stuck' for a while, i.e. that did not update their personal best for some time.
Note that the implementation is rough and in particular i did not extract a parameter to activaite/deactivaite the Scoute phase to the constructor of ParticleSwarm(). Therefore it should probably NOT be merged as-is.