Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mzIdentML validator: residue-pair-level score pairing and ambiguity #3

Open
lutzfischer opened this issue May 8, 2020 · 0 comments

Comments

@lutzfischer
Copy link

The validator flags residue level scores up as not paired - but this disregards ambiguity. I.e. I have a case where I have a link from peptide XXXXXKXR to PEPTIDEKR and the protein actually contains the sequence ...PEPTIDEKRPEPTIDEKR... - therefore I get an ambiguous residue pair. Now in the resulting mzIdentML contains:

  <ProteinAmbiguityGroup id="PAG_13">
    <ProteinDetectionHypothesis dBSequence_ref="dbseq_XXXXX_target" passThreshold="false" id="PAG_13_PDH_0">
      ...
      <cvParam cvRef="PSI-MS" accession="MS:1002677" name="residue-pair-level global FDR" value="151808167.a:214:0.0:true"></cvParam>
      <cvParam cvRef="PSI-MS" accession="MS:1002677" name="residue-pair-level global FDR" value="151808167.b:141:0.0:true"></cvParam>
      <cvParam cvRef="PSI-MS" accession="MS:1002677" name="residue-pair-level global FDR" value="151808167.b:149:0.0:true"></cvParam>

But the validator comes back with:

Message 14497:
    Level: ERROR
    --> Interaction score is not paired for XL interaction ID 151810610 and score 0.0 (has only 1 entries for : PAG: PAG_13 and PDH: PAG_13_PDH_0

but it is paired - only that 151808167.b: turns up twice (as that side is the ambiguous).

@ypriverol ypriverol transferred this issue from HUPO-PSI/mzIdentML Oct 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant