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

typo fixes #5763

Merged
merged 6 commits into from
Jan 26, 2022
Merged

typo fixes #5763

merged 6 commits into from
Jan 26, 2022

Conversation

cbielow
Copy link
Contributor

@cbielow cbielow commented Jan 25, 2022

Description

X!Tandem's Protein-N-terminal cleavage rules are more flexible than OpenMS' PeptideIndexer allows for.
More specifically, ANY aminoacid (not just 'M') can be cleaved off the protein n-terminus.
This PR makes the behaviour consistent with how X!Tandem calls peptides.

fixes #5755

How can I get additional information on failed tests during CI:

If your PR is failing you can check out

Note:

  • Once you opened a PR try to minimize the number of pushes to it as every push will trigger CI (automated builds and test) and is rather heavy on our infrastructure (e.g., if several pushes per day are performed).

Advanced commands (admins / reviewer only):

  • /rebase will try to rebase the PR on the current develop branch.
  • /reformat (experimental) applies the clang-format style changes as additional commit
  • setting the label NoJenkins will skip tests for this PR on jenkins (saves resources e.g., on edits that do not affect tests)

@timosachsenberg
Copy link
Contributor

looks simple enough. @jpfeuffer any objections?

@jpfeuffer
Copy link
Contributor

Do we know where it says ANY in Xtandem docs?

@jpfeuffer
Copy link
Contributor

Because it could also just consider X since X matches M

@timosachsenberg
Copy link
Contributor

I think I found some code in the X!Tandem source code that skips * and X at the N-terminus of peptides.

while((m_pSeq[lStart] == '*' || m_pSeq[lStart] == 'X') && lStart < m_lStartMax) ...

@jpfeuffer
Copy link
Contributor

Aha! Nice find. Then the PR won't do much good and an extended strategy is required.

@cbielow
Copy link
Contributor Author

cbielow commented Jan 25, 2022

I think I found some code in the X!Tandem source code that skips * and X at the N-terminus of peptides.

Nice find, Timo.
Can you provide a link to the code?!
And why peptides and not protein?

And all I used to implement the fix was the comment from Ron Beavis here #2497 (comment)

Then the PR won't do much good and an extended strategy is required.

Well, it now could lead to some false positives, if truly only 'X' and 'M' are considered by X!Tandem.
The '*' we must not worry about. It is removed before processing in PeptideIndexer.

@timosachsenberg
Copy link
Contributor

sent link on discord

@cbielow cbielow changed the title Xtandem PeptideIndexer fix typo fixes Jan 26, 2022
@timosachsenberg timosachsenberg merged commit 07f980d into OpenMS:develop Jan 26, 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.

Unmatched peptides found by PeptideIndexer in XTandemAdapter
3 participants