Repository navigation
WIP: Initial impl of error subgraph visualization - #374
Draft
cmalinmayor wants to merge 1 commit into
Draft
cmalinmayor wants to merge 1 commit into
cmalinmayor wants to merge 1 commit into
Conversation
This branch has not been deployed
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
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.
Proposed Change
Add a utility to take the output of a matching/error computation (annotated graphs), filter to subgraphs with error annotations, build small "matched" graphs (including the matching edges), and export those as graphml files. These can then be plotted with our docs example plotting function, if you sum all the spatial dimensions for the y axis.
Not sure how much of my use-case-specific setup leaked into here, since I basically just ported it over without the loading. But it's super useful already!! I had to resolve annotation discrepancies in two versions of annotations of the same tracks, and this narrowed it down to exactly the cases an annotator needed to resolve much better than individual lists of nodes/edges.
Types of Changes
What types of changes does your code introduce? Delete those that do not apply.
Which topics does your change affect? Delete those that do not apply.
TrackingGraph,run_metrics,cli, etc.)Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.