Perhaps you could upload the .dat file to ftp://insilicos.serveftp.net/pub
and I can investigate.  Zip it up with the database you used, and the mzXML
file (so, everything needed to run xinteract).

Brian

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of andreas quandt
Sent: Friday, July 10, 2009 12:52 AM
To: [email protected]
Subject: [spctools-discuss] Re: parsing error for pepXML from mascot result


hey brian,

its 4.2.1 in that case ;-)


Brian Pratt wrote:
> What version of the software are you using?  
>
> Brian
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of andreas quandt
> Sent: Thursday, July 09, 2009 5:50 AM
> To: [email protected]
> Subject: [spctools-discuss] parsing error for pepXML from mascot result
>
>
> dear list,
>
> i analyzed a few samples with mascot and converted the dat file 
> successfully to pepXML (only error: scan number cannot be found).
> afterwards i was running xinteract on all created pep.xml files 
> (arguments:  l -dDECOY_ -OAlIwp).
> this was also successful but when i want to display the results, i get 
> an error message:
>
> unable to read pepxml file: error parsing pepxml file: XML parsing 
> error: mismatched tag, at xml file line 1048198, column 2
>
> when looking at the file, the line contains following tag: </search_hit>.
> the same happens when using iprophet. here the error message is the same 
> and when jumping to the indicated line, the same tag appears.
>
> does anyone of you know what's going wrong and/or know how to fix this?
>
> many thanks in advance,
> andreas
>
>
>
>
> >
>   





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"spctools-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/spctools-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to