Skip to content

Conversation

@sarahet
Copy link
Member

@sarahet sarahet commented Nov 18, 2022

This PR includes #194 and #191 and adds nucleotide profiles as well as updated tests matching changes in index and the search default settings.

@sarahet sarahet requested a review from h-2 November 18, 2022 14:46
@sarahet
Copy link
Member Author

sarahet commented Nov 18, 2022

@h-2 Do we want tests for the different profiles? I didn't think it was necessary given that we also don't test all other parameters so I did not add them but let me know if you think differently

int32_t minBitScore = 42;
double maxEValue = -1;
int32_t idCutOff = 0;
uint64_t maxMatches = 256;
Copy link
Member

Choose a reason for hiding this comment

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

I forgot to change this to 25

Copy link
Member

Choose a reason for hiding this comment

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

This means you need to recreate the search test files I am afraid...

Copy link
Member Author

Choose a reason for hiding this comment

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

No problem

{
if (options.nucleotide_mode)
{
options.iterativeSearch = false;
Copy link
Member

Choose a reason for hiding this comment

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

I thought we came to the conclusion that the iterativeSearch is always beneficial, or did we not find a good parameter-pair for nucleotide+fast?

Copy link
Member Author

Choose a reason for hiding this comment

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

We did not find a good pair and you suggested to pick one of the search0 candidates as regular search for fast.

int32_t minBitScore = 42;
double maxEValue = -1;
int32_t idCutOff = 0;
uint64_t maxMatches = 256;
Copy link
Member

Choose a reason for hiding this comment

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

This means you need to recreate the search test files I am afraid...

// "Size of the DP-band used in extension (-3 means log2 of query length;"
// " -2 means sqrt of query length; -1 means full dp; n means band of size 2n+1)",
// seqan3::option_spec::advanced,
// seqan3::arithmetic_range_validator{-3, 1000});
Copy link
Member

Choose a reason for hiding this comment

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

If nothing uses this, I would propose to remove it (also the option itself). No point in carrying around more legacy codepaths.

Copy link
Member Author

Choose a reason for hiding this comment

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

I guess depends if we ever want to introduce it again, that's why I left it. But we can remove it, just wanted to check.

Copy link
Member

Choose a reason for hiding this comment

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

If we add it again, we can also add the option back. Considering other people (including future-me), I think it's better to reduce the amount of commented-out code!

@h-2
Copy link
Member

h-2 commented Nov 24, 2022

Do we want tests for the different profiles? I didn't think it was necessary given that we also don't test all other parameters so I did not add them but let me know if you think differently

I don't think it would hurt to have at least some tests for the other profiles. Even if we don't test all options/combinations, testing the advertised ones gives us a better coverage.

@sarahet
Copy link
Member Author

sarahet commented Nov 27, 2022

Even if we don't test all options/combinations, testing the advertised ones gives us a better coverage.

Should we test m8 and sam with unidirectional index for fast and sensitive?

@h-2
Copy link
Member

h-2 commented Nov 28, 2022

Should we test m8 and sam with unidirectional index for fast and sensitive?

Sounds good!

@h-2 h-2 merged commit a79d2cf into seqan:lambda3 Nov 28, 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.

3 participants