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

LFQ-phospho - sequence #1649

Open
ghost opened this issue Jun 26, 2024 · 2 comments
Open

LFQ-phospho - sequence #1649

ghost opened this issue Jun 26, 2024 · 2 comments
Assignees

Comments

@ghost
Copy link

ghost commented Jun 26, 2024

Will you be able to extract the sequence window more flexibly? Could you get the predicted phosphosite in the middle of the window, so we can get the sequence of both the N and C terminus sides? I am using combined_site_STY_79.9663.tsv, and the Peptide column provides sequence, but the the length of the sequence varies between sites too.

@fcyu
Copy link
Member

fcyu commented Jun 26, 2024

What if there are two phospho in the peptide?

Thanks,

Fengchao

@fcyu fcyu self-assigned this Jun 26, 2024
@ghost
Copy link
Author

ghost commented Jun 26, 2024

Hi Fengchao,

I am working on PhosR to examine kinase-substrate relationship using combined_site_STY_79.9663.tsv. I thought we still know which site based on the localization score even if you have two phospho in the peptide?

They said; "Sequence window: A character vector denoting the sequence window, typically of 15–31 in
length. The residues in the sequence window should be capitalized. Note that the predicted phosphosite should reside in the middle of the window. Any phosphosites that are found near the N or C terminus of the protein will require a placeholder (i.e., add ‘‘_’’ to either side of the flanking sequence) to position the phosphosite in concern at the middle of the sequence win- dow (Most processing software will do this for you automatically)."

The sequence window shown in combined_site_STY_79.9663.tsv might not be suitable for this analysis.

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

1 participant