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.

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

Does this tool take in fully-processed bams as input or unprocessed bams? #9

Open
claudiadast opened this issue Sep 19, 2018 · 0 comments

Comments

@claudiadast
Copy link

claudiadast commented Sep 19, 2018

When running bamhash on a bam file, should the bam be fully processed (i.e. sorted, deduped, and recalibrated)?

I just tested bamhash on a fully-processed bam file and its source paired-end fastq files, however the resulting hashes differ, so I'm wondering if it's because the input bam was fully processed.

UPDATE:

I just re-ran bamhash on a non-fully processed bam file, and got the following results:

bam result:
2490f971d6f15fa2	764438888

source fastq result:
2490f971d6f15fa2	382219444

What do the two columns represent? Is it enough that one of the columns match between the files?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant