Closed alongalor closed 5 years ago
Hi Alon,
I think this is a bug in GATK, see https://gatkforums.broadinstitute.org/gatk/discussion/comment/42836#Comment_42836-- they should have a release fixing it soon. @chapmanb might know better, though. It looks like it might be something that you could try rerunning and it might only happen randomly. bcbio will pick up where it left off if you start again to see if it fails in the same spot.
Ah interesting! Thanks for the quick reply Rory! Much appreciated!
Alternatively you could turn on GATK4 instead and run with that and it shouldn't have this issue. See Brad's GATK4 validation here (https://github.com/bcbio/bcbio_validations/tree/master/gatk4). You can turn on GATK4 with this: http://bcbio-nextgen.readthedocs.io/en/latest/contents/configuration.html (search for GATK4). Adding tools_on: [gatk4]
to your configuration template will turn on GATK4.
Great suggestion. Thanks again!
Hi Alon, side note, should your genome_build be hs37d5 in your project template?
Haha hey Patrick, thanks for jumping in! Just running a test here, but in general I am!
cool, cheers!
Thanks, hopefully this was all set, closing for now.
Hello!
I am using the
gatk-variant
template and have encountered some issues I would really appreciate any help with.Upon executing the following command:
bcbio_nextgen.py /n/data1/hms/dbmi/park/alon/software/bcbio/project2/config/project2.yaml -t ipython -n 64 -s lsf -q park_long
things run smoothly for a few hours and then an error appears.
the
bcbio-nextgen-debug.log
is attached. bcbio-nextgen-debug.logThe commands I used are as follows:
*for reference, my
project2-template.yaml
reads as follows:Thanks a lot for your help!
Alon