pacsomatic

Generate pacsomatic samplesheets and Nextflow launch artifacts from tumor-normal BAM inputs.

Updated May 24, 2026
One-click install
npx skills add https://github.com/Estrella-231/Mathematical_modeling_tongmeng --skill pacsomatic-estrella-231
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pacsomatic
Source: https://github.com/Estrella-231/Mathematical_modeling_tongmeng/tree/main/.agents/skills/pacsomatic
Command: npx skills add https://github.com/Estrella-231/Mathematical_modeling_tongmeng --skill pacsomatic-estrella-231

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires argparse, csv, os, re, shlex, shutil, subprocess, sys, pathlib, urllib.parse, and includes scripts (resource) and references (resource) components.

What problem does it solve?

It solves the problem of reliably preparing matched tumor-normal PacBio HiFi runs by validating BAM/reference inputs, generating a correct pacsomatic samplesheet, and producing reproducible Nextflow launch artifacts for local or scheduler execution.

Core Features & Use Cases

  • Samplesheet generation: Creates a pacsomatic-compatible samplesheet with required columns (patient,sample,status,bam,pbi).
  • Reproducible launch artifact creation: Writes a generated params YAML plus an executor-specific launch script so reruns are consistent.
  • Pre-flight validation and troubleshooting: Performs input/path checks, validates identifiers (no spaces), verifies runtime/tool availability (e.g., Nextflow/Java/container tooling), and returns actionable failure points.
  • Dry-run then execute/submit workflow: Supports generate-only and dry-run validation, then optional execution/submission using local, LSF, Slurm, PBS, or SGE.
  • Use case: You have one tumor BAM and one normal BAM for a patient and need to validate inputs, generate the correct artifacts, and then submit a scheduler job without manually crafting Nextflow commands.

Quick Start

Run a dry-run validation and generate the pacsomatic samplesheet and launch assets for your tumor-normal BAM pair by calling the helper script with your BAM paths, IDs, output directory, and either --genome GRCh38 or --fasta /path/to/reference.fa.

Frequently Asked Questions about pacsomatic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a Nextflow samplesheet for nf-core/pacsomatic tumor-normal analysis?

To generate a Nextflow samplesheet for nf-core/pacsomatic tumor-normal analysis, run a helper script with your matched tumor and normal BAM paths, patient IDs, and an output directory to create a compliant CSV file with required columns including patient, sample, status, bam, and pbi.

Can I submit a Nextflow workflow to an HPC scheduler like Slurm or LSF for PacBio HiFi runs?

Yes, you can submit a Nextflow workflow to an HPC scheduler like Slurm or LSF for PacBio HiFi runs. The tool generates executor-specific launch scripts and detects job IDs, supporting local, LSF, Slurm, PBS, and SGE scheduler submissions.

What's the best way to validate inputs before running a matched tumor-normal Nextflow pipeline?

The best way to validate inputs before running a matched tumor-normal Nextflow pipeline is to use a pre-flight validation script that checks BAM and reference paths, verifies identifiers have no spaces, and confirms runtime tool availability like Nextflow and Java before execution.

Does the pacsomatic preparation tool support dry-run checks for Nextflow pipeline reproducibility?

Yes, the pacsomatic preparation tool supports dry-run checks for Nextflow pipeline reproducibility. You can perform a generate-only run or dry-run validation to test launch artifacts before actual execution or scheduler submission.

Why does my Nextflow launch fail when starting a tumor-normal bioinformatics workflow?

Your Nextflow launch may fail when starting a tumor-normal bioinformatics workflow due to missing runtime dependencies like Java, invalid input paths, or identifiers containing spaces. A pre-flight validation script can identify these actionable failure points before execution.