-
Notifications
You must be signed in to change notification settings - Fork 45
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
The target SV in *.svaba.sv.vcf is not found in *.alignments.txt.gz #127
Comments
I can’t see the whole SV, but if is a discordant-read only SV (DSCRD), it
won’t be in alignments (contigs) file.
…On Mon, Jul 31, 2023 at 10:30 AM hhd1008611 ***@***.***> wrote:
Hello,
By the code:
svaba run -t $TUM_BAM -t $NORM_BAM -p $CORES -k $k -a $name -G $REF
I found the target SV in *.svaba.sv.vcf, but the target SV is not found in
*.alignments.txt.gz. Is there something wrong with my code? Please tell me
if this is normal, thank you very much.
[image: image]
<https://user-images.githubusercontent.com/35066896/257251221-f7206d3c-1fba-4b37-a690-f2437da5fcaf.png>
—
Reply to this email directly, view it on GitHub
<#127>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUZ7CGMWL3IQPUMKQN42WDXS66RBANCNFSM6AAAAAA26LGAKY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
The order of the IGV diagram is: |
well the discordant reads are relevant for CNVs. What I think you mean is that they aren't substantial contributors to the copy-number. Svaba aims to compile rearrangement breakpoints, especially complex ones, that are most relevant in cancer genomes. For finding germline CNVs, you might try Lumpy |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
By the code:
svaba run -t $TUM_BAM -t $NORM_BAM -p $CORES -k $k -a $name -G $REF
I found the target SV in *.svaba.sv.vcf, but the target SV is not found in *.alignments.txt.gz. Is there something wrong with my code? Please tell me if this is normal, thank you very much.
The text was updated successfully, but these errors were encountered: