-
Notifications
You must be signed in to change notification settings - Fork 25
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
whamg trouble - finishing instantly with no results #38
Comments
Odd. |
Well that's what's so odd, there was no error message. Nothing at all was echoed to the screen, and according to the .err file everything went fine, but there was no output (except for the VCF header) and it took no time to run. samtools view -H SL150028.bwamem.unfilt.rmdup.sort.bam |
can you post the full SL150028.err error file? There should be something like: INFO: for Sample:xxx |
What I posted in the original message was the full file. I have only INFO fields, no STATS fields like in your example. |
@afkoeppel thanks, I was expecting it to be longer, but maybe not if it is an options parsing error. original: "whamg -a $GENOME **–**f SL150028.bwamem.unfilt.rmdup.sort.bam > SL150028.vcf 2> SL150028.err" try: "whamg -a $GENOME -f SL150028.bwamem.unfilt.rmdup.sort.bam > SL150028.vcf 2> SL150028.err" Note the difference in the dash for -f. If this solves the problem I'll add better error handling for this case. |
Well I'll be. I replaced the dash and now it seems to be running. I'll update as soon as I have output. I'm not even quite sure how I got that non-dash dash, but I think maybe from copy-pasting from the instructions here (I sometimes copy example commands and then just replace the file names with my own). |
Shame on me! I'll make sure to check for m vs n dash. http://www.punctuationmatters.com/hyphen-dash-n-dash-and-m-dash/ The wrong dash was in the README. |
That did the trick. I have a vcf with SVs in it now. Thank you so much for your help. |
Trying to call SVs on some rat sequences and want to try whamg.
whamg -a $GENOME –f SL150028.bwamem.unfilt.rmdup.sort.bam > SL150028.vcf 2> SL150028.err
Strangely, it seems to be finishing instantaneously (despite >50Gb bam file), and producing no results.
cat SL150028.err
INFO: fasta file: /home/sdt5z/genomes/igenomes/Rattus_norvegicus/Ensembl/Rnor_5.0/Sequence/WholeGenomeFasta/genome.fa
INFO: Loading discordant reads into forest.
INFO: Finished loading reads.
INFO: Gathering graphs from forest.
INFO: Matching breakpoints.
INFO: Printing.
INFO: done processing trees
INFO: WHAM finished normally, goodbye!
The output VCF file contains the VCF header lines but is otherwise empty.
I also tried with the -c option limiting to just a few chromosomes, but the results were the same.
Any advice about what I might be doing wrong would be appreciated.
The text was updated successfully, but these errors were encountered: