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

Extending moarchiving to 3 and 4 objectives #8

Open
13 of 15 tasks
ttusar opened this issue Mar 15, 2024 · 1 comment
Open
13 of 15 tasks

Extending moarchiving to 3 and 4 objectives #8

ttusar opened this issue Mar 15, 2024 · 1 comment

Comments

@ttusar
Copy link

ttusar commented Mar 15, 2024

@nikohansen could you help me determine which of the methods of BiobjectiveNondominatedSortedList would need to be implemented by a similar class for 3 and 4 objectives? Here's a list of all of them:

  • add
  • add_list
  • contributing_hypervolume (of an element already existing in the archive; if the element is not in the archive yet, it returns hypervolume_improvement)
  • copy ?
  • discarded (maybe for testing purposes)
  • distance_to_hypervolume_area
  • distance_to_pareto_front ("Pareto front" should be taken with a grain of salt)
  • dominates
  • dominators
  • hypervolume
  • hypervolume_improvement (0 if the element is already in the archive and > 0 otherwise)
  • in_domain
  • infos
  • make_expensive_asserts (a flag used for testing purposes)
  • remove
@ttusar
Copy link
Author

ttusar commented Mar 20, 2024

Some additional clarifications after a discussion with @nikohansen:

  • self.hypervolume_computation_float_type is telling you which kind of float type (float or fraction - to be used where the precision is cancelled) is used in some parts of the code. Done for performance reasons.
  • Similarly holds for self.hypervolume_final_float_type
  • Try to not introduce new dependencies (the code is independent of fractions.Fraction right now)

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

No branches or pull requests

1 participant