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

"Specific only" broken or misleading #22

Closed
heuselm opened this issue Jan 16, 2019 · 2 comments
Closed

"Specific only" broken or misleading #22

heuselm opened this issue Jan 16, 2019 · 2 comments

Comments

@heuselm
Copy link

heuselm commented Jan 16, 2019

Dear pFind team,

Some peptides are erroneously labeled as specific, even though they map to multiple entries in the .fasta reference sequence database. Specific should (I assume) indicate proteotypicity which, in the context of the considered sequence space, means mapping to one parent sequence (AC) only.

I noticed a bug when visualizing results, specifically protein sequence view with aligned detected peptides. Limiting the view to "only specific" leaves peptides in the view which map to and may have originated from multiple different parent sequences (ACs).

This is highly misleading as to the quality and frequency of evidence for a target protein of interest.
Hope you can make this a high priority bug fix.

Best,
mh

image

@jalew188
Copy link

jalew188 commented Jan 26, 2019

@heuselm "Specific Flag" = "S" means it is a specifically digested peptide, not for proteins.

@heuselm
Copy link
Author

heuselm commented Mar 23, 2019

Alright, thanks for the clarification.
I would have anticipated specificity to stand for specificity of a peptide sequence for the given protein entry, which is often of interest.
Therefore, please consider it a feature suggestion - It would be nice to remove non-proteotypic peptides (that could also have been generated from another protein entry in the .fasta) for visualization purposes (Especially the nice sequence alignments!).
Thanks & best,
Moritz

@heuselm heuselm closed this as completed Mar 23, 2019
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