-
Notifications
You must be signed in to change notification settings - Fork 46
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
Unspecific HLA datasets #99
Comments
One more questions is the calculated mass including the modifications or with out them ? |
Hi Karim, The process is killed due to lack of RAM - fragment indexing requires the pre-generation of every single b/y ion for every peptide in the search space... This gets quite large for unspecific searches! I am going to refer you to #97 (comment) where a work-around python script is presented for splitting a FASTA file into chunks (reducing the search space) and running Sage multiple times. For decoy generation, decoy sequences that also appear in the target database are removed - so a peptide should never be shared across both decoy proteins and a target protein. If you find a case where this happens, please let me know since it is a bug. Calculated mass includes any specified variable or static mods present in the peptide sequence, but will not include any open modification search masses. |
Thank you so much for your help. Regarding the peptide sequence shared between proteins, I checked earlier today, and didn't find such an occurrence. |
Hello Michael,
I had an issue trying to use sage with HLA datasets. I want the cleavage to be unspecific, which based on the documentation it should be left empty. The process is killed afterwords.
Another thing is the generation of decoys. In the protein column is it possible to have a peptide that is occurring in say two decoy proteins and one target ? Thanks in advance.
Best,
Karim Abdelfattah
The text was updated successfully, but these errors were encountered: