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

Validator - incorrect error about SearchType CV term #1

Open
vrkosk opened this issue Mar 10, 2022 · 3 comments
Open

Validator - incorrect error about SearchType CV term #1

vrkosk opened this issue Mar 10, 2022 · 3 comments

Comments

@vrkosk
Copy link

vrkosk commented Mar 10, 2022

Mascot Server 2.6 and later support combined spectral library and FASTA searches. The software exports the type using a valid CV term:

    <SpectrumIdentificationProtocol id="SIP" analysisSoftware_ref="AS_mascot_server">
      <SearchType>
        <cvParam accession="MS:1002755" name="combined ms-ms + spectral library search" cvRef="PSI-MS" value="" />
      </SearchType>

Term definition in psi-ms.obo:

id: MS:1002755
name: combined ms-ms + spectral library search
def: "A combined MS2 (with fragment ions) and spectral library search." [PSI:PI]
is_a: MS:1001080 ! search type

The validator isn't happy and gives two errors:

Message 2:
    Rule ID: SearchTypeObjectRule
    Level: ERROR
    Context(/MzIdentML/AnalysisProtocolCollection/SpectrumIdentificationProtocol )
    --> At least one child term of 'search type' must occur in SearchType of the SpectrumIdentificationProtocol (id='SIP') element at /MzIdentML/AnalysisProtocolCollection/SpectrumIdentificationProtocol
    Tip: The SearchType element of SpectrumIdentificationProtocol must contain a CV term.

Message 3:
    Rule ID: SearchType_must_rule
    Level: ERROR
    Context(/searchType/cvParam/@accession ) in 2 locations
    --> The result found at: /searchType/cvParam/@accession for which the values is  ''MS:1002755'' didn't match any of the 6 specified CV terms:
  - The sole term MS:1001010 (de novo search) or any of its children. A single instance of this term can be specified. The matching value has to be the identifier of the term, not its name.
  - The sole term MS:1001031 (spectral library search) or any of its children. A single instance of this term can be specified. The matching value has to be the identifier of the term, not its name.
  - The sole term MS:1001081 (pmf search) or any of its children. A single instance of this term can be specified. The matching value has to be the identifier of the term, not its name.
  - The sole term MS:1001082 (tag search) or any of its children. A single instance of this term can be specified. The matching value has to be the identifier of the term, not its name.
  - The sole term MS:1001083 (ms-ms search) or any of its children. A single instance of this term can be specified. The matching value has to be the identifier of the term, not its name.
  - The sole term MS:1001584 (combined pmf + ms-ms search) or any of its children. A single instance of this term can be specified. The matching value has to be the identifier of the term, not its name

The validator is wrong. The mzIdentML 1.1 specification section 6.63 says "MUST supply a child term of MS:1001080 (search type)" and MS:1002755 is a child of MS:1001080. mzIdentML 1.2 specification section 6.66 says the same.

@colin-combe
Copy link

@vrkosk
Copy link
Author

vrkosk commented Jun 16, 2022

I'm not familiar with the mapping file or how it's used by the validator, but looks probable.

@colin-combe
Copy link

I'm not familiar with the mapping file or how it's used

me neither

it looks like the validator maybe isn't maintained at the moment?

we could prob fix this, but maybe it makes more sense to look at it after mzIdentML 1.2.1 is finalised (there'll be a few changes to be made to the validator then)

@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

2 participants