Skip to content

[Fix] Get correct number of header entries for subject sequences#156

Merged
h-2 merged 1 commit intoseqan:masterfrom
sarahet:fix_bam_header
Jan 30, 2020
Merged

[Fix] Get correct number of header entries for subject sequences#156
h-2 merged 1 commit intoseqan:masterfrom
sarahet:fix_bam_header

Conversation

@sarahet
Copy link
Copy Markdown
Member

@sarahet sarahet commented Jan 30, 2020

For translated databases, the number of original sequence lengths was used to determine the header entries. The last entry of the original sequence lengths is however the sum, so one empty header line was accidentally created in this case.

@sarahet sarahet requested a review from h-2 January 30, 2020 04:58
Copy link
Copy Markdown
Member

@h-2 h-2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but does this intentionally only target the master branch (lambda2)?

@sarahet
Copy link
Copy Markdown
Member Author

sarahet commented Jan 30, 2020

LGTM, but does this intentionally only target the master branch (lambda2)?

Yes, only a problem in lambda2 as we directly access the sequences and not a length vector in lambda3. In lambda3 is a different bug in the bam header, though, that will be fixed by #157.

@h-2 h-2 merged commit 52fd0bb into seqan:master Jan 30, 2020
@h-2
Copy link
Copy Markdown
Member

h-2 commented Jan 30, 2020

Note that we have increasing divergence between the branches. At some point, this needs to be synchronised again.

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

Successfully merging this pull request may close these issues.

2 participants