Skip to content

TargetDecoy

Bioc current

Diagnostic Plots to Evaluate the Target Decoy Approach

v1.18.0 · Package record · software · Artistic-2.0

Release Lineage

Entered 3.14 · Oct 27, 2021

Current · Requires R 4.6

1.0 In 10 of 49 releases 3.23

Description

A first step in the data analysis of Mass Spectrometry (MS) based proteomics data is to identify peptides and proteins. With this respect the huge number of experimental mass spectra typically have to be assigned to theoretical peptides derived from a sequence database. Search engines are used for this purpose. These tools compare each of the observed spectra to all candidate theoretical spectra derived from the sequence data base and calculate a score for each comparison. The observed spectrum is then assigned to the theoretical peptide with the best score, which is also referred to as the peptide to spectrum match (PSM). It is of course crucial for the downstream analysis to evaluate the quality of these matches. Therefore False Discovery Rate (FDR) control is used to return a reliable list PSMs. The FDR, however, requires a good characterisation of the score distribution of PSMs that are matched to the wrong peptide (bad target hits). In proteomics, the target decoy approach (TDA) is typically used for this purpose. The TDA method matches the spectra to a database of real (targets) and nonsense peptides (decoys). A popular approach to generate these decoys is to reverse the target database. Hence, all the PSMs that match to a decoy are known to be bad hits and the distribution of their scores are used to estimate the distribution of the bad scoring target PSMs. A crucial assumption of the TDA is that the decoy PSM hits have similar properties as bad target hits so that the decoy PSM scores are a good simulation of the target PSM scores. Users, however, typically do not evaluate these assumptions. To this end we developed TargetDecoy to generate diagnostic plots to evaluate the quality of the target decoy method.

Advisories

None published for Bioconductor

Test coverage

Line coverage

–

Expression

–

Tests / Examples

–

Functions

18 6 exported

Complexity

2.3 avg / 5 max

Call network

18 nodes / 26 edges

Test coverage is not measured for Bioconductor packages; nodes fall back to a neutral fill.

Loading call graph…

Lowest coverage

Per-function coverage is not measured for this package yet.

Code

Structure

Lines of code

1,839

Files

28

Compiled share

0%

Has compiled src

No

Language breakdown

R 731 (39.7%)Tests 190 (10.3%)Docs 353 (19.2%)Vignettes 565 (30.7%)

API

Exported functions

6

Internal functions

12

Testing

Has tests

Yes

Test-to-code ratio

0.26

testthat edition

3

Docs

Roxygen coverage

100%

Health & Security signals

Informational signals; not verdicts.

on.exit coverage

–

Unsafe pattern score

0

Dep constraint coverage

0%

Secret pattern count

0

Bundled 3rd-party code

2 items

Portability & License

Min R version

4.1

System requirements

–

C++ standard

–

License

Artistic-2.0

License flags

SPDX valid, OSI approved

History

Versions

10

First release

2021-10-26

Latest release

2026-04-28

Avg cadence

182 days

Cold removal rate

–

Dep drift

2

LOC over versions

v3.14: 1,560 LOCv3.15: 1,560 LOCv3.16: 1,839 LOCv3.17: 1,839 LOCv3.18: 1,839 LOCv3.19: 1,839 LOCv3.20: 1,839 LOCv3.21: 1,839 LOCv3.22: 1,839 LOCv3.23: 1,839 LOC

Per-file churn detail lives in the source pipeline: https://github.com/r-observatory/bioc-code-metrics.

Documentation

In the Bioconductor 3.23 release
READMEYes · 371 wordsVignettesYes · 1 · dynamicNEWSYes · 100% structuredCitation fileNoWebsiteYes · pkgdown
Help pages
7 (1 internal)includes a package overview page
Examples that run
100%4 run in a plain check
Exported functions with examples
100%
Documented parameters
100%
Return-value docs
100%
Help pages citing references
0%

Repository practices

Upstream repositoryBeta

7 development-tooling and community-health practices detected across 3 families in the upstream repository

Checks run against github.com/statomics/targetdecoy on 2026-10-11.

Continuous integration (2)
GitHub ActionsR CMD check workflow

The R CMD check workflow runs on Linux, macOS and Windows

Docs source (4)
README.Rmdpkgdown

GitHub Pages site last deployed 2022-11-04 · The repository has a site deploy workflow

Coverage (1)
Coverage reporting (Codecov)
How this is detected·Detection ruleset v3 (2026-09-26)

Datasets

Bundled datasets · 2
NameClassSizeAlso in
ModSwiss–––
ModSwissXT–––

All of TargetDecoy's data objects

Topics

Maintainer
Elke Debrie

Available on

CRANr2uBioconductorautoCRANCOPR

People

Cite

Cite this package

Run in R for the authors' preferred citation:

citation("TargetDecoy")
Debrie, E., Clement, L., & Malfait, M. (2026). TargetDecoy: Diagnostic Plots to Evaluate the Target Decoy Approach (Version 1.18.0) [Computer software]. https://bioconductor.org/packages/TargetDecoy

This package has no citation file, so citation() returns this entry built from DESCRIPTION.

Cite the R Observatory

For a number measured here: a download total, a coverage figure, an archival date.

APA

Balamuta, J. J. (2026). R Observatory: Metrics for TargetDecoy version 1.18.0 [Data set]. HJJB, LLC. Data release v2026-10-18. https://doi.org/10.5281/zenodo.21843040

From data release v2026-10-18, which the citation names so these numbers can be found later. More on citing and the projects behind them.

Report a problem with this page →

Privacy choices

These apply to this browser and are stored on this device only. Nothing about your choice is sent to us.

Read the privacy policy