Closed chrishuges closed 4 years ago
Hi Chris,
I just tried with a 10-plex TMT dataset and did not see any such issues. I don't have any 11- or 16-plex datasets available though, so would it be possible for you to share these so that I can try to locate the problem? You can send them directly to me at harald.barsnes@gmail.com.
Best regards, Harald
Hi again,
One thing I note is that you are using a fragment ion accuracy of only 0.5 ppm. Is this in purpose? Perhaps you can try with something like 0.02 Da?
Best regards, Harald
Hi Harald,
Ah, that was silly of me. You are correct, the fragment mass error was too small because it was set to ppm. Was this default as 'Da' in previous releases? I don't remember having to specify it as such before. In any case, it is working fine now.
Thanks for looking at that. Chris
Hi Chris,
Yes, I think the default was Dalton in the previous releases. Not sure why it was changed. But great to hear that you were able to get it to work.
Best regards, Harald
Hi,
I am having an odd issue in version 4.0.0 of SearchCLI/PeptideShaker 2.0.0. Basically, if I search a file with TMT labeling, I get zero, or very close to zero hits in the output files. If I search a normal, unlabeled analysis file, I have no problems and the result looks good.
I have tried this with files from TMT 11-plex and 16-plex labeled samples. In the case of the 11-plex samples, these give good results in the previous versions of SearchCLI. I have tried putting the peptide N-terminal label in the fixed or variable spots, and it doesn't make a difference (TMT on K is always variable).
There are no errors in either the SearchCLI or PeptideShakerCLI log files. I have tried this with XTandem and Comet and had the same result with both.
Example XTandem output:
Example Comet output:
The modifications file looks OK to me:
Any idea what might be happening here?
Thanks, Chris