DIA ion entrapment (Astral)#

beta FDR validation — DIA, Orbitrap Astral, global precursor-ion FDR

This module is in beta stage

This module has been validated and is suitable for submissions. However, metrics or thresholds may be refined as we gather more community results and feedback.

Uses entrapment peptides to assess whether the false discovery rate (FDR) reported by a DIA search engine is reliable. Based on the entrapment approach in Wen et al., 2025.

Open in web app

At a glance#

Acquisition

DIA

Instrument

Orbitrap Astral

Level

Global precursor-ion FDR

Metric

Lower bound / combined / paired FDP

What this module tests#

FDR control is a central assumption in proteomics data analysis: if a search engine reports 1% FDR, the actual proportion of false discoveries should not exceed 1%. This module tests that assumption empirically by spiking a known set of “entrapment” peptides into the search space. These peptides cannot be present in the sample (they’re derived from a shuffled/decoupled database), so any identification of one is a genuine false discovery.

Search engines calculate FDR at different levels (within-run vs. global, precursor vs. peptidoform vs. protein-group). This module tests the global precursor-ion-level FDR specifically — search engines that don’t calculate FDR at this level can’t be benchmarked here.

Three metrics are computed:

  • Lower bound FDP: minimum estimate of the false discovery proportion, from the raw count of entrapment identifications.

  • Combined FDP (upper bound): corrected upper bound accounting for the 1:1 target-to-entrapment ratio in the search database.

  • Paired FDP (upper bound): refined upper bound using a paired peptide mapping, accounting for entrapment peptides that are harder to identify than their target counterparts.

Each submission is classified as:

  • Valid: the upper bound FDP is lower than the reported FDR threshold.

  • Inconclusive: the lower bound is below the declared FDR but the upper bound is above it — the actual FDP could be either side of the reported value.

  • Invalid: even the lower bound is above the declared FDR threshold.

Critical requirements before running#

Important

  • Do not rename the raw files after download. File names are used for run mapping.

  • Use the pre-digested entrapment FASTA; do not enable in-silico digestion. The FASTA already contains peptide sequences, not full proteins. Enabling digestion leads to identified peptides without matched entrapments, which makes FDP calculation less accurate.

  • Only methionine oxidation is supported as a variable modification. The entrapment mapping enumerates every combination of methionine oxidation and cysteine carbamidomethylation. Enabling any other modification (variable, or an additional fixed modification) causes metric calculation to fail with an error, because the target/entrapment pairing cannot be resolved for it.

Dataset#

Three technical replicates of a 50ng HeLa digest acquired on an Orbitrap Astral in DIA mode with a 15-minute gradient. Full MS scans over m/z 380–980 at 240,000 resolution (Orbitrap); 300 windows of 2 Th isolating and fragmenting precursors from 380–980 m/z; 25% normalized collision energy (HCD); MS2 over m/z 150–2000 (Astral), 3 ms maximum injection time. Full dataset details are in this preprint.

Download:

Important

Do not rename the downloaded raw files.

The entrapment FASTA (ProteoBenchFASTA_Entrapment_Human_with_contaminants_entrapment_pep.txt) is available from the ProteoBench server. It contains human peptide sequences alongside a matched set of entrapment peptides (suffixed _p_target for classification). This file is pre-digested — do not apply enzymatic digestion in your search engine settings.

How the metric is calculated#

ProteoBench reads the search engine output, maps runs to samples, and classifies each precursor identification as a target or an entrapment hit based on the FASTA tag. The three FDP estimates are computed from the resulting set and compared to the reported FDR threshold (inferred from the output file).

Note

reported_fdr_parsed_from_input (used for this comparison) is not always the same value as ident_fdr_psm (the FDR setting extracted from the parameter/log file for public submission). reported_fdr_parsed_from_input is computed as the maximum Q-value actually present among the rows in the uploaded result file, so it reflects what the file contains rather than what was configured.

Precursor identifications are matched to the entrapment mapping file using their exact modified sequence, not the stripped peptide. The mapping file enumerates every combination of variable methionine oxidation and fixed cysteine carbamidomethylation, so an identification built only from those two modifications is paired correctly, down to the specific set of oxidized methionines. Any other modification present in the reported sequence is not recognized, and metric calculation fails with an error rather than silently ignoring it.

Run your workflow#

The module currently accepts DIA-NN, AlphaDIA, and Spectronaut output (or a Custom tab-delimited format). Use the suggested parameters below for a fair comparison between tools, then follow Your First Submission to upload, inspect, and (if you’d like) submit your results publicly.

Table: suggested parameters

Parameter

Value

PSM / precursor FDR

0.01

Spectral library

Predicted from entrapment FASTA

Digestion

None (FASTA is pre-digested)

Fixed modifications

Carbamidomethylation (C)

Variable modifications

Methionine oxidation (M), optional. No other variable modification is supported.

Precursor charge range

1–5

Precursor m/z range

400–1000

Fragment m/z range

100–1800

Tool-specific setup#

Table: input files required for metric calculation and public submission

Tool

Input file

Parsed FDR column

Parameter file

AlphaDIA

precursors.parquet

qval

log.txt

Custom

custom_format.csv

Q-Value

—

DIA-NN

report.tsv or report.parquet

Lib.Q.Value

report.log.txt

Spectronaut

*.tsv

EG.LibraryQvalue

ExperimentSetupOverview.txt

Note

FragPipe (native search) is not currently supported: its decoy generation is not compatible with the pre-digested entrapment FASTA (see this FragPipe issue).

DIA-NN
  1. Import the raw .raw files.

  2. Add the entrapment FASTA. Do not enable “Contaminants” (already included).

  3. Disable in-silico digestion — use --cut in additional parameters, since the FASTA is pre-digested.

  4. Variable modifications are limited to methionine oxidation (optional); disable all other variable modifications. Carbamidomethylation (C) can be used as a fixed modification.

  5. Enable library-free search / FASTA-based library generation.

  6. Do not set verbosity/log level above 1, or parameter parsing will fail.

  7. Upload report.tsv or report.parquet for scoring and report.log.txt for public submission.

AlphaDIA

Parsed from precursor-level output; the entrapment module currently expects AlphaDIA 2.x-style precursor output.

  1. Use the entrapment FASTA and disable additional contaminants.

  2. Configure a no-enzyme / pre-digested-FASTA search: set “no-cleave” as the enzyme parameter.

  3. Variable modifications are limited to methionine oxidation; keep all other variable modifications disabled. Use carbamidomethylation (C) as the fixed modification if alkylation was applied.

  4. Upload precursors.parquet for scoring and the AlphaDIA log.txt for public submission.

Spectronaut
  1. Set up a new cleavage rule without any cleavage.

  2. Import the entrapment FASTA in the “Databases” tab (Proteins) using the UniProt parsing rule.

  3. In the “Analysis” tab, select “Set up a DirectDIA Analysis from folder” and select the folder containing the raw files.

  4. Select the entrapment FASTA as the database, set Protein ID to “Accession”, and use the new no-cleavage rule.

  5. In the modifications tab, add carbamidomethylation as a fixed modification and/or methionine oxidation as variable. No other modifications are supported.

  6. Once the search is finished, go to the “Report” tab, select “BGS Factory Report”, and export the report as .tsv.

  7. Upload the report .tsv for scoring and the accompanying ...Report.setup.txt (in the same folder) for public submission.

Custom format

If your tool isn’t listed above, upload a tab-delimited table with:

  • Peptide — stripped peptide sequence (no modifications)

  • Sequence — modified peptide sequence, already in ProForma-style bracket notation (e.g. M[Oxidation], C[Carbamidomethyl]); no further conversion is applied, so other notations (e.g. M(UniMod:35)) are not recognized

  • Charge — precursor charge

  • Q-Value — global precursor-level FDR value

Example file: custom_format_entrapment.csv.

Result plots#

After uploading, you’ll see the FDP bounds plotted against the FDR estimate reported by the search engine. A valid (conservative) FDR calculation has the empirical upper bound below the declared FDR threshold.

The “View Public + New Results” tab shows:

  • Forest plot: one horizontal interval per workflow, from the lower bound FDP to the paired FDP upper bound, with the declared FDR threshold marked as a diamond.

  • FDP / FDR ratio vs. # IDs: paired FDP divided by the declared FDR (x-axis) against the number of identifications at 1% FDR (y-axis). Points left of x = 1 have an empirical FDP below the declared threshold.

Parameters tracked for public submission#

ProteoBench extracts:

  • software tool name and version

  • FDR threshold (PSM/precursor, peptide, protein level)

  • precursor and fragment m/z range

  • precursor and fragment mass tolerance

  • fixed and variable modifications

  • minimum/maximum precursor charge

  • enzyme (should be “None” for this module)

If a parameter isn’t in your file, add it in Comments for submission.

Check your parameter file for personal information

Parameter files can embed local file paths (FASTA location, raw data location, tool installation paths) that may reveal personal or institutional information. Review and sanitize before submission.

Once submitted you’ll get a pull-request link; save it to track your submission (see what happens next). Contact us or open an issue with any problems.