Note: only do this if you have been explicitly asked to do so.
You posted a question about a problem you had with GATK tools, we answered that we think it's a bug, and we asked you to submit a detailed bug report.
A snippet file is a slice of the original BAM file which contains the problematic region and is sufficient to reproduce the error. We need it in order to reproduce the problem on our end, which is the first necessary step to finding and fixing the bug. We ask you to provide this as a snippet rather than the full file so that you don't have to upload (and we don't have to process) huge giga-scale files.
-Largument and progressively narrowing down the interval
-Lto write the problematic region (with 500 bp padding on either side) to a new file -- this is your snippet file.
We've realized that having separate Team / Community Q&A sections is confusing and unnecessary, so we are going to merge the two. From now on there will only be one Q&A section (Ask the Team). We invite you to ask any questions related to the GATK and its application in that category. We welcome answers and comments from everyone in the community in these discussions; if you know something, say something! And of course you are also always welcome to comment on tool and method documentation articles.
Hello GATK users,
You may have noticed that we have had a spate of spam postings on the forum in the past two days. We apologize for any inconvenience this may have caused you, and would like to assure you that we are working to improve our spam blocking defenses in order to minimize the possibility of further incidents.
We have taken a few immediate measures that may affect your use of the forum.
First, all new users will now be required to confirm their email before they are allowed to post any comments. If you find yourself suddenly unable to post, it may be that your status is still "unconfirmed". If so, please retrieve the email you originally received from the forum system when you registered, and click the confirmation link it contains. If you cannot find that email, you can have the system issue resend one to you.
Second, we have increased the "freeze period" between postings. You will now have to wait two minutes between postings (whether you are posting new discussions or commenting on existing ones). The reason for this is that most spammers want to make several postings in a very short time. If they are made to wait, they give up. This should limit the likelihood that we'll see more spates of a dozen messages at a time, which is what we saw tonight and is particularly obnoxious. Based on the normal forum usage we have seen this should not be a problem for real users. However if you find that this is too stringent, please let us know in this thread.
Thank you for your patience and understanding. As always, we welcome your feedback and suggestions.