Skill detail
pacsomatic
Prepares and launches nf-core/pacsomatic matched tumor-normal PacBio HiFi genomics workflows from unaligned BAM inputs. Supports samplesheet generation, pinned Nextflow launch artifacts, local checks, LSF/Slurm/PBS Pro/SGE launcher submission, and startup troubleshooting. Use for pacsomatic run…
Why we recommend it: PacBio tumor-normal genomics workflow, adjacent to clinical genomics but research-oriented.
Needs (stated): Python
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- name: pacsomatic description: Prepares and launches nf-core/pacsomatic matched tumor-normal PacBio HiFi genomics workflows from unaligned BAM inputs. Supports samplesheet generation, pinned Nextflow launch artifacts, local checks, LSF/Slurm/PBS Pro/SGE launcher submission, and startup troubleshooting. Use for pacsomatic run preparation and execution, not general short-read somatic analysis or medical imaging PACS. license: MIT compatibility: Requires Python 3.10+ for the standard-library helper. Execution requires Bash, Nextflow >=24.04.2, a compatible Java runtime (current Nextflow supports Java 17-26), the selected container runtime and optionally a scheduler. Network access is needed for uncached pipeline code, plugins, references and containers. metadata: version: "1.4" skill-author: Beifang Niu contributors: Haidong, Wenchao upstream-pipeline: https://github.com/nf-core/pacsomatic upstream-revision: "24c84cb371b0339c1d65a4de9451671945e19772" last-reviewed: "2026-10-01" --- # pacsomatic ## When to use Use [scripts/run_pacsomatic.py](scripts/run_pacsomatic.py) to prepare one matched PacBio HiFi tumor/normal pair, generate a samplesheet and reproducible launch artifacts, and launch locally or submit the **Nextflow driver** to a scheduler. The pipeline realigns input BAMs; this helper targets unaligned HiFi BAMs and optional PacBio `.pbi` indexes. Do not substitute short reads or treat a BAM filename as evidence of platform, matched identity, or methylation information. The reviewed upstream `dev` commit is `24c84cb371b0339c1d65a4de9451671945e19772`. GitHub had no releases or tags on 2026-10-01, despite the internal manifest saying `1.0.0`. The helper pins that commit by default for `nf-core/pacsomatic`; it does not invent a release tag. This is a source-reviewed development workflow, not a clinically validated assay. See [references/pacsomatic_guide.md](references/pacsomatic_guide.md) for sources and scientific checks. ## Workflow 1. Obtain distinct tumor and normal BAM paths, patient ID, distinct sample IDs, output directory, and exactly one reference mode: `--fasta` or `--genome`. IDs and BAM/PBI/FASTA paths must have no whitespace. Local inputs must be nonempty regular files. Remote BAM/PBI/FASTA URIs are passed through without downloading or authenticating; use managed filesystem/cloud credentials, never embed secrets or signed URLs in generated files. 2. Confirm PacBio HiFi read groups and sample identity from acquisition metadata; confirm that MM/ML modification tags needed for methylation have been retained. Verify reference sequence/contig compatibility for every annotation resource. 3. Generate artifacts with `--dry-run`. This performs helper checks and writes files, but does **not** invoke the pipeline, validate BAM contents, check remote availability, resolve every pipeline parameter, or verify biological suitability. Missing runtime tools are warnings here. `--dry-run` cannot be combined with `--run`/`--submit`, cloning, or environment creation. 4. Review samplesheet, generated params YAML, script, pipeline revision, profiles, and branch-specific resources/skips. Existing artifacts require explicit `--overwrite`; input files can never be artifact targets. `config.yaml` is an operator reference, not an automatically loaded configuration file. 5. For execution, select the actual runtime with `--use-current-path` or an existing `--conda-env`. Load cluster modules **before** invoking the helper; `--module-load` only repeats those commands in the generated script. No Conda YAML is bundled; creating an environment needs `--conda-env-file` explicitly. 6. Use `--run` only for requested execution. For HPC, distinguish the outer launcher scheduler (`--executor`) from Nextflow's per-task `process.executor`, configured by a site profile or `--nextflow-config`. Driver CPU/memory requests do not constrain task resources. Read [references/config-aRead the full source on GitHub (opens external page)