Parabricks
Purpose
Use this skill to discover the right NVIDIA Parabricks pbrun command, assess
runtime readiness, and generate version-aware command guidance for individual
tools.
Do not use this skill for whole-workflow inspection, acceleration planning,
or wiring optional GPU branches. For pipeline-level work, use
genomics-workflow-acceleration.
When to Use This Skill
- Which
pbrun tool fits the user's data and goal
- GPU, driver, Docker, container, storage, or installation readiness
- Command shape, flags, and validation for a specific Parabricks tool
- Reference/index compatibility and CPU-to-Parabricks option translation
- Troubleshooting a single Parabricks command or tool family
- Planning-only or "do not run" questions about a named
pbrun tool (for
example reference/index compatibility, output naming, or flag validity). Use
this skill's references to answer; do not skip it because nothing will be
executed.
Prerequisites
- Command guidance: No Parabricks/NGC credential or local GPU/container
runtime is required to read references or generate commands.
- Readiness helper: Requires Bash and GNU coreutils
timeout (or gtimeout)
on the host being inspected. Missing runtime components are reported as
readiness gaps; without a timeout utility it exits before running probes.
- STAR translation helper: Requires Python 3.7 or newer, using only the
standard library. It does not require a GPU or a Parabricks installation.
- Execution: The documented Docker commands require a supported Linux host,
an NVIDIA GPU with sufficient memory, a compatible NVIDIA driver, Docker,
NVIDIA Container Toolkit, and access to the selected Parabricks image.
Pulling the image may require an NGC API key for authentication to nvcr.io.
See runtime-environment.md for
version-specific requirements and checks.
Tool scope: read this skill's references and user-supplied manifests; write only
requested command artifacts. Use the bundled helpers for translation or an
authorized host inspection. Documentation lookups use docs.nvidia.com; image
access uses the selected registry only for authorized container execution.
These instructions do not grant tool permissions; the host's permission policy
still applies to shell, file, network and optional documentation MCP access.
Inputs
Use the user's explicit arguments and supplied manifests as the source of
truth; use prior context only where it does not conflict. Read a named manifest
before translating it. For command guidance, identify the assay, input paths,
reference/index provenance, outputs and target release. Ask only for missing
facts that change the answer; label unresolved template values as placeholders.
Required inputs are the selected tool's read/reference and output arguments.
Optional inputs include intervals, resource bundles, logs and tuning parameters
when supported by that tool; do not invent them to fill a template.
Runtime-only questions do not need sample metadata. Supplied deployment paths
are not permission to probe local data or hardware.
If the user is unsure which tool applies, scan the Tool Reference Index
below, then load the matching references/pbrun-<tool>.md file.
Limitations
This skill routes and guides Parabricks commands. It does not install
Parabricks, infer missing sample metadata, guarantee output parity, provide
clinical interpretation, or promise exact runtime without benchmark data.
Instructions
- Identify the requested release. The option references cover v4.8.0; examples
from another release are labeled. A software version and image tag can
differ: NVIDIA's 4.8.0 image is tagged
4.8.0-1. Preserve the user's verified
image selection; use command-conventions.md
for the shared launch and validation contract.
- Classify the request:
- Runtime → runtime-environment.md
- Tool discovery → Tool Reference Index (below)
- Specific command → matching
references/pbrun-<tool>.md. Read it
before any web search or MCP lookup; use those only to verify
version-sensitive details the reference does not settle.
- Combine the tool-specific mapping with shared-options.md
rows whose Tools column names the selected command. For STAR argument
arrays or multi-lane batches,
use the local translation helper; it preserves
tokens and reports unmapped semantics without executing a workload.
- Collect missing biological and filesystem context before generating commands.
- Return the requested command or artifact with unresolved assumptions. For
planning-only work, check command text against the references and supplied
facts. Filesystem, container and output checks apply only to an authorized
execution. Do not turn command preparation into a readiness inspection.
Available Scripts
Run these from the skill directory containing this file; paths are relative to
that directory. See the helper prerequisites above.
| Script |
Purpose |
Arguments |
scripts/check_parabricks_runtime.sh |
Inspect the execution host; report gaps without installing anything |
--path DIR (repeatable), --format text|json, --timeout SECONDS; container probes require --run-container-check or --run-parabricks-check with --parabricks-version TAG / --parabricks-image IMAGE |
scripts/translate_star_to_parabricks.py |
Convert explicit STAR argument arrays to reviewed command drafts |
--input FILE or --input -; request and output schema |
Output Format
For explanations, give the decision, complete command, and remaining checks.
For file requests, write the specified path and schema, then read back and
validate the artifact against the input manifest. Report all job IDs, omitted
options and unresolved output contracts. Do not replace supplied values with
illustrative examples. The runtime helper's JSON has schema_version, checks
and readiness results; the translator emits status, draft_argv, command,
notes, issues and untranslated for each request.
Tool Reference Index
If the command is named, open references/pbrun-<command>.md directly.
For tool selection and official manual links, use tool-index.md.
Common routes:
| Request |
Reference |
| DNA FASTQ alignment / RNA STAR translation |
fq2bam / rna_fq2bam |
| Existing BAM germline calls / tumor-normal calls |
haplotypecaller / mutectcaller |
| Giraffe graph alignment |
giraffe |
| STAR-Fusion migration |
starfusion |
| Recalibration / apply a recalibration report |
bqsr / applybqsr |
| BAM metrics / multiple metric families |
bammetrics / collectmultiplemetrics |
| GVCF indexing / joint genotyping |
indexgvcf / genotypegvcf |
| Panel-of-normals preparation / annotation |
prepon / postpon |
| BWA performance options |
performance |
Examples
Runtime Readiness
For GPU, driver, Docker, container, storage, or installation questions, read
runtime-environment.md and prefer:
bash scripts/check_parabricks_runtime.sh --format json
Add --path <dir> for known input/output/tmp paths. Run container probes only
with user consent.
STAR Translation
python3 scripts/translate_star_to_parabricks.py --input requests.json
Prepare the request using the translation schema.
Review issues and untranslated before using the draft. Tool references show
the pbrun portion; the shared container envelope is documented once in
command-conventions.md.
Troubleshooting
| Error |
Cause |
Solution |
| Multiple plausible tools |
Data type or goal underspecified |
Ask for assay, inputs, caller preference, desired output; use Tool Reference Index |
| Exact flag requested |
Options are version-sensitive |
Check the selected tool reference, NVIDIA docs, or pbrun <tool> --help |
| Runtime question |
GPU, Docker, drivers, or storage |
Use runtime-environment reference and diagnostic script |
| Wrong tool family |
Assay or input type unclear |
Confirm DNA/RNA/methylation/long-read/pangenome before routing |
| CUDA or memory failure |
Runtime not ready or GPU memory constrained |
Assess runtime before tuning command flags |
| Documentation MCP unavailable |
Connection, timeout or server error |
Use the bundled release reference first; for an unresolved fact, fall back to the official versioned manual and mark any remaining uncertainty |
Guardrails
- Treat command availability and options as version-sensitive.
- Do not infer exact flags from command names alone.
- Do not collapse standalone tools and full pipelines when explaining tradeoffs.
- Do not substitute DNA
fq2bam for RNA, or germline for somatic callers.
- Do not invent sample names, read groups, reference builds, known-sites files,
model files, graph resources, container tags, or output paths.
- Do not install, upgrade, or modify packages. Label setup commands as user-run.
- Do not claim CPU execution of Parabricks tools.
- Do not claim biological or VCF parity without a comparison run.
- Use the optional documentation MCP server only for details the bundled
references do not settle. If its connection fails, avoid repeated discovery
or lookup loops; use the official manual. Never claim a failed lookup verified
an option. Documentation access does not require genomic data or credentials.
Key References
1---2name: parabricks3description: >-4 Plan NVIDIA Parabricks pbrun commands, translate CPU options and check runtime5 readiness. Use for individual tools, including planning-only questions.6license: CC-BY-4.0 AND Apache-2.07metadata:8 source: https://skillmd.com/skills/nvidia/parabricks9 author: "Angel Pizarro <apizarro@nvidia.com>"10 version: "1.4.0"11 tags:12 - parabricks13 - genomics14 - nvidia15---1617# Parabricks1819## Purpose2021Use this skill to discover the right NVIDIA Parabricks `pbrun` command, assess22runtime readiness, and generate version-aware command guidance for individual23tools.2425Do **not** use this skill for whole-workflow inspection, acceleration planning,26or wiring optional GPU branches. For pipeline-level work, use27`genomics-workflow-acceleration`.2829## When to Use This Skill3031- Which `pbrun` tool fits the user's data and goal32- GPU, driver, Docker, container, storage, or installation readiness33- Command shape, flags, and validation for a specific Parabricks tool34- Reference/index compatibility and CPU-to-Parabricks option translation35- Troubleshooting a single Parabricks command or tool family36- Planning-only or "do not run" questions about a named `pbrun` tool (for37 example reference/index compatibility, output naming, or flag validity). Use38 this skill's references to answer; do not skip it because nothing will be39 executed.4041## Prerequisites4243- **Command guidance:** No Parabricks/NGC credential or local GPU/container44 runtime is required to read references or generate commands.45- **Readiness helper:** Requires Bash and GNU coreutils `timeout` (or `gtimeout`)46 on the host being inspected. Missing runtime components are reported as47 readiness gaps; without a timeout utility it exits before running probes.48- **STAR translation helper:** Requires Python 3.7 or newer, using only the49 standard library. It does not require a GPU or a Parabricks installation.50- **Execution:** The documented Docker commands require a supported Linux host,51 an NVIDIA GPU with sufficient memory, a compatible NVIDIA driver, Docker,52 NVIDIA Container Toolkit, and access to the selected Parabricks image.53 Pulling the image may require an NGC API key for authentication to [nvcr.io](https://nvcr.io).54 See [runtime-environment.md](references/runtime-environment.md) for55 version-specific requirements and checks.5657Tool scope: read this skill's references and user-supplied manifests; write only58requested command artifacts. Use the bundled helpers for translation or an59authorized host inspection. Documentation lookups use [docs.nvidia.com](https://docs.nvidia.com); image60access uses the selected registry only for authorized container execution.61These instructions do not grant tool permissions; the host's permission policy62still applies to shell, file, network and optional documentation MCP access.6364## Inputs6566Use the user's explicit arguments and supplied manifests as the source of67truth; use prior context only where it does not conflict. Read a named manifest68before translating it. For command guidance, identify the assay, input paths,69reference/index provenance, outputs and target release. Ask only for missing70facts that change the answer; label unresolved template values as placeholders.71Required inputs are the selected tool's read/reference and output arguments.72Optional inputs include intervals, resource bundles, logs and tuning parameters73when supported by that tool; do not invent them to fill a template.74Runtime-only questions do not need sample metadata. Supplied deployment paths75are not permission to probe local data or hardware.7677If the user is unsure which tool applies, scan the **Tool Reference Index**78below, then load the matching `references/pbrun-<tool>.md` file.798081## Limitations8283This skill routes and guides Parabricks commands. It does not install84Parabricks, infer missing sample metadata, guarantee output parity, provide85clinical interpretation, or promise exact runtime without benchmark data.8687## Instructions88891. Identify the requested release. The option references cover v4.8.0; examples90 from another release are labeled. A software version and image tag can91 differ: NVIDIA's 4.8.0 image is tagged `4.8.0-1`. Preserve the user's verified92 image selection; use [command-conventions.md](references/command-conventions.md)93 for the shared launch and validation contract.942. Classify the request:95 - **Runtime** → [runtime-environment.md](references/runtime-environment.md)96 - **Tool discovery** → **Tool Reference Index** (below)97 - **Specific command** → matching `references/pbrun-<tool>.md`. Read it98 **before** any web search or MCP lookup; use those only to verify99 version-sensitive details the reference does not settle.1003. Combine the tool-specific mapping with [shared-options.md](references/shared-options.md)101 rows whose **Tools** column names the selected command. For STAR argument102 arrays or multi-lane batches,103 use the local [translation helper](references/rna-translation.md); it preserves104 tokens and reports unmapped semantics without executing a workload.1054. Collect missing biological and filesystem context before generating commands.1065. Return the requested command or artifact with unresolved assumptions. For107 planning-only work, check command text against the references and supplied108 facts. Filesystem, container and output checks apply only to an authorized109 execution. Do not turn command preparation into a readiness inspection.110111## Available Scripts112113Run these from the skill directory containing this file; paths are relative to114that directory. See the helper prerequisites above.115116| Script | Purpose | Arguments |117| --- | --- | --- |118| `scripts/check_parabricks_runtime.sh` | Inspect the execution host; report gaps without installing anything | `--path DIR` (repeatable), `--format text\|json`, `--timeout SECONDS`; container probes require `--run-container-check` or `--run-parabricks-check` with `--parabricks-version TAG` / `--parabricks-image IMAGE` |119| `scripts/translate_star_to_parabricks.py` | Convert explicit STAR argument arrays to reviewed command drafts | `--input FILE` or `--input -`; [request and output schema](references/rna-translation.md) |120121## Output Format122123For explanations, give the decision, complete command, and remaining checks.124For file requests, write the specified path and schema, then read back and125validate the artifact against the input manifest. Report all job IDs, omitted126options and unresolved output contracts. Do not replace supplied values with127illustrative examples. The runtime helper's JSON has `schema_version`, `checks`128and readiness results; the translator emits `status`, `draft_argv`, `command`,129`notes`, `issues` and `untranslated` for each request.130131## Tool Reference Index132133If the command is named, open `references/pbrun-<command>.md` directly.134For tool selection and official manual links, use [tool-index.md](references/tool-index.md).135Common routes:136137| Request | Reference |138| --- | --- |139| DNA FASTQ alignment / RNA STAR translation | [fq2bam](references/pbrun-fq2bam.md) / [rna_fq2bam](references/pbrun-rna_fq2bam.md) |140| Existing BAM germline calls / tumor-normal calls | [haplotypecaller](references/pbrun-haplotypecaller.md) / [mutectcaller](references/pbrun-mutectcaller.md) |141| Giraffe graph alignment | [giraffe](references/pbrun-giraffe.md) |142| STAR-Fusion migration | [starfusion](references/pbrun-starfusion.md) |143| Recalibration / apply a recalibration report | [bqsr](references/pbrun-bqsr.md) / [applybqsr](references/pbrun-applybqsr.md) |144| BAM metrics / multiple metric families | [bammetrics](references/pbrun-bammetrics.md) / [collectmultiplemetrics](references/pbrun-collectmultiplemetrics.md) |145| GVCF indexing / joint genotyping | [indexgvcf](references/pbrun-indexgvcf.md) / [genotypegvcf](references/pbrun-genotypegvcf.md) |146| Panel-of-normals preparation / annotation | [prepon](references/pbrun-prepon.md) / [postpon](references/pbrun-postpon.md) |147| BWA performance options | [performance](references/performance.md) |148149## Examples150151### Runtime Readiness152153For GPU, driver, Docker, container, storage, or installation questions, read154[runtime-environment.md](references/runtime-environment.md) and prefer:155156```bash157bash scripts/check_parabricks_runtime.sh --format json158```159160Add `--path <dir>` for known input/output/tmp paths. Run container probes only161with user consent.162163### STAR Translation164165```bash166python3 scripts/translate_star_to_parabricks.py --input requests.json167```168169Prepare the request using the [translation schema](references/rna-translation.md).170Review `issues` and `untranslated` before using the draft. Tool references show171the `pbrun` portion; the shared container envelope is documented once in172[command-conventions.md](references/command-conventions.md).173174## Troubleshooting175176| Error | Cause | Solution |177|-------|-------|----------|178| Multiple plausible tools | Data type or goal underspecified | Ask for assay, inputs, caller preference, desired output; use Tool Reference Index |179| Exact flag requested | Options are version-sensitive | Check the selected tool reference, NVIDIA docs, or `pbrun <tool> --help` |180| Runtime question | GPU, Docker, drivers, or storage | Use runtime-environment reference and diagnostic script |181| Wrong tool family | Assay or input type unclear | Confirm DNA/RNA/methylation/long-read/pangenome before routing |182| CUDA or memory failure | Runtime not ready or GPU memory constrained | Assess runtime before tuning command flags |183| Documentation MCP unavailable | Connection, timeout or server error | Use the bundled release reference first; for an unresolved fact, fall back to the official versioned manual and mark any remaining uncertainty |184185## Guardrails186187- Treat command availability and options as version-sensitive.188- Do not infer exact flags from command names alone.189- Do not collapse standalone tools and full pipelines when explaining tradeoffs.190- Do not substitute DNA `fq2bam` for RNA, or germline for somatic callers.191- Do not invent sample names, read groups, reference builds, known-sites files,192 model files, graph resources, container tags, or output paths.193- Do not install, upgrade, or modify packages. Label setup commands as user-run.194- Do not claim CPU execution of Parabricks tools.195- Do not claim biological or VCF parity without a comparison run.196- Use the optional documentation MCP server only for details the bundled197 references do not settle. If its connection fails, avoid repeated discovery198 or lookup loops; use the official manual. Never claim a failed lookup verified199 an option. Documentation access does not require genomic data or credentials.200201## Key References202203- Parabricks documentation MCP server:204 <https://docs.nvidia.com/clara/parabricks/_mcp/server>205- Parabricks tool index:206 <https://docs.nvidia.com/clara/parabricks/tool-reference>207- Output accuracy and compatible CPU software versions:208 <https://docs.nvidia.com/clara/parabricks/about-parabricks/software-overview/output-accuracy-and-compatible-cpu-software-versions>209- Getting started:210 <https://docs.nvidia.com/clara/parabricks/get-started>211- Overview:212 <https://docs.nvidia.com/clara/parabricks/about-parabricks>213- 4.8.0 release notes (changes from 4.7.1):214 <https://docs.nvidia.com/clara/parabricks/v4.8.0/about-parabricks/release-notes/4-8-0-1-release-notes>