You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was hoping the info fields preserved by breakpointRanges() would also be preserved as additional columns but this is not the case. Could this be implemented as an option, or could you suggest a workaround? Thanks.
The text was updated successfully, but these errors were encountered:
This issue is that each bedpe record is a merger of two breakpointGRanges rows and those two rows don't necessarily have the same values. For example the partner field.
For simple DEL/DUP/INS events, it's a 1 to 2 to 1 operation so there's no ambiguity, so you could copy the INFO fields from info(vcf) as additional bedpe columns. For other events, you'll need to work out which is the 'correct'^ value.
^ in many cases there is no 'correct' value. For example, a breakpoint can be homozygous on one side and heterozygous on the other side (e.g. chr1<->chr2 breakpoint with a total loss of the other copy of chr2).
Hello, sorry to bother you. I used StructuralVariantAnnotation packages when annotating on the vcf results of Gridss
software. This R package appears in the annotation script. I encountered some issues while running this script. I received the file, but it did not contain the expected columns. May I consult with you? Thank you very much!
Hello,
Thanks for maintaining StructuralVariantAnnotation! I'm attempting to convert VCFs to .bedpe files using the following code:
I was hoping the info fields preserved by breakpointRanges() would also be preserved as additional columns but this is not the case. Could this be implemented as an option, or could you suggest a workaround? Thanks.
The text was updated successfully, but these errors were encountered: