-
Notifications
You must be signed in to change notification settings - Fork 0
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
CPTAC MS dataset files in s3 bucket are not found #75
Comments
For a given peptide precursor (a combination of peptide sequence, charge and modification), if there is no any spectra matched from the query, it will print out something like "*.mgf doesn't exist". This is not an error message from the search. |
It’s quite common for some peptides not to have any spectra matched in a query |
Thanks for the reply |
May I know is there a way to query multiple protein sequences as in a single input file in the stand alone version? It seems that only multiple peptides query in a single input file is supported now. |
Yes, you could put your protein sequences in a FASTA format file like the one below and then set parameter as "-i target_proteins.fasta -t protein -s 1". This only works for novel protein search not known protein search. target_proteins.fasta :
|
Thanks, that helps a lot. May I ask how to say a protein search result is confident or not? By looking at the pepquery result, the psm_rank.txt is reported at the peptide level. Is there any downstream analysis required for the novel protein identification? |
We have some description at http://pepquery.org/document.html#saoutput to show how to interpret the result in the psm_rank.txt file, such as how a match is considered as confident in a query. |
Hi, thanks for creating this tool. But recently when I use pepquery2 in web application and stand alone version, there was error about the mgf file in s3 bucket is not exist. I attached the screenshot of the error on web application.
My input peptide is
MAEASPHPGRYFCHCCSVEIVPRLPIISVQDASLVLSRSFRKRPEHRKWFCPLHSSHRPEPATVGHVDQHLFTLPQGYGQFAFGIFDDSFEIPTFPPGAQADDGRDPESRRERDHPSRHRYGARQPRARLTTRRATGRHEGVPTLEG
The text was updated successfully, but these errors were encountered: