I'm not familiar with that error message but possibly your search
didn't run? The .out files should have scores and peptide sequences
in them and not be the same format as the .dta peak lists. If they
are the same, something is wrong.
On Wed, Mar 3, 2010 at 7:08 AM, BIackEye
Hi All,
The output of the Proteome Discover is *.msf. Is there an easy way to
compute peptide prophet from it? Or I have to run sequest.exe to get
*.out to do so?
Thanks!
Ping
--
You received this message because you are subscribed to the Google Groups
spctools-discuss group.
To post to this
unless there's a way to convert .msf to pep.xml, and I'm not aware of
any tool that does this, you'll have to go the .out route.
On Mar 3, 2:18 pm, Ping yanpp...@gmail.com wrote:
Hi All,
The output of the Proteome Discover is *.msf. Is there an easy way to
compute peptide prophet from it? Or
Look up accurate mass and time tags, peptide mass fingerprinting, and
maybe even a general proteomics data analysis review such as doi:
10.1038/nrm1468
I hope you don't take this too negatively but the scope of what one
might consider ms1 data is too general (a peptide mass fingerprint
spectra,
It's a software problem on a couple of levels. ReAdW was never
intended for gcms data so it was never tested on those instruments and
I would be surprised if it worked. Additionally, most if not all of
the software tools that consume mzXML files probably won't work with
the data, even if you
I would advocate trying msconvert to convert to mzML as Jimmy suggests. If
that doesn't work, then we have active leads that could likely fix that.
-Original Message-
From: spctools-discuss@googlegroups.com [mailto:spctools-
disc...@googlegroups.com] On Behalf Of Jimmy Eng
Sent:
Hi Zhang,
As Jimmy pointed out, identification from MS1 level data is too general to
be considered conclusive evidence, although it provides a fast way of
identifying (potential) peptides. The amount of information in MS1 is too
low to draw conclusions. MS2 has peptide fragments (as opposed to
