Bug in NSGA-II in jMetal 5.8+: getting solutions from population during reproduction
See original GitHub issueI was reading the code of NSGA-II and found out that, during reproduction, the solutions are taken sequentially from the population itself instead of the mating pool. See line 122:
I believe it is a bug, because the mating pool is the one containing the selected parents from the selection phase. Moreover, the indexes are taken from the mating pool, which is another indication that the reproduction is using the wrong list.
If it is indeed a bug (I might be wrong), the fix is straightforward: matingPool.get(i+j)
instead of population.get(i+j)
in line 122.
This code is the same for versions 5.7 and 5.9 too.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Release 6.0-SNAPSHOT - jMetal project documentation
The last step is to run NSGA-II, get the result and store the found solutions: AlgorithmRunner algorithmRunner = new AlgorithmRunner.
Read more >ARJA: Automated Repair of Java Programs via Multi-Objective ...
Abstract—Automated program repair is the problem of automatically fixing bugs in programs in order to significantly reduce the.
Read more >Supporting Evolution and Maintenance of android Apps - CORE
This dissertation presents a set of empirical studies, as well as solutions for some of the key challenges when evolving and maintaining Android...
Read more >14 Configuring Software Product Lines by Combining Many ...
Next, offspring solutions are obtained by using crossover and mutation operators. Finally, through the environmental selection procedure, the population for the ...
Read more >Multi-objective Ensemble Generation for Software Defect ...
population, respectively. At the end of the generation, the fittest solutions survive and become parents in the subsequent generation. When a given stopping ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for reporting the bug and the pull request to fix it.
I guess since the fix from my pull request was merged into the 5.10 release, this issue can be closed.