Thanks for sending me the file, I was able to replicate the bug. It has
been fixed in the newest version of Kojak. For those with similar problems,
the newest Kojak can be found here: http://www.kojak-ms.org/download.html
Instructions for manually upgrading your Kojak before the next TPP
I think you found a bug. There is some rare property of a particular
precursor scan in that file that Kojak isn't handling correctly. I'll
probably need access to that particular mzML file to identify the bug. I'll
reach out to you by email.
On Monday, April 6, 2020 at 12:39:33 PM UTC-7,
The screenshot shows all that's in the command-line output sub-window. It
stops while mapping precursors and gives no further diagnostic messages.
Any reasons it would stop running?
On Monday, March 30, 2020 at 1:33:18 PM UTC-7, Luis wrote:
>
> Hi Lindsey,
>
> It seems that Kojak did not finish
Hi Lindsey,
It seems that Kojak did not finish successfully, and it may be the reason
why there is no output file. If you scroll down in the command-line output
sub-window (the one in your screenshot, just scroll down more), you should
be able to see diagnostic messages that may be helpful in
Hi,
I've run Kojak with the same settings on other data files with no problem,
but for some reason with this particular data file I keep getting the error
that the pep.xml file cannot be found and am not sure why this one file
would be different.
Thanks!
Lindsey
--
You received this message
