MzIdentML incorrect

37 views
Skip to first unread message

Andrew Collins

unread,
Jan 22, 2019, 10:14:21 AM1/22/19
to MS Amanda
I noticed the MSAmanda mzIdentML output in 2.0.0.11219 standalone appears to be incorrect.

It currently generates two SpectrumIdentificationResult entries per spectrum, one for targets and another for decoys. The entry should be unique per spectrum, containing a combination of both identification types.
Actual as per 2.0:

    <SpectrumIdentificationResult id="SIR_0" spectrumID="0" spectraData_ref="SD_1">
      <SpectrumIdentificationItem id="SII_0_1" chargeState="2" experimentalMassToCharge="790.3333536858" peptide_ref="EEGDEKEEEKDDK_000000000000000" rank="1" passThreshold="True">
        <PeptideEvidenceRef peptideEvidence_ref="EEGDEKEEEKDDK_000000000000000_sp|Q9JL35" />
        <cvParam name="Amanda:AmandaScore" value="47.0586583281504" cvRef="PSI-MS" accession="MS:1002319" />
      </SpectrumIdentificationItem>
      ......
      <cvParam name="spectrum title" value="260416_Sample5.5119.5119.2 (intensity=966488.9626)" cvRef="PSI-MS" accession="MS:1000796" />
      <cvParam name="retention time" value="1188.781" cvRef="PSI-MS" accession="MS:1000894" unitCvRef="UO" unitAccession="UO:0000010" unitName="second" />
    </SpectrumIdentificationResult>

 

    <SpectrumIdentificationResult id="SIRD_0" spectrumID="0" spectraData_ref="SD_1">
      <SpectrumIdentificationItem id="SII_0_6482" chargeState="2" experimentalMassToCharge="790.3333536858" peptide_ref="EQLSSCALAKANK_000011100000000" rank="1" passThreshold="True">
        <PeptideEvidenceRef peptideEvidence_ref="EQLSSCALAKANK_000011100000000_REV_sp|Q9DBR4" />
        <cvParam name="Amanda:AmandaScore" value="58.5417487911531" cvRef="PSI-MS" accession="MS:1002319" />
      </SpectrumIdentificationItem>
      ....
      <cvParam name="spectrum title" value="260416_Sample5.5119.5119.2 (intensity=966488.9626)" cvRef="PSI-MS" accession="MS:1000796" />
      <cvParam name="retention time" value="1188.781" cvRef="PSI-MS" accession="MS:1000894" unitCvRef="UO" unitAccession="UO:0000010" unitName="second" />
    </SpectrumIdentificationResult>

This results in two rank="1" peptides being returned for the same spectrum with differing scores.

Expected:

    <SpectrumIdentificationResult id="SIR_0" spectrumID="0" spectraData_ref="SD_1">

      <SpectrumIdentificationItem id="SII_0_6482" chargeState="2" experimentalMassToCharge="790.3333536858" peptide_ref="EQLSSCALAKANK_000011100000000" rank="1" passThreshold="True">
        <PeptideEvidenceRef peptideEvidence_ref="EQLSSCALAKANK_000011100000000_REV_sp|Q9DBR4" />
        <cvParam name="Amanda:AmandaScore" value="58.5417487911531" cvRef="PSI-MS" accession="MS:1002319" />
      </SpectrumIdentificationItem>
      <SpectrumIdentificationItem id="SII_0_1" chargeState="2" experimentalMassToCharge="790.3333536858" peptide_ref="EEGDEKEEEKDDK_000000000000000" rank="2" passThreshold="True">
        <PeptideEvidenceRef peptideEvidence_ref="EEGDEKEEEKDDK_000000000000000_sp|Q9JL35" />
        <cvParam name="Amanda:AmandaScore" value="47.0586583281504" cvRef="PSI-MS" accession="MS:1002319" />
      </SpectrumIdentificationItem>

      ....
      <cvParam name="spectrum title" value="260416_Sample5.5119.5119.2 (intensity=966488.9626)" cvRef="PSI-MS" accession="MS:1000796" />
      <cvParam name="retention time" value="1188.781" cvRef="PSI-MS" accession="MS:1000894" unitCvRef="UO" unitAccession="UO:0000010" unitName="second" />
    </SpectrumIdentificationResult>

This bug appears to confuse a few readers and knock FDR scores out by quite a bit since it is assumed spectrumID will be unique.

Viktoria Dorfer

unread,
Feb 1, 2019, 6:43:54 AM2/1/19
to MS Amanda
Hi Andrew,

thanks for reporting this! We will have a look at that, it may be dependent on the settings, whether you let MS Amanda generate the decoy database or provide a concatenated target decoy database yourself, but I need to check. In any case, there should be an option to get just the best hit independent if it is target or decoy.
We will work on this!

Thanks!
Best regards,
Viktoria

Viktoria Dorfer

unread,
Aug 2, 2019, 8:24:48 AM8/2/19
to MS Amanda
Hi Andrew,

we have fixed that issue in the new standalone version (v. 2.0.0.13723). There is now an option available to rank the target and decoy together instead of separately.

Please let me know if that doesn't work for you!
Best regards,
Viktoria
Reply all
Reply to author
Forward
0 new messages