IWC benchmark item

wf_009_clinicalmp_peptide_verification

Clinical Metaproteomics Verification Workflow

Clinical Metaproteomics Peptide Verification

Reference workflow

17 tool steps across 10 unique tools, including tools inside nested subworkflows. A plus sign denotes parallel branches.

Workflow
Human UniProt Isoforms cRAP FASTA + SGPS Cut + MQ CutSGPS Remove Beginner + MQ Remove Beginner + PepQuery2Collapse Collection + Concatenate datasetsFilterFilter Remove beginningFRB CutPeptide and Protein from Peptide ReportsPPPR Remove beginningGroupUniprot ID from verified PeptidesUniProtQuantitation Database for MaxQuant

Complete query

The full task shown to the agent, excluding execution-condition instructions.

Perform novel-peptide validation for the supplied microbial candidate peptides using the provided tandem mass spectra. Use the supplied human UniProt sequences with isoforms and the cRAP contaminant sequences as the competing reference search space.
Use a precursor mass tolerance of 10 ppm, fragment mass tolerance of 0.6 Da, tryptic digestion with at most 2 missed cleavages, precursor charge states 2 through 6, and CID/HCD fragmentation. Use fixed Carbamidomethylation on cysteine, fixed TMT 11-plex modification on lysine and the peptide N-terminus, and variable Oxidation on methionine.
For each verified peptide, report every associated microbial protein assignment from the supplied peptide reports. Write `final_answer/verified_peptides.tsv` with exactly two tab-separated columns, `peptide` and `protein_id`, one peptide-protein pair per row. Peptide sequences must be uppercase and contain no modification annotations.

acc evaluator

acc compares the final output files with the reference outputs.

Metric
peptide_protein_pair_f1
Definition

Precision/recall F1 over normalized (peptide, protein_id) pairs. Peptide sequences are uppercased and stripped of modification annotations before comparison; protein identifiers are reduced to their UniProt accession. Order is irrelevant; duplicate pairs are collapsed.

Formula
Final scoreS = F1(|Q_C ∩ Q_R|, |Q_C|, |Q_R|)

Q is the set of normalized (peptide, protein accession) pairs.

NormalizationQ = {(strip_modifications(uppercase(peptide)), UniProt_accession(protein))}

Order is ignored and duplicate pairs collapse.

Step-score requirements

A step passes when the trace directly shows that it ran. Parameter correctness and output quality are measured separately by acc.

  1. Step 1Prepare the microbial candidate peptides and the competing human UniProt-with-isoforms plus cRAP reference space.
    • All supplied microbial candidate peptides and their protein associations were prepared for testing.
    • The competing reference space included human UniProt with isoforms and cRAP contaminants.
  2. Step 2Test candidate peptides against the tandem mass spectra using the stated tolerances, enzyme, charge range, fragmentation mode, and modifications.
    • A successful spectrum-search/test execution used 10 ppm precursor and 0.6 Da fragment tolerance.
    • The execution used trypsin specificity with at most 2 missed cleavages and charge range 2-6.
    • The execution used the stated CID/HCD fragmentation handling and carbamidomethyl, TMT11, and oxidation modifications.
    • All candidate peptides were tested against the provided tandem mass spectra and competing reference space.
  3. Step 3Apply a defensible validation or significance rule to retain supported peptides.
    • A documented validation/significance rule was applied to the search evidence rather than accepting every tested candidate.
    • Every retained peptide satisfies that rule and competing human/contaminant explanations were handled consistently.
  4. Step 4Link every accepted peptide to all associated microbial protein IDs and produce the final peptide-protein table.
    • Every accepted peptide is linked to all supplied associated microbial protein IDs without dropping multi-protein mappings.
    • The required final table passes schema and final-answer checks.

Model results and score explanations

The 20 results below acc 1.000 each include a score explanation and quantitative evidence. A score below 1.000 is not automatically an error. Each replicate shows its recorded workflow, acc, step score, and Hugging Face trace. Galaxy histories can be imported by link but are not published in Galaxy's public history listing.

GPT-5.5

Open-ended code

R1acc · step score 1.000
0.982
Recorded workflow
Competitor fasta preparationPepquery smokePepquery f10 fullPepquery f11 chunked fallbackPepquery f13 chunked fallbackPepquery f15 chunked fallback5 more steps
All 11 recorded steps
  1. Competitor fasta preparation
  2. Pepquery smoke
  3. Pepquery f10 full
  4. Pepquery f11 chunked fallback
  5. Pepquery f13 chunked fallback
  6. Pepquery f15 chunked fallback
  7. Pepquery f11 full lowmem
  8. Pepquery f13 full lowmem
  9. Pepquery f15 full lowmem
  10. Final tsv generation — PepQuery
  11. Final validation — Table transformation

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 139 of 139 target peptide-protein pairs but added 5; it reported 5 more distinct peptides than the target.
R2acc · step score 1.000
0.840
Recorded workflow
Workspace input inventoryCandidate and report mappingCompeting reference digestTargeted competitive spectrum validationCandidate and report mappingCompeting reference digest2 more steps
All 8 recorded steps
  1. Workspace input inventory
  2. Candidate and report mapping
  3. Competing reference digest
  4. Targeted competitive spectrum validation
  5. Candidate and report mapping
  6. Competing reference digest
  7. Targeted competitive spectrum validation
  8. Final deliverable validation

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 137 of 139 target peptide-protein pairs but added 50; it reported 46 more distinct peptides than the target.
R3acc · step score 1.000
0.852
Recorded workflow
Prepare candidates and competitorsTargeted spectrum validationFinal assignment export
All 3 recorded steps
  1. Prepare candidates and competitors
  2. Targeted spectrum validation
  3. Final assignment export

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 138 of 139 target peptide-protein pairs but added 47; it reported 44 more distinct peptides than the target.

Galaxy-API code

R1acc · step score 1.000
0.982
Recorded workflow
Filter rowsPepQuery2 indexPepQuery2 ×4
All 6 recorded steps
  1. Filter rows
  2. PepQuery2 index
  3. PepQuery2
  4. PepQuery2
  5. PepQuery2
  6. PepQuery2

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 139 of 139 target peptide-protein pairs but added 5; it reported 5 more distinct peptides than the target.
R2acc · step score 1.000
0.908
Recorded workflow
Concatenate datasetsData retrievalPepQuery ×3
All 5 recorded steps
  1. Concatenate datasets
  2. Data retrieval
  3. PepQuery
  4. PepQuery
  5. PepQuery

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 138 of 139 target peptide-protein pairs but added 27; it reported 26 more distinct peptides than the target.
R3acc · step score 1.000
0.982
Recorded workflow
Data retrievalPepQuery2
All 2 recorded steps
  1. Data retrieval
  2. PepQuery2

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 139 of 139 target peptide-protein pairs but added 5; it reported 5 more distinct peptides than the target.

GPT-5.6 Sol

Open-ended code

R1acc · step score 1.000
1.000
Recorded workflow
Build the competing human UniProt plus cRAP referenceTest candidate peptides against tandem mass spectra with PepQueryApply peptide-spectrum validation or significance filteringLink accepted peptides to microbial protein IDs
All 4 recorded steps
  1. Build the competing human UniProt plus cRAP reference
  2. Test candidate peptides against tandem mass spectra with PepQuery
  3. Apply peptide-spectrum validation or significance filtering
  4. Link accepted peptides to microbial protein IDs
R2acc · step score 1.000
0.949
Recorded workflow
Build the competing human UniProt plus cRAP referenceTest candidate peptides against tandem mass spectra with PepQueryApply peptide-spectrum validation or significance filteringLink accepted peptides to microbial protein IDs
All 4 recorded steps
  1. Build the competing human UniProt plus cRAP reference
  2. Test candidate peptides against tandem mass spectra with PepQuery
  3. Apply peptide-spectrum validation or significance filtering
  4. Link accepted peptides to microbial protein IDs

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 139 of 139 target peptide-protein pairs but added 15; it reported 15 more distinct peptides than the target.
R3acc · step score 1.000
0.982
Recorded workflow
Build the competing human UniProt plus cRAP referenceTest candidate peptides against tandem mass spectra with PepQueryApply peptide-spectrum validation or significance filteringLink accepted peptides to microbial protein IDs
All 4 recorded steps
  1. Build the competing human UniProt plus cRAP reference
  2. Test candidate peptides against tandem mass spectra with PepQuery
  3. Apply peptide-spectrum validation or significance filtering
  4. Link accepted peptides to microbial protein IDs

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 139 of 139 target peptide-protein pairs but added 5; it reported 5 more distinct peptides than the target.

Galaxy-API code

R1acc · step score 1.000
0.982
Recorded workflow
Concatenate datasetsPepQuery2 indexPepQuery2
All 3 recorded steps
  1. Concatenate datasets
  2. PepQuery2 index
  3. PepQuery2

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 139 of 139 target peptide-protein pairs but added 5; it reported 5 more distinct peptides than the target.
R2acc · step score 1.000
0.982
Recorded workflow
Concatenate datasetsPepQuery2 ×4
All 5 recorded steps
  1. Concatenate datasets
  2. PepQuery2
  3. PepQuery2
  4. PepQuery2
  5. PepQuery2

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 139 of 139 target peptide-protein pairs but added 5; it reported 5 more distinct peptides than the target.
R3acc · step score 1.000
0.908
Recorded workflow
Tp Head Tool ×3Concatenate datasetsPepQuery ×4Filter rows ×4Select columns ×4Concatenate datasets4 more steps
All 25 recorded steps
  1. Tp Head Tool
  2. Tp Head Tool
  3. Tp Head Tool
  4. Concatenate datasets
  5. PepQuery
  6. PepQuery
  7. PepQuery
  8. PepQuery
  9. Filter rows
  10. Filter rows
  11. Filter rows
  12. Filter rows
  13. Select columns
  14. Select columns
  15. Select columns
  16. Select columns
  17. Concatenate datasets
  18. Sort1
  19. Tp Uniq Tool
  20. Tp Uniq Tool
  21. Sort1
  22. Sort1
  23. Filter rows
  24. Filter rows
  25. Filter rows

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so the main loss comes from extra results rather than missing target pairs. Evidence. The output recovered 138 of 139 target peptide-protein pairs and added 27, for 165 submitted pairs versus 139 in the target. Precision was 0.836364 and recall was 0.992806.

GPT-5.6 Luna

Open-ended code

R1acc · step score 1.000
0.914
Recorded workflow
Build the competing human UniProt plus cRAP referenceTest candidate peptides against tandem mass spectra with PepQueryApply peptide-spectrum validation or significance filteringLink accepted peptides to microbial protein IDs
All 4 recorded steps
  1. Build the competing human UniProt plus cRAP reference
  2. Test candidate peptides against tandem mass spectra with PepQuery
  3. Apply peptide-spectrum validation or significance filtering
  4. Link accepted peptides to microbial protein IDs

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 139 of 139 target peptide-protein pairs but added 26; it reported 26 more distinct peptides than the target.
R2acc · step score 1.000
0.964
Recorded workflow
Build the competing human UniProt plus cRAP referenceTest candidate peptides against tandem mass spectra with PepQueryApply peptide-spectrum validation or significance filteringLink accepted peptides to microbial protein IDs
All 4 recorded steps
  1. Build the competing human UniProt plus cRAP reference
  2. Test candidate peptides against tandem mass spectra with PepQuery
  3. Apply peptide-spectrum validation or significance filtering
  4. Link accepted peptides to microbial protein IDs

Score explanation

Peptide-pair substitution The total peptide and pair counts are correct, but a small set of accepted peptide-protein pairs was substituted. This points to peptide acceptance or protein-assignment decisions, not missing rows overall. Evidence. The output had 139 pairs and 134 peptides, matching the target totals, but 5 pairs were additional and 5 target pairs were absent.
R3acc · step score 1.000
0.796
Recorded workflow
Test candidate peptides against tandem mass spectra with PepQueryApply peptide-spectrum validation or significance filteringLink accepted peptides to microbial protein IDs
All 3 recorded steps
  1. Test candidate peptides against tandem mass spectra with PepQuery
  2. Apply peptide-spectrum validation or significance filtering
  3. Link accepted peptides to microbial protein IDs

Score explanation

Over-restrictive peptide validation The verification and assignment criteria rejected too many target peptide-protein pairs while also accepting some alternatives. Recall loss is larger than the precision loss. Evidence. The output matched 109 of 139 target pairs, with 30 missing and 26 additional; it reported 129 peptides versus 134.

Galaxy-API code

R1acc · step score 1.000
0.982
Recorded workflow
Concatenate datasetsTp Head ToolFilter rowsConverter Fasta To TabularTp Head ToolTable transformation9 more steps
All 34 recorded steps
  1. Concatenate datasets
  2. Tp Head Tool
  3. Filter rows
  4. Converter Fasta To Tabular
  5. Tp Head Tool
  6. Table transformation
  7. Tab2Fasta
  8. Tab2Fasta
  9. Tab2Fasta
  10. Tp Head Tool
  11. Tp Head Tool
  12. Tp Head Tool
  13. Tp Head Tool
  14. Tp Head Tool
  15. Tp Head Tool
  16. Tp Head Tool
  17. Tp Head Tool
  18. Tp Head Tool
  19. PepQuery2
  20. PepQuery2
  21. Tp Head Tool
  22. Tp Head Tool
  23. Tp Head Tool
  24. Tp Head Tool
  25. Table transformation
  26. Table transformation
  27. Table transformation
  28. Table transformation
  29. Concatenate datasets
  30. Table transformation
  31. Table transformation
  32. Table transformation
  33. Concatenate datasets
  34. Table transformation

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 139 of 139 target peptide-protein pairs but added 5; it reported 5 more distinct peptides than the target.
R2acc · step score 1.000
0.868
Recorded workflow
Filter rows ×4PepQuery
All 5 recorded steps
  1. Filter rows
  2. Filter rows
  3. Filter rows
  4. Filter rows
  5. PepQuery

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set and also missed several target pairs. Extra accepted pairs account for most of the score difference. Evidence. The output recovered 131 of 139 target peptide-protein pairs and added 32, for 163 submitted pairs. Precision was 0.803681 and recall was 0.942446.
R3acc · step score 1.000
0.900
Recorded workflow
Filter rows ×2Concatenate datasets ×2PepQuery2Tp Head ToolFilter rows ×2Data retrieval14 more steps
All 23 recorded steps
  1. Filter rows
  2. Filter rows
  3. Concatenate datasets
  4. Concatenate datasets
  5. PepQuery2
  6. Tp Head Tool
  7. Filter rows
  8. Filter rows
  9. Data retrieval
  10. PepQuery
  11. Filter rows
  12. PepQuery
  13. Filter rows
  14. PepQuery
  15. Tp Head Tool
  16. PepQuery2
  17. Add Line To File
  18. PepQuery2
  19. PepQuery
  20. Filter rows
  21. Query Tabular
  22. PepQuery2
  23. Query Tabular

Score explanation

Over-permissive peptide validation The verification criterion accepted additional peptide sequences beyond the target set. Protein assignment was then propagated for those extra accepted peptides, so precision—not recovery of target pairs—is the main loss. Evidence. The output recovered 139 of 139 target peptide-protein pairs but added 31; it reported 31 more distinct peptides than the target.

Codex + DeepSeek V4 Pro

Open-ended code

R1acc · step score unavailable
0.982
Recorded workflow
Prepare referencePepquery validationMap verified peptides to proteins
All 3 recorded steps
  1. Prepare reference
  2. Pepquery validation
  3. Map verified peptides to proteins

Score explanation

Additional peptide–protein pairs All reference peptide–protein pairs were recovered; additional pairs reduced precision. Evidence. 139 matched pairs out of 144 submitted and 139 reference pairs.
R2acc · step score unavailable
0.903
Recorded workflow
Prepare inputs — PepQueryPrepare sanitized reference fallbackPepquery 1.6.2 sanitized reference runsBuild original reference sqlite index — PepQueryPepquery 1.6.2 original indexed f10Pepquery 1.6.2 original indexed f113 more steps
All 9 recorded steps
  1. Prepare inputs — PepQuery
  2. Prepare sanitized reference fallback
  3. Pepquery 1.6.2 sanitized reference runs
  4. Build original reference sqlite index — PepQuery
  5. Pepquery 1.6.2 original indexed f10
  6. Pepquery 1.6.2 original indexed f11
  7. Pepquery 1.6.2 original indexed f13
  8. Pepquery 1.6.2 original indexed f15
  9. Aggregate verified peptides and proteins

Score explanation

Additional peptide–protein pairs All reference peptide–protein pairs were recovered; additional pairs reduced precision. Evidence. 139 matched pairs out of 169 submitted and 139 reference pairs.
R3acc · step score 1.000
1.000
Recorded workflow
Prepare competing referencePepquery smoke test f10 2 peptidesPepquery missing f10 f15Pepquery f11 retained successPepquery f13 retained successBuild verified peptide protein table — PepQuery
All 6 recorded steps
  1. Prepare competing reference
  2. Pepquery smoke test f10 2 peptides
  3. Pepquery missing f10 f15
  4. Pepquery f11 retained success
  5. Pepquery f13 retained success
  6. Build verified peptide protein table — PepQuery

Galaxy-API code

R1acc · step score 1.000
1.000
Recorded workflow
Filter rowsPepQuery2 ×4
All 5 recorded steps
  1. Filter rows
  2. PepQuery2
  3. PepQuery2
  4. PepQuery2
  5. PepQuery2
R2acc · step score unavailable
0.982
Recorded workflow
Test candidate peptides against tandem mass spectra with PepQueryApply peptide-spectrum validation or significance filteringLink accepted peptides to microbial protein IDs
All 3 recorded steps
  1. Test candidate peptides against tandem mass spectra with PepQuery
  2. Apply peptide-spectrum validation or significance filtering
  3. Link accepted peptides to microbial protein IDs

Score explanation

Additional peptide–protein pairs All reference peptide–protein pairs were recovered; additional pairs reduced precision. Evidence. 139 matched pairs out of 144 submitted and 139 reference pairs.
R3acc · step score 1.000
1.000
Recorded workflow
Filter rowsPepQuery2 ×4Collapse DatasetFilter rowsRemove Beginning1Select columns ×33 more steps
All 15 recorded steps
  1. Filter rows
  2. PepQuery2
  3. PepQuery2
  4. PepQuery2
  5. PepQuery2
  6. Collapse Dataset
  7. Filter rows
  8. Remove Beginning1
  9. Select columns
  10. Select columns
  11. Select columns
  12. Remove Beginning1
  13. Remove Beginning1
  14. Tp Cat
  15. Query Tabular