Problem transformation functionality#473
Draft
g-poveda wants to merge 3 commits into
Draft
Conversation
this comes from the observation that many problem are generalisation of the other one (but without python inheritance), so solver from one problem can be used to the other one modulo transformation of the solutions. We generalize therefore the sequentialmetasolver mecanism to include transformation nodes which transforms problem. Moreover we can also build any dag of execution of different bricks. The mecanism still will evolve with the different needs or examples we could find in the lib.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In this big PR, we add a new functionality around problem transformation.
-The idea is to add an api (in generic_tools/transformation) that is specifically done to transform a problem into another one, keeping either an exact or approximated mapping, and convert also the solution from 1 problem to another one.
-We then build a TransformationSolver class that is a new SolverDO class that take a source problem, a problem transformation and a solver subbrick to build a new solver. In practice it can be used for example to solve a binpack problem using a RCPSP solver.
-We introduce a new api idea to generalize SequentialMetaSolver, by creating a DAG of solver/transformation that can be used to solve a problem, it allows "parallel" solver tries (in different branches of the DAG) even though it's not done in parallel in practice.
-Added transformation for most problem and associated tests.
Replace #466