Hi all,

I am trying to use SearchGUI to manage the parameters of different search 
engines, and collect pepxml files for TPP components.

Based on my test, comet and omssa seem to work seamlessly.  Results from 
X!Tandem, Myrimatch, MSGF+ and Tide all has some problems to work with 
xinteract.

I am trying to check the pepxml files one by one, and it seems the problem 
arises from the attribute "spectrumNativeID" in <spectrum_query>.

myrimatch and msgf+ give results like <spectrum_query spectrum="****", 
spectrumNativeID="index=xxx" ...>
xtandem's result is even more weird:
 <spectrum_query spectrum="00631_A10_P004781_B00A_A00_R1.4025.4025.2 
File:"00631_A10_P004781_B00A_A00_R1.raw", NativeID:"controllerType=0 
controllerNumber=1 scan=4025" RTINSECONDS=1303.9596" start_scan="2778" 
end_scan="2778" precursor_neutral_mass="1044.5541" assumed_charge="2" 
index="984" retention_time_sec="1303.9596">
This information seems to come from <Note label="Description"> in t.xml 
file before using Tandem2XML.

Once I remove the attribute of "spectrumNativeID", xinteract can run and 
complete the job. I am just wondering if this way affects the results of 
xinteract.  And for XTandem, can I simply remove the <Note 
label="Description">?

Thanks,

-Han


-- 
You received this message because you are subscribed to the Google Groups 
"spctools-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/spctools-discuss.
For more options, visit https://groups.google.com/d/optout.

Reply via email to