Skip to content
This repository was archived by the owner on May 18, 2024. It is now read-only.
This repository was archived by the owner on May 18, 2024. It is now read-only.

Question about method MzIdentMLUtils.getSpectrumId #30

Description

@colin-combe

Hi - we have been looking at different ways of parsing mzIdentML files. PRIDEs ms-data-core-api looks to be the most complete solution, for example, other libraries do not deal with the different formats used for spectrum ids.

I have a question regarding the formats used for spectrum ids and the code at:
https://github.com/PRIDE-Utilities/ms-data-core-api/blob/4b5f9f8d8a87c03b37a9652492a95aec029c1ca9/src/main/java/uk/ac/ebi/pride/utilities/data/utils/MzIdentMLUtils.java#L55-L82

As I read it, in the case where the fileIdFormat is Constants.SpecIdFormat.MASCOT_QUERY_NUM or Constants.SpecIdFormat.MULTI_PEAK_LIST_NATIVE_ID
then one is added to the spectrum id. I took this to mean that these formats use zero-based indexes whereas the norm for these formats is to use one based indexes.

This is the case for the multiple peak list nativeID format (MS:1000774) which says:

Index is the spectrum number in the file, starting from 0.

However, for the Mascot query number (MS:1001528) it says:

The spectrum (query) number in a Mascot results file, starting from 1.

So, finally getting to my question, why is one added to the spectrum id for Mascot query number format when the corresponding CV term says it is already one-based?

cheers,
Colin

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions