class documentation
class TestMOArchiving4obj(unittest.TestCase):
Tests for the MOArchive4obj class
Method | test |
test if the add_points function works correctly for 4obj points |
Method | test |
test the contributing_hypervolume function, by comparing it to the 3obj result |
Method | test |
test the distance_to_hypervolume_area function |
Method | test |
test the distance_to_pareto_front function, by randomly sampling points and computing the distance to the selected point |
Method | test |
test the distance_to_pareto_front function, by comparing it to the 2obj pareto front |
Method | test |
test the distance_to_pareto_front function, by comparing it to the 3obj pareto front |
Method | test |
test the dominates function |
Method | test |
test the dominators function |
Method | test |
test the hypervolume calculation, by comparing to the result of original implementation in C |
Method | test |
test if the hypervolume is calculated correctly after adding points |
Method | test |
test the hypervolume calculation for a 'simple' case |
Method | test |
test the hypervolume_improvement function, by comparing it to the 3obj result |
Method | test |
test the hypervolume_plus indicator |
Method | test |
test if the in_domain function works correctly for 3obj points |
Method | test |
test if the infos about dominated points are removed |
Method | test |
test if the infos are stored correctly - if the points are non dominated, the infos should be the same |
Method | test |
Test that the length of the archive is correct after adding and removing points |
Method | test |
Test the remove function, by comparing the archive with 100 non-dominated points added and then 50 removed, to the one with only the other 50 points added |
test the distance_to_pareto_front function, by randomly sampling points and computing the distance to the selected point
test if the infos are stored correctly - if the points are non dominated, the infos should be the same