Dear David,
Thank you for providing your suggestions. I implemented your advice by
including all variable modifications in the search, and the warning
messages did not appear.
I appreciate your assistance.
Sincerely,
Longping
在2023年11月17日星期五 UTC-5 20:49:25 写道：
> Thanks Longping, I got
Thanks Longping, I got your files.
> On Nov 17, 2023, at 5:21 PM, Longping Fu wrote:
>
> Dear David,
>
> I appreciate your swift response. I've compressed the pepXML and mzML files
> and uploaded them to Google Drive. You can access them through the following
> link:
>
Dear David,
I appreciate your swift response. I've compressed the pepXML and mzML files
and uploaded them to Google Drive. You can access them through the
following link:
https://drive.google.com/file/d/1P463uxdvw67ZI7axiZO1OZOIlEZZg5qh/view?usp=sharing
Kindly confirm if you can successfully
Dear Longping,
Maybe you can compress your analysis pepXML and mzML files and post them
somewhere so I can replicate the issue locally?
Meanwhile, you can try the specifying all variable mods used in the search,
when you run PTMProphet by changing the modification string as follows:
I am currently working with PTMProphet in TPP version 6.3.3 for PTM
localization. While PTMProphet successfully completes the task, I am
encountering a significant number of warning messages in the console.
To provide some context, my workflow involves utilizing MSFragger as the
search engine
