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

Some N-terminal acetylations are not N-terminal #748

Closed
ndtivendale opened this issue Jul 1, 2022 · 2 comments
Closed

Some N-terminal acetylations are not N-terminal #748

ndtivendale opened this issue Jul 1, 2022 · 2 comments

Comments

@ndtivendale
Copy link

ndtivendale commented Jul 1, 2022

Protein N-terminal acetylation was included in my search as a variable modification. For most of the psms, the N-terminal acetylation is mapped to the first or second residue of the protein, which makes sense since I checked the box to 'Clip N-term M.' However I am finding a small number of psms with 'N-terminal' aceylations that are not mapped to the first or second residue of the protein. If these peptides are not mapped to the N-terminal end of their proteins, how can they be N-terminally acetylated? Why is this happening and how can I stop it? You can see the problem in the attached example output file.
Note, that I used '[^' to specify protein N-terminal acetylation in MSFragger.

psm_000_1.xlsx

@ndtivendale
Copy link
Author

I am not sure why that text came out so big! Sorry.

@fcyu
Copy link
Member

fcyu commented Jul 1, 2022

Seems to be the same one as #718

Can you check if those peptides can be mapped to another protein, which makes it N-term Acetylation?

Best,

Fengchao

@fcyu fcyu closed this as completed Jul 7, 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

No branches or pull requests

2 participants