compomics / peptide-shaker

Interpretation of proteomics identification results
http://compomics.github.io/projects/peptide-shaker.html
48 stars 19 forks source link

Failed to put two fixed modifications #498

Closed KKKKK-tech closed 1 year ago

KKKKK-tech commented 1 year ago

When I using SearchGUI, I added the TMT10plex to the fixed modification. But when I run out.zip with PeptideShaker, following error occurred. How can I solve this problem?

O@A5WONV%ERBPR)DKJ4F73Y

hbarsnes commented 1 year ago

Thanks for letting us know. A fix is in progress, but I cannot at the moment tell you when it will be included in an official new release as it requires a lot more testing first. Perhaps @mvaudel could provide you with a beta version to test?

KKKKK-tech commented 1 year ago

Thanks for your reply. Looking forward to the new release! : )

mvaudel commented 1 year ago

Hi, Sorry for the delay. Would you have more information on how the search parameters were designed? It seems that you are using two fixed modifications targeting lysine which is not allowed. You can add only one modification per amino acid. When using TMT please use one modification for all tags, and add the different reporter ions in the modification details. For TMT 10-plex I would recommend using the modification definition available in SearchGUI. Hope it helps, Marc

KKKKK-tech commented 1 year ago

Hi, It's my problem and I've solved it after following your advice, thanks!

When using TMT please use one modification for all tags, and add the different reporter ions in the modification details

BTW, I encountered the same problem with #450, and it does not seem to work even though I increased the memory to 128G. My database is concatenated target-decoy human protein, which is about 26M, and the search_output.zip of comet is about 300M. Could you give me some suggestions to solve this problem avoid increasing memory? Thank you!

hbarsnes commented 1 year ago

It's my problem and I've solved it after following your advice, thanks!

Great! I will then close this issue. But do not hesitate to open a new one if you come across other problems.

BTW, I encountered the same problem with https://github.com/compomics/peptide-shaker/issues/450, and it does not seem to work even though I increased the memory to 128G. My database is concatenated target-decoy human protein, which is about 26M, and the search_output.zip of comet is about 300M. Could you give me some suggestions to solve this problem avoid increasing memory?

The only other option is to try turning off the parallel processing. You can do this from the New Project dialog by setting the Processing option at the bottom to only use 1 core. Note however that this will make the processing significantly slower.