Skip to content

Clarify mixed-ploidy handling in dnascope-hybrid (--haploid_bed) #35

Closed

Description

@iamh2o

Question

What is the supported way to run sentieon-cli dnascope-hybrid on a human sample with both diploid and haploid regions (for example, an XY sample)? Is the absence of --haploid_bed from the Hybrid CLI intentional, a documentation gap, or a missing feature/bug?

We are prototyping mixed-ploidy support in a downstream fork, but want to avoid introducing scientifically incorrect behavior.

Current documented/source behavior

As of the current upstream main (1bf377d3ce79fc4d8c2dc221e1f696441e38349d):

  • The Hybrid documentation exposes only -b DIPLOID_BED.
  • dnascope_hybrid.py defines only -b/--bed and uses that shared BED for Hybrid small-variant calling and its CNV path.
  • The DNAscope LongRead documentation separately documents -b DIPLOID_BED --haploid_bed HAPLOID_BED for mixed-ploidy samples.
  • The CNVscope application note says male samples should use separate CNVscope and CNVModelApply passes over disjoint diploid and haploid BEDs, followed by VCF combination.
  • Sentieon 202503.04 notes improved haploid CNVscope calling.

Relevant documentation:

Downstream behavior we are considering

For an XY sample, our candidate fork would accept:

sentieon-cli dnascope-hybrid \
  ... \
  -b hg38_diploid_male_no_alt.bed \
  --haploid_bed hg38_haploid_male_no_alt.bed \
  sample.vcf.gz

The candidate implementation would:

  1. Require -b whenever --haploid_bed is supplied.
  2. Run one diploid CNVscope -> CNVModelApply pass restricted to the diploid BED and one haploid pass restricted to the haploid BED, using the same cnv.model member from the composite Hybrid bundle.
  3. Combine those disjoint CNV VCFs in reference order.
  4. Run the Hybrid LongReadSV component over the sorted/merged union of the diploid and haploid BEDs.
  5. Refuse to run Hybrid small variants/gVCF with --haploid_bed until their supported haploid semantics and model contract are confirmed.

For XX samples, it would retain one diploid pass using the female diploid BED.

Questions for Sentieon

  1. Does current Hybrid -b intentionally restrict all Hybrid outputs to only those intervals, meaning non-PAR X/Y are omitted when the official male diploid BED is supplied?
  2. Is there an existing supported or planned --haploid_bed contract for dnascope-hybrid?
  3. For Hybrid CNV, is the two-pass scheme above correct with the cnv.model from HybridIlluminaONT2.0.bundle? Should CNVModelApply receive an interval too, or only the already interval-restricted CNVscope VCF?
  4. For Hybrid LongReadSV, is using the union of diploid and haploid BEDs correct? Does LongReadSV have any ploidy-sensitive genotype behavior that requires the regions to remain separate?
  5. What is the supported approach for Hybrid SNV/indel and gVCF calling in haploid non-PAR X/Y? Can the Hybrid model be used in separate haploid processing, or is another model/pipeline required?
  6. Is Sentieon 202503.04 required for the supported male Hybrid behavior?

In short: would adding --haploid_bed with the behavior above close a gap, or would any part of it induce incorrect calls? We would be happy to shape an upstream PR around the supported contract once clarified.

Activity

  1. iamh2o commented on Aug 27, 2026

    @iamh2o
    Author

    A concrete review branch is now available at https://github.com/iamh2o/sentieon-cli/tree/codex/hybrid-ploidy-components-1.7.3i (commit 4218c04). It implements the proposed two-pass CNVscope path and LongReadSV region union, but deliberately rejects Hybrid small-variant/gVCF execution when --haploid_bed is present. We have not tagged or used it for production calls; confirmation of the supported Hybrid haploid small-variant/model contract remains the release gate.

  2. DonFreed commented on Aug 29, 2026

    @DonFreed
    Contributor

    Sentieon version 202503.04 (which was recently released) updated CNVscope to explicitly support CNV calling across both diploid and haploid chromosomes. Here is the new command line usage:

    $ sentieon driver -h --algo CNVscope
    Usage for CNVscope:
      driver -r reference.fasta [driver_options] \
             --algo CNVscope --model CNV_model_file [algo_options] output.vcf[.gz]
    
    Options for CNVscope:
          --sex             Specify sex for human samples (M or F). If not specified, assumes a diploid organism.
          --par             Specify BED file for PAR region (required for male samples)
          --dump_probes     Dump probe information for visualization
    

    Additionally, version 202503.04 introduced support for a new hybrid pangenome pipeline. Development and model training for this new pipeline is currently in-progress (#33). For Human samples, the new pipeline can be used with the HPRC pangenome. Compared to the dnascope-hybrid pipeline, the pangenome pipeline has significant runtime and accuracy improvements.

    The next version of the sentieon-cli will update CNVscope calling (across all pipelines) to use the new --sex and --par arguments introduced in Sentieon v202503.04 to perform correct handling of male/female samples.

    LongReadSV and the DNAscope hybrid model currently only support diploid variant calling. If you are using separate diploid and haploid bed files, I would pass the union of the diploid and haploid bed files to these variant callers.

  3. DonFreed commented on Sep 27, 2026

    @DonFreed
    Contributor

    Closing this for now. Feel free to re-open if you have additional questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions