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.

Sign up for GitHub

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

Jump to bottom

[DOC] Add changelog entry for #2458 #2495

Merged
merged 2 commits into from
Mar 25, 2021
Merged

[DOC] Add changelog entry for #2458 #2495

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
307f634
[DOC] Add changelog entry for #2458
eseiler Mar 24, 2021
6f27c2e
Update CHANGELOG.md
eseiler Mar 25, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
13 changes: 11 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,15 @@ If possible, provide tooling that performs the changes, e.g. a shell-script.
* Requesting the alignment without also requesting the sequence for BAM files containing empty CIGAR strings does now
not result in erroneous parsing ([\#2418](https://github.com/seqan/seqan3/pull/2418)).
* BAM files with 64 references are now parsed correctly ([\#2423](https://github.com/seqan/seqan3/pull/2423)).
* Writing `gz`-compressed output no longer results in `bgzf`-compressed output. This change may have following effects
([\#2458](https://github.com/seqan/seqan3/pull/2458)):
* A noticeable slowdown when writing `gz`-compressed content since, in contrast to `bgzf`, `gz` does not feature
parallelisation (magnitude depends on the application and level of parallelisation).
* A reduced output size when writing `gz`-compressed content due to `gz` storing less metadata than `bgzf`
(up to 20% smaller file size).
* The processed data should experience no negative effects since `gz` and `bgzf` are **fully compatible**.
* This bug may also cause unexpected parallelisation when reading `gz`-compressed input. This is the case when the
`gz`-compressed input was also generated with SeqAn.

## API changes

Expand Down Expand Up @@ -174,8 +183,8 @@ If possible, provide tooling that performs the changes, e.g. a shell-script.
#### Search

* We removed the concepts seqan3::[bi_]fm_index[_cursor]_specialisation. We did this because we currently have only one
implementation modelling each concept and are not completely sure if the current definition of the concepts is the
right one. If you used those concepts, you can check whether the cursor type is seqan3::[bi_]fm_index_cursor as a
implementation modelling each concept and are not completely sure if the current definition of the concepts is the
right one. If you used those concepts, you can check whether the cursor type is seqan3::[bi_]fm_index_cursor as a
substitute. ([\#2348](https://github.com/seqan/seqan3/pull/2348))

# 3.0.2
Expand Down