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

[FIX] Wrong alignment score #3043 #3098

Merged
merged 1 commit into from
Nov 14, 2022

Conversation

rrahn
Copy link
Contributor

@rrahn rrahn commented Nov 7, 2022

Resolves #3043

Added carry bit to up and left open trace directions in order to capture original open signal even if it is overwritten by the orhtogonal direction. In the particular issue the left extension overwrites the up Open signal in the last column and fifth row. The traceback now follows the vertical or horizontal direction unitl it encounters the carry bit signal.

@vercel
Copy link

vercel bot commented Nov 7, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
seqan3 ✅ Ready (Inspect) Visit Preview Nov 14, 2022 at 11:49AM (UTC)

@seqan-actions seqan-actions added lint [INTERNAL] signal for linting and removed lint [INTERNAL] signal for linting labels Nov 7, 2022
@rrahn rrahn mentioned this pull request Nov 7, 2022
2 tasks
@rrahn rrahn requested review from a team and Irallia and removed request for a team November 7, 2022 18:01
@seqan-actions seqan-actions added lint [INTERNAL] signal for linting and removed lint [INTERNAL] signal for linting labels Nov 7, 2022
@codecov
Copy link

codecov bot commented Nov 7, 2022

Codecov Report

Base: 98.22% // Head: 98.22% // Decreases project coverage by -0.00% ⚠️

Coverage data is based on head (6e23815) compared to base (4961904).
Patch coverage: 96.15% of modified lines in pull request are covered.

❗ Current head 6e23815 differs from pull request most recent head 4fe5489. Consider uploading reports for the commit 4fe5489 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3098      +/-   ##
==========================================
- Coverage   98.22%   98.22%   -0.01%     
==========================================
  Files         275      275              
  Lines       12181    12192      +11     
==========================================
+ Hits        11965    11975      +10     
- Misses        216      217       +1     
Impacted Files Coverage Δ
...eqan3/alignment/matrix/detail/trace_directions.hpp 100.00% <ø> (ø)
.../seqan3/alignment/pairwise/alignment_algorithm.hpp 99.40% <92.85%> (-0.60%) ⬇️
...n3/alignment/matrix/detail/trace_iterator_base.hpp 100.00% <100.00%> (ø)
.../detail/policy_affine_gap_with_trace_recursion.hpp 100.00% <100.00%> (ø)
...n3/alignment/pairwise/policy/affine_gap_policy.hpp 100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@rrahn rrahn changed the title [FIX] Alignment Wrong alignment score #3043 [FIX] Wrong alignment score #3043 Nov 7, 2022
@@ -18,8 +18,8 @@ static constexpr seqan3::detail::trace_directions N = seqan3::detail::trace_dire
static constexpr seqan3::detail::trace_directions D = seqan3::detail::trace_directions::diagonal;
static constexpr seqan3::detail::trace_directions u = seqan3::detail::trace_directions::up;
static constexpr seqan3::detail::trace_directions l = seqan3::detail::trace_directions::left;
static constexpr seqan3::detail::trace_directions U = seqan3::detail::trace_directions::up_open;
static constexpr seqan3::detail::trace_directions L = seqan3::detail::trace_directions::left_open;
static constexpr seqan3::detail::trace_directions U = seqan3::detail::trace_directions::carry_up_open;
Copy link
Member

Choose a reason for hiding this comment

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

Changes as to not need to touch every test

: (best_trace |= previous_cell.horizontal_trace(), diagonal_score);
diagonal_score =
(diagonal_score < horizontal_score)
? (best_trace = previous_cell.horizontal_trace() | (best_trace & trace_directions::carry_up_open),
Copy link
Member

Choose a reason for hiding this comment

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

(best_trace & trace_directions::carry_left_open) is not needed in the above (L 79) case, because the horizontal trace is always set

Copy link
Contributor

@Irallia Irallia left a comment

Choose a reason for hiding this comment

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

Thx for resolving this issue!
I just had some reading problems. Decide yourself if it makes sense to change it.

Added carry bit to up and left open trace directions in order to capture original open signal even if it is overwritten by the orhtogonal direction.
In the particular issue the left extension overrites the up open signal in the last column and fifth row.
The traceback now follows the vertical or horizontal direction unitl it encounters the carry bit signal.
@seqan-actions seqan-actions added lint [INTERNAL] signal for linting and removed lint [INTERNAL] signal for linting labels Nov 14, 2022
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.

[Alignment] Wrong alignment score
4 participants