-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Updating solver __solve function for MOO #787
Conversation
The _loss function accommodates the MultiObjectiveOptimizationFunction in the __solve method.
Updated loss function in __solve of OptimizationEvolutionary.jl
Any reason for raising this PR, it would be great to know what kind of bug you're trying to fix. |
@Abhinavcode13 it's a PR, not an issue. The aim is to add support for multiobjective optimization with Evolutionary.jl (for now) |
Thanks for pointing it out, but don't it already support one? |
No |
Set the traits for NSGA2 explicitly
Updated the __loss function to handle MOOFunction results.
Added the struct to use BB0_borg_moea.
Exported the new borg_moea struct.
Corrected the loss function check for MultiObjectiveOptimizationFunction.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs the tests to be pushed to the PR
Added tests for the Multi-Objective Optimization tests to the test set.
Added Multi-Objective Optimization tests to the test set.
Removed NaNMath, as it wasn't needed.
Added regression tests to the tests for MOO.
Added regression tests for MOO.
Evolutionary seems to be failing, it might be a random number seeding issue, when you ran it locally did you run the entire script in the same order? |
The regression tests have been updated to solve errors.
The optimize function call updated to handle multi-objective problems.
Added the build_solution alternative call for MOO tests.
Added objective tests for the testset.
Great work @ParasPuneetSingh! 🎉 |
Checklist
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
Additional context
Add any other context about the problem here.