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

Merge str harmonization update #153

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion RELEASE_NOTES.rst
Original file line number Diff line number Diff line change
@@ -1,11 +1,18 @@
Unreleased changes
-----

CompareSTR and mergeutils changes:
Functionality Changes:

* MergeSTR: Decision on which records are able to be merged is now based on data from harmonized TRRecords,
and not from the records directly from VCF readers. Thanks to this, HipSTR records which have different starting positions,
but position of their repeat is at the same position are merged correctly. This difference is caused by flanking BP that are
included in the record. These flanking BPs are also removed during the merge, and merged HipSTR records no longer contain them

* CompareSTR: the tool now only compares records that start and end at the same position. If overlap in records is detected,
the program will output a warning to the user. This warning contains IDs of the records and their positions.

Misc:

* mergeutils: function GetMinHarmonizedRecords was transformed into GetRecordComparabilityAndIncrement, which allows the caller
to define custom predicate that decides whether records are comparable.

Expand Down
Loading