This site is now read-only. You can find our new documentation site and support forum for posting questions here.
Be sure to read our welcome blog!
MuTect2 seems to be hung, has created .vcf but run for many hours without creating the .idx
I've had several instances of MuTect2 running, on 5 samples. Three have finished and there is a .vcf and corresponding .idx file for each, each pair with the same time stamp. The other 2 samples have not finished although they have been running for 24 hours in one case and 15 hours in the other. The .vcf files for those two are present in the directory and their size is non-zero. I think files are usually size 0 while they are being created, which suggests to me that Mutect2 is finished making the .vcf files. There are no .idx files in the directory for those two. I assume that creating the index file is very fast. I'm wondering if somehow MuTect2 has hung? 'top' shows two processes running with Mutect2, and 'top -H' shows perhaps 26 additional processes that come and go, and are threads running within Mutect2, I think. I have not specified the -nct option so as far as I know Mutect2 should not be running extra threads (although maybe that just means it won't run a certain TYPE of thread?). I'm unsure whether to keep waiting for it to finish, or kill it. The file size has not changed all day.