% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/duckhts.R
\name{rduckhts_bigwig}
\alias{rduckhts_bigwig}
\title{Create a BigWig Signal Table}
\usage{
rduckhts_bigwig(
  con,
  table_name,
  path,
  region = NULL,
  blocks_per_iteration = 64L,
  overwrite = FALSE
)
}
\arguments{
\item{con}{A DuckDB connection with DuckHTS loaded.}

\item{table_name}{Name for the created table, or \code{NULL} to create the
\code{bigwig_data} view.}

\item{path}{Local path or URL to a BigWig file.}

\item{region}{Optional character vector of genomic regions such as
\code{c("chr1:1000-2000", "chr2:1-500")}. A single comma-separated string
is also accepted.}

\item{blocks_per_iteration}{Positive integer number of indexed BigWig data
blocks decoded per iterator batch.}

\item{overwrite}{Logical. If \code{TRUE}, replace an existing table.}
}
\value{
Invisibly returns \code{TRUE}.
}
\description{
Materializes stored zero-based, half-open BigWig intervals through the
DuckHTS extension. Region filters use htslib's one-based inclusive syntax;
a character vector is combined into one multi-region request and overlapping
requests emit each stored interval once.
}
