-
Notifications
You must be signed in to change notification settings - Fork 741
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
Not all shards generated #776
Comments
@ErinKinghorn somewhat confusingly, shard specifies are 0-based for the first number (shard index) and 1-indexed for the second (count). So your first shard is The message you report here looks normal - and the warning should not make a difference. |
Once you follow @danielecook 's suggestion to see if the files look good. If you in fact find the files look normal, can you please test this docker: docker pull google/deepvariant:CL602468145
docker pull google/deepvariant:CL602468145-gpu It seems like this issue is related to a this issue: #769 |
Thank you for the feedback! @danielecook I can confirm that the files in the tmp directory do look to be normal as you described above. @kishwarshafin, I tested the docker that you suggested and now it seems that Deepvariant did not run at all (vcfs and gvcfs are empty) I have attached a log file for one of the samples, so you can see what happened. |
I have picked up an error in the original cram files for the 4 samples that did not work. Thank you for the help! |
Hi @ErinKinghorn , if I understand your latest comment, you meant that you were able to get them to work now? @kishwarshafin will plan to do a 1.6.1 release to fix the issue above (and will officially publish a Docker). Thanks for helping us test! |
Hi
I have used the following script to run deepvariant (v1.6.0) on WGS samples.
Of the 30 samples I have, only 4 have not completed. I believe this is due to the 32nd shard not being generated in the temporary directory. All of the four samples that have not completed have the same error in the .log regarding the 32nd shard. The error is as follows:
While the run has not errored out, I do believe that there is an issue here and would appreciate if anyone has any insight.
Regards
Erin
The text was updated successfully, but these errors were encountered: