Skip to content

v2.0.1

Latest

Choose a tag to compare

@jluebeck jluebeck released this 27 Oct 18:02
2ec0c14

AmpliconClassifier v2.0.1

TL;DR: bug-fix release for the BFB and FAN feature reporting added in 2.0.0. It fixes BFBArchitect BFB footprints, reports every BFB feature, removes ghost features in FAN amplicons, and writes results tables in single-amplicon mode.

Overview

AmpliconClassifier 2.0.1 fixes several problems in how 2.0.0 turned BFB and FAN calls into reported features (BED files, gene lists and results-table rows). Most BFB+ / ecDNA+ / FAN+ amplicon calls are unchanged. BFB feature intervals and the genes reported on them can change substantially, and a small number of amplicons lose a BFB+ call. If you have 2.0.0 BFB feature intervals or BFB gene lists, re-run AC 2.0.1 on those samples. Record the AC version alongside any cohort results.

This release requires BFBArchitect 1.0.2, which supports PuLP 4, retries CBC if its process aborts, and makes CBC pick the same solution among ties. Under CBC, BFBArchitect scores can differ from 1.0.1 on tied graphs, and runs are about twice as slow. In testing on 44 graphs, no score crossed AC's 2.8 threshold.

BFB feature intervals

  • BFBArchitect BFB footprints are now trimmed to the AA graph. BFBArchitect bridges gaps between graph segments when it builds its copy-number vector. In 2.0.0, AC reported that padded region as the BFB feature, so a feature could span many Mb that are not in the breakpoint graph. Genes in those spans were reported as BFB-amplified with unknown copy number. AC now restricts BFBArchitect-derived intervals to AA graph segments with CN ≥ 4, the same floor used for AC's native BFB features.
  • Minimum BFB feature size. BFB features smaller than 5 kbp after trimming are dropped. A BFB+ call now requires at least one reportable BFB feature. The threshold is the new config parameter min_bfb_feature_size (default 5000).
  • Every BFB feature is reported. 2.0.0 only wrote BFB_1 to the results table and only computed complexity for BFB_1, so BFB_2, BFB_3, ... features never appeared in the table. Each BFB feature now gets its own results-table row and its own complexity values.

FAN amplicons

  • In FAN+ amplicons, 2.0.0 also created a fallback Linear / Complex-non-cyclic feature that always lay inside FAN_1. That feature was written to BED files, gene lists, basic properties, complexity, features_to_graph and similarity scores, but not to the results table. It is no longer created. Complexity rows are written only for features that exist.

Foldbacks and fb_dist_cut

  • The SV summary tables (*_SV_summaries/) labelled same-orientation inversions as foldback using a hard-coded 25 kbp cutoff, while classification used fb_dist_cut (50 kbp). The SV summaries now use fb_dist_cut, so inversions of 25–50 kbp are relabelled from inversion to foldback. Classification is unaffected.
  • BFBArchitect uses a fixed 50 kbp foldback cutoff. AC now logs a warning at startup when a custom --config sets a different fb_dist_cut while BFBArchitect is enabled.
  • AC_config_parameters.md now gives the correct fb_dist_cut default (50000; it previously said 25000) and documents min_bfb_feature_size.

Input handling and results table

  • Empty-input check: AC exits with an error before classifying if any cycles or graph file is empty.
  • Single-amplicon results table: single-amplicon runs (--cycles / --graph) now produce _result_table.tsv and _result_data.json, like --AA_results / --input runs.
  • Derived-file warning: in single-amplicon mode, AC warns, but still classifies, when an explicit path looks like an AC- or BFBArchitect-derived file that make_input.sh would skip (for example an annotated_cycles file or a file under bfbarchitect_outputs/).

Upgrading from 2.0.0

  • There are no new required arguments and no changes to the output column layout.
  • Expect these differences against 2.0.0 outputs:
    • BFB BED intervals are smaller.
    • Fewer genes are reported on BFB features, mainly genes that previously had unknown copy number.
    • A few amplicons are no longer BFB+. These are BFBArchitect-only calls with no CN ≥ 4 segment of at least 5 kbp left after trimming.
    • New BFB_2+ rows appear in the results table.
    • Ghost Complex-non-cyclic_1 / Linear_1 BED files and gene-list rows are gone from FAN amplicons.
    • Some inversion → foldback relabels appear in the SV summaries.

Tag update

The v2.0.1 tag was moved on 2026-11-06, from 0ca5d74 to 2ec0c14, so that AC 2.0.1 requires BFBArchitect 1.0.2. It also adds one small fix: AC now reports why BFBArchitect failed to load. Source archives of this tag downloaded before that date have a different checksum.