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] Non dominated frontiers ranking/sorting #1475

Closed
10 tasks done
Jimmy-INL opened this issue Mar 15, 2021 · 1 comment · Fixed by #1476
Closed
10 tasks done

[TASK] Non dominated frontiers ranking/sorting #1475

Jimmy-INL opened this issue Mar 15, 2021 · 1 comment · Fixed by #1476
Assignees
Labels
priority_critical RAVENv2.1 All tasks and defects that will go in RAVEN v2.1 task This tag should be used for any new capability, improvement or enanchment

Comments

@Jimmy-INL
Copy link
Collaborator

Jimmy-INL commented Mar 15, 2021


Issue Description

Is your feature request related to a problem? Please describe.
For NSGA-II; the multi-objective GA method, it is required to rank the nondominated fronts recursively

Describe the solution you'd like
I suggest a ranking/sorting utility to find the first front give it a baking '1', then remove it from the data, find the next front, rank it '2', then remove it, and so on.

Describe alternatives you've considered
An alternative is to add this in the Genetic algorithm but I guess shipping it as a utility enables reuse.


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_critical task This tag should be used for any new capability, improvement or enanchment RAVENv2.1 All tasks and defects that will go in RAVEN v2.1 labels Mar 15, 2021
@Jimmy-INL Jimmy-INL self-assigned this Mar 15, 2021
@alfoa
Copy link
Collaborator

alfoa commented Apr 5, 2021

Closure checklist passed...

Closure approved via #1476

No need of email, since the capability (ND) is very very recent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_critical RAVENv2.1 All tasks and defects that will go in RAVEN v2.1 task This tag should be used for any new capability, improvement or enanchment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants