Infer gene regulatory networks (GRNs) from gene expression matrices using GRNBoost2 or GENIE3; use when analyzing bulk or single-cell RNA-seq to identify TF→target regulatory relationships.
Start a fresh conversation. Replace the highlighted placeholders.
Use arboreto to infer a ranked TF-to-target gene regulatory network from [normalized expression matrix], using [GRNBoost2 or GENIE3], and deliver the weighted edge list with the selected method and relevant runtime assumptions.
Required inputs
[normalized expression matrix]
[GRNBoost2 or GENIE3]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: arboretodescription: Infer gene regulatory networks (GRNs) from gene expression matrices using GRNBoost2 or GENIE3; use when analyzing bulk or single-cell RNA-seq to identify TF→target regulatory relationships.license: MITauthor: AIPOCH
Input: a gene expression matrix (e.g., TSV) where rows typically represent samples/cells and columns represent genes (exact expectations depend on scripts/infer_network.py).
Output: a ranked edge list representing inferred regulatory relationships (TF → target) with an importance/weight score.
Algorithms
GRNBoost2: uses gradient boosting to estimate feature importance of candidate regulators for each target gene; generally preferred for larger datasets due to speed and scalability.
GENIE3: uses random forests to compute regulator importance per target gene; a classic baseline for GRN inference.
For a detailed comparison and practical guidance, refer to references/algorithms.md.
Parallel/Distributed Execution
Computation is parallelized with Dask, enabling scaling from local multi-core execution to distributed clusters.
Cluster configuration and deployment considerations are documented in references/distributed_computing.md.
Key Parameters
--algo: selects the inference method (grnboost2 or genie3), affecting runtime and model behavior.
Additional runtime/cluster parameters (if exposed by the script) typically control Dask scheduling, worker counts, and resource usage.