Improvements to DuplexMaker and ConsensusMaker.

[nh13]

• Remove output BAM from DuplexMaker and fixing up Docs.
• Ensure read names are unique across DCSs.
• Read name collisions are possible, although unlikely, across DCSs. This can occur when two DCSs with the same Duplex Tags are found; their respective SSCSs and raw reads map to different genomic locations.
• Fixing up duplex barcode collisions. See: https://github.com/loeblab/Duplex-Sequencing/issues/33

[nh13]

@loeblab how do I go about testing this? I would be happy to contribute a .travis.yml if that would help if you have tests somewhere? https://travis-ci.org/

[scottrk]

I haven't the faintest clue how that works, but I'm certainly happy make your contributions easier. I've signed up with travis-ci.

On 4/15/16 5:16 PM, Nils Homer wrote:

@loeblab https://github.com/loeblab how do I go about testing this? I would be happy to contribute a |.travis.yml| if that would help if you have tests somewhere? https://travis-ci.org/

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/loeblab/Duplex-Sequencing/pull/35#issuecomment-210694442

[nh13]

@loeblab if you have a test dataset or two with expected outputs that run end-to-end in a reasonable amount of time (a few minutes), I can have them run, check that they produce the expected output, then pass or fail. This would all be run by the travis-ci service for every pull request.