Skip to content

Conversation

@jimbethancourt
Copy link
Collaborator

@jimbethancourt jimbethancourt commented Dec 18, 2025

  • Now calculating Minimum Feedback Arc Set instead of generating a DSM to identify relationships that need to be removed
  • Calculating Minimum Feedback Vertex Set to identify the direction relationships should move
  • Prioritizing relationships that need to be removed based on number of cycles they are in, the strength of the relationship, and the amount of churn of the source and target class
  • Fixed bug that reversed the relationship direction for generics

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants