Inversion merge: Check for possible merging inversions every time inversion breakpoints are modified

caceres-lab / InvFEST-code

Visual platform for human polymorphic inversions

Apache License 2.0

5 stars 0 forks source link

Inversion merge: Check for possible merging inversions every time inversion breakpoints are modified #28

Open cacereslab opened 8 years ago

cacereslab commented 8 years ago

It would be nice if once the breakpoints of an inversion are modified, the database automatically searches for possible inversions with overlapping inversions an gives a warning (the user can decide if it merges the inversions or not using the merging tool).

RuthGG commented 5 years ago

I think that this has been somewhat solved; not exactly a warning but in the Advanced edition section when an inversion has >90% of reciprocal overlap it informs the user that it could be a good match for a merge.

Maybe this message can be completed with more information about the criteria used to find the match, and another line can be incorporated with the inversions that match breakpont-to-breakpoint with the one in the Inversion Report.

cacereslab commented 5 years ago

Yes, maybe we could include below each candidate inversion to merge if the breakpoints match perfectly with those of the reported inversion and the % of reciprocal overlap between them.