-
Notifications
You must be signed in to change notification settings - Fork 25
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
Unfeasible problem analyzer : add a new check #1689
Conversation
…n() function for analysis
…nto a shared pointer This change should be useful in the devs to come, when passing the problem to new analysis classes
…eport by adding a sort method
…eport by adding a sort method
…ve slack vars analysis to its own class
…m abstract analysis class
…implementing the run() method
…this title is then printed to logs
…implementing the printReport() method
…de for further unit tests
…undsConsistency in separate source files
… and any particular analysis as dependency of analyzer
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.
a few more design issue + unit tests would be nice :)
|
||
namespace Antares::Optimization | ||
{ | ||
class UnfeasibilityAnalysis |
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.
We could add some documentation comments on the few classes we added, to clarify their role
double upBound; | ||
}; | ||
|
||
class VariablesBoundsConsistency : public UnfeasibilityAnalysis |
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.
Can we add unit tests to this module, like a few tests for each component, the 2 analysis and the analyzer?
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.
Yes we can. It should be the subject of a further issue / PR.
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.
Will be done in #1716
src/solver/infeasible-problem-analysis/unfeasible-pb-analyzer.h
Outdated
Show resolved
Hide resolved
src/solver/infeasible-problem-analysis/variables-bounds-consistency.cpp
Outdated
Show resolved
Hide resolved
src/solver/infeasible-problem-analysis/variables-bounds-consistency.cpp
Outdated
Show resolved
Hide resolved
…run methods (next part)
src/solver/infeasible-problem-analysis/constraint-slack-analysis.h
Outdated
Show resolved
Hide resolved
src/solver/infeasible-problem-analysis/constraint-slack-analysis.h
Outdated
Show resolved
Hide resolved
Not that i'm against it but the new file's name are not consistent with other lib name convention (we generally don't have hyphens) |
src/solver/infeasible-problem-analysis/unfeasible-pb-analyzer.cpp
Outdated
Show resolved
Hide resolved
src/solver/infeasible-problem-analysis/unfeasible-pb-analyzer.cpp
Outdated
Show resolved
Hide resolved
…ared ptr with unique ptr
…copy into a const &
…tions that need it
Signed-off-by: Sylvain Leclerc <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
The current PR to fix issue #1682
what's done here :