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

CRAM queryUnmapped returns incorrect values with recordPerSlice=2000 #562

Closed
cmnbroad opened this issue Apr 9, 2016 · 1 comment
Closed
Labels

Comments

@cmnbroad
Copy link
Collaborator

cmnbroad commented Apr 9, 2016

I used a large BAM file, converted to CRAM and compared the number of records returned from unmappedQuery:

BAM: 50,000 records
CRAM converted using samtools defaults: 50,000 records
CRAM converted using htsjdk: 50,000 records
CRAM converted using samtools, seqs_per_slice=2000: 65501 records

The file I used is too big to add as a test case, so we'll need to dig deeper to find out if the problem originates in the cram file, index generation, crai->bai conversion, or htsjdk query implementation.

@cmnbroad
Copy link
Collaborator Author

Closed via #552.

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

No branches or pull requests

1 participant