Skip to content

VCF-based prediction is unnecessarily slow due to full VCF scan #61

Description

@yoshihikosuzuki

VCF-based expression predictions are slower than necessary because bcftools consensus is run against the full input VCF even when only a small region is specified.

I observed this clearly in tests/test_ad_risk.py and notebooks/vcf2exp.py, where the prediction took ~20 min using B200 GPU.

I have tested a simple fix (make small temporary VCF only for the specified region and apply it) and confirmed it reduces the same workload to ~2 min.

Metadata

Metadata

Assignees

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