-
-
Notifications
You must be signed in to change notification settings - Fork 43
#152 Add minimum feedback set algorithms #165
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
Open
jimbethancourt
wants to merge
91
commits into
main
Choose a base branch
from
#152-add-minimum-feedback-set-algorithms
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
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
- Applied Spotless
Initial commit of SuperTypeToken. SuperTypeToken will make it possible to reify graphs in feedback algorithms when needed.
Now using SuperTypeToken in DirectedFeedbackVertexSetSolver and MinimumFeedbackArcSetSolver when creating new graphs in the algorithms
No longer using parallel streams to create vertices in createRandomGraph() to ensure that all vertices are created.
All MinimumFeedbackArcSetSolverTest unit tests are now passing or are disabled with good reason
Adding edges serially instead of in parallel in MinimumFeedbackArcSetSolver.createGraphWithoutEdges(). Adding edges in parallel was causing ArrayIndexOutOfBounds exceptions and appeared to run slightly slower as well when it did succeed. ClassCastException exceptions also stopped. Remediated several issues identified by sonar
No longer adding vertices in parallel. Adding vertices in parallel consistently led to ArrayOutOfBounds exceptions
Initial commit of eta (η) and k computation. Some unit tests are failing - will investigate further.
Initial commit of ModulatorComputer - includes additional algorithms to compute the modulator value Some unit tests are failing - will investigate further.
Adding vertices serially in TreewidthComputer.convertToUndirectedWithoutModulator() - adding vertices in parallel was causing errors and nondeterministic behavior
computeModulator() was returning an empty result when a cycle was present since the current treewidth was calculated to be the target treewidth for some algorithms for a simple cycle.
Adding eta computation shortcuts. A graph with a single vertex will always have an eta of 0, and a graph without cycles will have an eta of 1 for our purposes since we are not interested in graphs that do not have cycles
Extending timeout duration for graph computation Added TODO comment to look into using a SparseIntUndirectedGraph to perform copies
ModulatorComputerTest.ModulatorComputationTests.testCycleGraphModulator() was not generated correctly by Perplexity AI when it was generated. The graph generated is a cycle and will have a treewidth of 2.
Initial commit of OptimalKComputer and test classes
Adding no-arg solve() method to DirectedFeedbackVertexSetSolver and using the KosarajuStrongConnectivityInspector strongly connected count result as the value for k since it is a lower bound for k for a graph.
Added 1000 and 1500 node graph sizes to sparse graph benchmark test since codebases can get large but are often sparse
First pass of providing prioritized edges to remove. Will likely need to revisit how the edges are prioritized.
Updated algorithm that sorts edges that need to be removed and added unit test to confirm desired behavior
- Reordered edge disharmony removal columns - Moved edge disharmony rendering methods next to the renderEdgeDisharmonies() method
No longer computing FAS in parallel since it typically leads to a ConcurrentModificationException, even in large codebases.
Returning a CodebaseGraphDTO containing a classReferencesGraph instead of only a classReferencesGraph
Adding className Field to ScmLogInfo to allow mapping of class name to a file in Git. May be able to remove this in the future.
…each commit. Now caching the sum of all committed files in the repository at each commit. However, it does not appear that this provides a significant gain in speed.
Adding className Field to ScmLogInfo to allow mapping of class name to a file in Git. May be able to remove this in the future.
Returning a CodebaseGraphDTO containing a classReferencesGraph instead of only a classReferencesGraph
Calculating the priority order of edges / relationships that need to be removed to remove all cycles from the codebase
Adding HashMap as placeholder constructor value for CostBenefitCalculator since cycles are not currently being evaluated in the CsvReport or JsonReportExecutor
- Capturing edge target information to improve the ranking of relationships that need to be removed - Displaying only the largest cycle to keep page load time to a minimum while also allowing users to investigate the largest cycle.
- Making classes that need to be removed in bold instead of having a separate column indicating that it should be removed - Added spacing - Removed redundant text - Removed dead code
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Uh oh!
There was an error while loading. Please reload this page.