• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

hammerlab / varcode / 93 / 2
87%
master: 88%

Build:
Build:
LAST BUILD BRANCH: variants-vcf-output
DEFAULT BRANCH: master
Ran 22 Apr 2016 08:35PM UTC
Files 21
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

22 Apr 2016 07:57PM UTC coverage: 86.811%. First build
93.2

push

travis-ci

timodonnell
Parse sample info, including support for multisample VCFs

Add per-sample info to vcf loading. Works the same whether you use `load_vcf`
or `load_vcf_fast`.

The VariantCollection.metadata entry for each variant now includes a
`sample_info` entry, which maps samples names to a dict of pyvcf-parsed
per-sample attributes for that sample.

I think this takes care of the "support multisample vcf" issues. Summary is:

 * a `VariantCollection` is multisample: it contains whatever variants were in your VCF
 * the `VariantCollection.metadata` dict includes per-sample info (as well as across-sample info from the INFO column and filters, etc.)
 * if you care about what sample a variant was "called" in, it is left to the user to look at the genotype and decide what to do. For most VCFs this will be available in `VariantCollection.metadata[variant]['sample_info']['GT']` and the value '0/0' means no-call and anything else means there was a call. We don't assume anything about this field here though (similarly to pyvcf).

1119 of 1289 relevant lines covered (86.81%)

0.87 hits per line

Source Files on job 93.2
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 93
  • Travis Job 93.2
  • e53b2355 on github
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc