Changelog
Source:NEWS.md
ezGenomeTracks 0.0.17
Changes
- Made
height_factor = "auto"the default inez_sashimi(), using bounded square-root heights based on pooled junction clusters and shared coverage. A viewport safeguard prevents small clusters from receiving excessive heights. - Retained numeric
height_factorvalues as manual overrides; use0.05for the previous default behavior. - Added an optional
arc_heightaesthetic togeom_link()so curves, labels, and sashimi y-axis limits use the same resolved junction heights.
ezGenomeTracks 0.0.16
Changes
- Reduced whitespace in
ez_sashimi()by fitting shared y-axis limits to coverage and actual junction curve extrema, with a single 5% padding allowance. - Added validation for finite, non-negative
height_factorvalues and regression coverage for unequal arc endpoints, multiple tracks, and zero-height plots.
ezGenomeTracks 0.0.15
Changes
Fixed integer overflow in genome-wide Manhattan cumulative positions, preventing later chromosomes and highlighted SNPs from being dropped with integer BP inputs.
-
Consolidated GTF/GFF loading in
ez_gene():- GTF/GFF file paths are now standardized through
import_gtf()to produce a consistent data-frame schema. - Retained direct
rtracklayer::import()handling only for non-GTF generic file paths. - Updated
ez_gene()documentation to reflect the canonicalimport_gtf()pathway and deprecateauto_importbehavior.
- GTF/GFF file paths are now standardized through
ezGenomeTracks (development version)
Major Changes
- BigWig file processing now uses
megadepthfor significantly improved performance- Region-based BigWig queries are 2-50x faster depending on the number of regions
- Particularly beneficial for remote BigWig files (HTTP/HTTPS URLs)
- Built-in parallelization support for processing multiple BigWig files
- All existing APIs remain unchanged; upgrade is transparent to users
- v0.0.1 release.