Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Investigate whether our default validation stringency for reads should be STRICT rather than SILENT #1457

Open
droazen opened this issue Jan 28, 2016 · 0 comments
Open

Investigate whether our default validation stringency for reads should be STRICT rather than SILENT #1457

droazen opened this issue Jan 28, 2016 · 0 comments
Labels
Engine question

Comments

@droazen
Copy link
Contributor

droazen commented Jan 28, 2016

Currently our default reads validation stringency as defined in GATKTool is SILENT -- should it be STRICT, or is STRICT too impractical/annoying for read-world data?

Prompted by a discussion in #1439
@droazen droazen added this to the beta milestone Jan 28, 2016
@droazen droazen removed this from the beta milestone Mar 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Engine question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@droazen