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

[TASK] Crowding Distance for repeated boundary points #2427

Open
10 tasks
Jimmy-INL opened this issue Jan 18, 2025 · 0 comments
Open
10 tasks

[TASK] Crowding Distance for repeated boundary points #2427

Jimmy-INL opened this issue Jan 18, 2025 · 0 comments
Assignees
Labels
priority_critical task This tag should be used for any new capability, improvement or enanchment ToDo

Comments

@Jimmy-INL
Copy link
Collaborator


Issue Description

The crowding distance function should give the points on the boundary of each front a value of infinity. If there are repeated points on the boundary, all of them should get the same distance (infinity)
Is your feature request related to a problem? Please describe.
Without this, the probability of the boundary points will reduce and hence the diversity will reduce which might delay the convergence.

Describe the solution you'd like
If a point (or more) is/are repeated on the boundary of the nondominated front, they all should get the same crowding Distance

Describe alternatives you've considered
N/A


For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@Jimmy-INL Jimmy-INL added priority_minor task This tag should be used for any new capability, improvement or enanchment priority_critical ToDo and removed priority_minor labels Jan 18, 2025
@Jimmy-INL Jimmy-INL self-assigned this Jan 18, 2025
Jimmy-INL added a commit to JunyungKim/raven that referenced this issue Jan 18, 2025
…epeaqted boundry points on the nondominated fronts infinity
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_critical task This tag should be used for any new capability, improvement or enanchment ToDo
Projects
None yet
Development

No branches or pull requests

1 participant