Skip to content

BaalChIP

Bioc current

BaalChIP: Bayesian analysis of allele-specific transcription factor binding in cancer genomes

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

Release Lineage

Entered 3.4 · Oct 18, 2016

Current · Requires R 4.6

1.0 In 20 of 49 releases 3.23

Description

The package offers functions to process multiple ChIP-seq BAM files and detect allele-specific events. Computes allele counts at individual variants (SNPs/SNVs), implements extensive QC steps to remove problematic variants, and utilizes a bayesian framework to identify statistically significant allele- specific events. BaalChIP is able to account for copy number differences between the two alleles, a known phenotypical feature of cancer samples.

Advisories

None published for Bioconductor

Test coverage

Line coverage

–

Expression

–

Tests / Examples

–

Functions

62 1 exported

Complexity

4.3 avg / 39 max

Call network

62 nodes / 49 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

4,687

Files

135

Compiled share

0%

Has compiled src

No

Language breakdown

R 2,902 (61.9%)Tests 1 (0%)Docs 854 (18.2%)Vignettes 930 (19.8%)

API

Exported functions

1

Internal functions

61

Testing

Has tests

Yes

Test-to-code ratio

0.00

testthat edition

–

Docs

Roxygen coverage

100%

Health & Security signals

Informational signals; not verdicts.

on.exit coverage

0%

Unsafe pattern score

0

Dep constraint coverage

0%

Secret pattern count

0

Bundled 3rd-party code

2 items

Portability & License

Min R version

3.3.1

System requirements

–

C++ standard

–

License

Artistic-2.0

License flags

SPDX valid, OSI approved

History

Versions

20

First release

2016-10-17

Latest release

2026-04-28

Avg cadence

182 days

Cold removal rate

–

Dep drift

0

LOC over versions

v3.4: 4,681 LOCv3.5: 4,686 LOCv3.6: 4,686 LOCv3.7: 4,686 LOCv3.8: 4,686 LOCv3.9: 4,686 LOCv3.10: 4,686 LOCv3.11: 4,686 LOCv3.12: 4,686 LOCv3.13: 4,687 LOCv3.14: 4,687 LOCv3.15: 4,687 LOCv3.16: 4,687 LOCv3.17: 4,687 LOCv3.18: 4,687 LOCv3.19: 4,687 LOCv3.20: 4,687 LOCv3.21: 4,687 LOCv3.22: 4,687 LOCv3.23: 4,687 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 · 281 wordsVignettesYes · 1 · dynamicNEWSYes · 0% structuredCitation fileYes · cites a publicationWebsitenot declared in DESCRIPTION
Help pages
21
Examples that run
100%15 run in a plain check
Exported functions with examples
100%
Documented parameters
100%
Return-value docs
100%
Help pages citing references
5%

Repository practices

Bioconductor git repository

Checks read the Bioconductor git repository (git.bioconductor.org), branch RELEASE_3_23.

No development-tooling practices detected in the Bioconductor git repository.

Datasets

Bundled datasets · 6
NameClassSizeAlso in
BaalObject–––
ENCODEexample–––
FAIREexample–––
UniqueMappability50bp_hg19–––
blacklist_hg19–––
pickrell2011cov1_hg19–––

All of BaalChIP's data objects

Topics

Maintainer
Ines de Santiago

Available on

CRANr2uBioconductorautoCRANCOPR

People (from the free-text Author field)

Cite

Cite this package

Run in R for the authors' preferred citation:

citation("BaalChIP")

The package provides a citation file that builds its entry when R runs it. Run citation() to see it.

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 BaalChIP version 1.38.0 [Data set]. HJJB, LLC. Data release v2026-10-25. https://doi.org/10.5281/zenodo.21843040

From data release v2026-10-25, 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