-
Notifications
You must be signed in to change notification settings - Fork 21
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
Assigning peptide N- or C-termini labels when calculating mw/mz #50
Comments
Hey there! Sorry for not seeing this before ... but as an alternative you could make a helper function that combines LMK if that would help |
No worries, I found the NTerm- and CTerm-designations in the aaShift function and they seem to work very well. PEPTIDESS: You label for "S = 79.966331", but you are looking for only one phospho group. Labeling on the termini does not work in this case because you do not want to add phospho as a PTM to all your peptides. |
Well in the meantime you could do something like this:
in my experience implementing more than one is kind of tricky and not very prone to vectorization, so we would need to discuss what would be the desired behavior before implementing something. LMK if you have a more specific behavior ... maybe something like ...
That would be easy to implement but I am not sure how useful it would be. |
Those are great options, thank you!
This seems to work quite well, for multiple phosphorylations regardless of aminoacid, a nested ifelse command with counting STY residues within the sequence would be possible as well. |
Hey there!
Awesome package, thank you!
I was wondering if aaShift within mz/mw could be extended for a function to label peptide-termini besides specific aminoacids?
This would be very useful for example when adding labels to the termini of peptides.
In the case of TMT-tags, they would be even cumulative with N-terminus and specific aminoacids such as K (a N-terminal K would carry two TMT-labels, one on the amino group of the free peptide terminus and one on free amino group in the sidechain).
Cheers,
Tobias
The text was updated successfully, but these errors were encountered: