While I was fixing it, I noticed that we weren't allowing the cleaner to un-clean reads with indels when they're wrong even though we should. Hypothetically, that should rarely happen: only when we can left-align out an indel or when the original mapper really went haywire. This situation is rare enough that I'm calling logger.info to let the user know it's happening and suggesting that they double-check that everything looks right with their reads. Better to be extra-cautious now that the cleaner is moving into the 1kg and Broad production pipelines soon . Mark, have no fear: this was truly a rare edge case - one that won't affect the cleaning stats. There is no need to re-clean the data processing paper bams! git-svn-id: file:///humgen/gsa-scr1/gsa-engineering/svn_contents/trunk@4057 348d0f76-0448-11de-a6fe-93d51630548a |
||
|---|---|---|
| R | ||
| archive | ||
| c | ||
| doc | ||
| java | ||
| matlab | ||
| packages | ||
| perl | ||
| python | ||
| ruby | ||
| scala | ||
| settings | ||
| shell | ||
| testdata | ||
| LICENSE | ||
| build.xml | ||
| ivy.xml | ||