Universal Spectrum Identifier 🞩



USI Provider: Example USIs   ⇣ Recent USIs   ⇣

User Access

Please enter your PRIDE credentials to gain access to private data that may be available to you


Dismiss

Example use cases (USIs)

mzspec:PXD005336:Varlitinib_01410_A01_P014203_B00_A00_R1:scan:19343:LLSILSR/2
Simple HCD spectrum of LLSILSR
mzspec:PXD025716:PBMC_29_Rep_3:scan:16281:KLAELFTSW/2
Orbitrap CID spectrum of a non-tryptic HLA peptide (Figure 1 in Quetzal paper)
mzspec:PXD021265:Animal_20190611_OP_HStmt_Kroenke_Phospho_fr09:scan:10121:[TMT6plex]-SIGS[Phospho]DSQGR/2
Complex HCD spectrum of a TMT-labeled phosphopeptide (Figure 2 in paper)
mzspec:PXD000561:Adult_Frontalcortex_bRP_Elite_85_f09:scan:17555:VLHPLEGAVVIIFK/2
Complex spectrum that includes many prominent internal fragmentation ions (Figure 4 in paper)
Dismiss

Recently Opened USIs

You have no recently viewed USIs (on this browser) Dismiss


Peak List 🞩


Enter peak (and optional annotation) data, or drag/drop a TSV file below:
Input Format Help

Peak List Format

A peak list consists of rows with at least two columns (m/z and intensity), with an optional third column containing peak annotations.

Columns can be separated by one or more space characters (including combinations, e.g. tabs and spaces), and empty values are not allowed.

Furthermore, the following special spectrum and interpretation keywords are also recognized:

  • PRECURSORMZ
  • m/z
  • PEPTIDOFORMS
  • Peptide
  • CHARGES
  • Charge
If any of these strings is present as the first column in a given line, the value is taken from the second column.

Note: Spectrum and interpretation information may either be provided here or in the Edit section.

Spectrum Properties

Peptidoform(s): Syntax Help Charge(s): Fragmentation: Precursor m/z: Isobaric labeling: Target m/z: with ppm tolerance Upper offset: Isolation window Lower offset:

Peak Annotations Help Feedback

Please load annotated spectrum data to see annotation form.

QuickPlot

Quick Guide

ExampleDisplayDescription a4a4backbone a-ion b10^3b10+++triply charged b-ion c2c2c-ion x1x1x-ion y9-H2O^2y9++doubly charged y-ion with a water loss z6+iz6first isotope of z-ion IQQimmonium ion of Q ppprecursor ion r[TMT127N]TMTisobaric (TMT reporter) ion m4:6minternal "middle" ion spanning amino acids four to six f{C6H13O6}C6H13O6molecular formula ??unexplained peak
Dismiss
Use Mouse drag to zoom; hold down Control key to pan
⮜⮜ ⮞⮞ ⊕ Zoom in ⊖ Zoom out X Y ↺  Reset Zoom ⨉  Ion Labels ❔ Help

Settings

m/z minimum: m/z maximum: Y maximum: Mask isolation width: Min. labeling percent:

Preview



Press the Preview button above to generate image

What is Quetzal?

Quetzal is a peptide fragment ion spectrum annotation tool to assist researchers in annotating and examining tandem mass spectra to ensure that they correctly support study conclusions.

Quetzal annotates spectra using the new Human Proteome Organization (HUPO) Proteomics Standards Initiative (PSI) mzPAF standard for fragment ion peak annotation. Quetzal includes a Python-based codebase, a web-service endpoint that provides annotation services, and a user-friendly web-based application for annotating spectra and producing publication-quality figures.

You can view a usage guide, more information, and code at our GitHub page.

A publication is currently under review.

Detailed information on mzPAF can be found in this recent publication. A quick help guide is also available.


  

Annotation Guide

Annotations are given in mzPAF (PSI format). Below is a quick guide to help interpret them:
Dismiss

ProForma Guide

Peptidoforms are given in ProForma 2.0 (PSI format). Below is a quick guide to help build one:
ProForma Example Comment EMEVEESPEK Peptide with no modifications EM[Oxidation]EVEES[UNIMOD:21]PEK Modifications using common ontologies* EM[+15.9949]EVEES[+79.9663]PEK ...can also be specified directly [iTRAQ4plex]-EMEVNESPEK-[Methyl] Use a dash for terminal modifications

* Note that it is preferrable to use Unimod names when specifying PTMs Dismiss

Peak Annotation Feedback

Do you think Quetzal made a mistake in its annotations? Do you have a better/alternate interpretation that you wish to contribute?

Below are two options via which you can share your feedback with the Quetzal team:

Quick feedback on a specific peak or peaks

To send an alternate interpretation and/or provide feedback on one or a few peaks, please edit that peak's annotation using the form, adding the string Comment: anywhere in the annotation*, and choose to Save Annotations. This will trigger a manual review mechanism on our part. You can even include an email address if you wish to be contacted further; submissions are anonymous otherwise.

* Note that you will need to re-edit the annotation to remove the Comment and attached report before generating an image.

Detailed Feedback

For a deeper or more complex matter, please file an issue on our Github portal (click on the "New issue" button; a GitHub account is necessary). This will be investigated, tracked, and resolved in direct interaction with the development team.