Closed easyfly007 closed 1 year ago
Hi @easyfly007.
I'm running the nsgaiii_dtlz2.py
program after adding the get_non_dominated_solutions()
function in this way:
algorithm.run()
front = get_non_dominated_solutions(algorithm.get_result())
The front have 92 solutions, which is the expected result.
How are you using that function, in order to allow us to reproduce the situation where only a solution is returned?
thanks anjebro, I will try to reproduce the issue in my optimizations and will post how to reproduce it when I have one.
Hello, thanks for the great tool of jmetalpy and i use it in my optimization problems and it works quite well. the only issue I observed is that when I run it for 3 objectives optimization, the function get_non_domiated_solutions() seems didn't return the required PF result. it always return 1 PF point no matter how many points the original solutions has. to find out if this is my usage issue or potentially code risk, I try to look into the jmetalpy code and find that in: file util/archive.py:
I am afriad that when del some member in the original list when looping it, it may deleted the unexpeced member there. I think when during the looping of enumerate(), it will always get updated the list and then we are iterate the unexpected members
I did some simple test and find the issue:
what I want is to get the final a = [11, 13], but actually I got is [13, 14]