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

output_sequence1_id and output_sequence2_id are same #3205

Open
Jappy0 opened this issue Nov 8, 2023 · 4 comments
Open

output_sequence1_id and output_sequence2_id are same #3205

Jappy0 opened this issue Nov 8, 2023 · 4 comments
Assignees
Labels
bug faulty or wrong behaviour of code

Comments

@Jappy0
Copy link

Jappy0 commented Nov 8, 2023

Hi there,

Thanks so much for this excellent C++ library for bioinformatics. I had a question when I was using it; please have a look at the following,

Platform

  • SeqAn version: <seqan3.3.0 conda>
  • Operating system:
  • Compiler: <gcc 13.20>

Question

I used the following configurations to get pairwise alignment from a vector. I found the output pairwise sequence id-1 and id-2 are the same. Is this problem a bug?

#include <seqan3/alignment/pairwise/align_pairwise.hpp>
#include <seqan3/alphabet/nucleotide/dna4.hpp>
#include <seqan3/core/debug_stream.hpp>
#include <seqan3/utility/views/pairwise_combine.hpp>

int main()
{
    using namespace seqan3::literals;

    std::vector vec{"ACGTGACTGACT"_dna4, "ACGAAGACCGAT"_dna4, "ACGTGACTGACT"_dna4, "AGGTACGAGCGACACT"_dna4};

    auto config = seqan3::align_cfg::method_global{} | seqan3::align_cfg::edit_scheme | seqan3::align_cfg::min_score{-7}
                | seqan3::align_cfg::output_score{} | seqan3::align_cfg::output_sequence1_id{}
                | seqan3::align_cfg::output_sequence2_id{};

    auto alignment_results = seqan3::align_pairwise(seqan3::views::pairwise_combine(vec), config);
    auto filter_v = std::views::filter(
        [](auto && res)
        {
            return res.score() >= -6;
        });

    for (auto const & result : alignment_results | filter_v)
        seqan3::debug_stream << result << '\n';

    // {sequence1 id: 0, sequence2 id: 0, score: -4}
    // {sequence1 id: 1, sequence2 id: 1, score: 0}
    // {sequence1 id: 3, sequence2 id: 3, score: -4}
}

Thanks for your time.

Best regards,

Jappy

@Jappy0 Jappy0 added the question a user question how to do certain things label Nov 8, 2023
@rrahn rrahn self-assigned this Nov 8, 2023
@SGSSGene
Copy link
Contributor

SGSSGene commented Nov 8, 2023

Hi Jappy0

Thank you for your report. There is indeed a design flaw in the align_pairwise method. It is not possible for it to report sequence ids. Instead it is reporting the index of the alignment-pair.
We are discussing a solution.

For you to continue working, you need to create a list which does the same mapping as seqan3::views::pairwise_combine(vec) for indices and then convert it to the real sequence ids.

Here a detailed adjustment of your final for loop:

    // Create a mapping, that maps from alignment-pair-ids → sequence-ids
    auto pair_indices = seqan3::views::pairwise_combine(std::views::iota(0ul, vec.size()));
    for (auto const & result : alignment_results | filter_v)  {
        seqan3::debug_stream << result << '\n';

        // The sequence1_id is reporting the index of the alignment-pair, not the ids of the pairs them self
        auto alignment_id = result.sequence1_id(); // result.sequence1_id() == result.sequence2_id()

        auto [sid1, sid2] = pair_indices[alignment_id]; // alignment-pair-id -> sequence-id
        seqan3::debug_stream << "sid1: " << sid1 << "; sid2: " << sid2 << "\n"; // the real sequence ids
    }

I will keep this issue open, until we have some kind of proper solution in seqan

@eseiler
Copy link
Member

eseiler commented Nov 8, 2023

Here's a godbolt link showing both versions: https://godbolt.org/z/q6dMYajef

@Jappy0
Copy link
Author

Jappy0 commented Nov 8, 2023

Here a detailed adjustment of your final for loop:

Hi Simon,

I see, thanks so much for the quick solution.

@Jappy0
Copy link
Author

Jappy0 commented Nov 8, 2023

Here's a godbolt link showing both versions: https://godbolt.org/z/q6dMYajef

Hi Enrico, Thanks so much for the examples.

@SGSSGene SGSSGene added bug faulty or wrong behaviour of code and removed question a user question how to do certain things labels Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug faulty or wrong behaviour of code
Projects
None yet
Development

No branches or pull requests

4 participants