Brian
my apologies, the pepXML file was indeed broken. Mascot2XML took a
FASTA entry like
>tr|A0N7J4|V6-N-D-N-J1.1 protein (Fragment) Tax_Id=9606
>[Homo sapiens]
Into
Which breaks the pepXML viewer, and I imagine xinteract.
We have a version of Mascot2XML from TPP v4.3. Is there a more rec
Brian,
the pepXML was created using Mascot2XML. The pepXML file that was
input to xinteract does not contain the entry
"tr|Q78E99|MRXR"
My understanding is that xinteract opens the database mentioned in the
pepXML file to extract information.
Regards
Simon Michnowicz
On Apr 16, 1:09 am, Brian
The defect is really somewhere upstream - whatever created the pepxml files
that went into xinteract should have escaped those characters.
On Wed, Apr 14, 2010 at 11:25 PM, Simon Michnowicz <
simon.michnow...@gmail.com> wrote:
> Dear Group,
> I am running a Peptide Prophet search but xinteract br
Hi DT,
Thank you very much for the great suggestion.
I have not tried OMSSA too much. I will try to use these two software
and ASAPRatio for the quantification.
By the way, do you have any publications which described the way you
did the quantification?
As for Mascot, recently, I kind of detect
