HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
google
deepvariant
Python2018–2018
google / deepvariant

deepvariant

DeepVariant is an analysis pipeline that uses a deep neural network to call genetic variants from next-generation DNA sequencing data.

3Distinct people
3Mentions
0Explicit recommenders
3.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

DeepVariant is an analysis pipeline that uses a deep neural network to call genetic variants from next-generation DNA sequencing data.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month3 dated mentions

Observed mentions: 2018-02-21 00:24:39 UTC to 2018-11-02 16:44:15 UTC.

0122018-02-01 00:00:00 UTC to 2018-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 20182018-03-01 00:00:00 UTC to 2018-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-01 00:00:00 UTC to 2018-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-05-01 00:00:00 UTC to 2018-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-01 00:00:00 UTC to 2018-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 20182018-07-01 00:00:00 UTC to 2018-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-08-01 00:00:00 UTC to 2018-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-09-01 00:00:00 UTC to 2018-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-01 00:00:00 UTC to 2018-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-11-01 00:00:00 UTC to 2018-12-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsNov 2018

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 20182018-02-01 00:00:00 UTC2018-03-01 00:00:00 UTC101
Mar 20182018-03-01 00:00:00 UTC2018-04-01 00:00:00 UTC000
Apr 20182018-04-01 00:00:00 UTC2018-05-01 00:00:00 UTC000
May 20182018-05-01 00:00:00 UTC2018-06-01 00:00:00 UTC000
Jun 20182018-06-01 00:00:00 UTC2018-07-01 00:00:00 UTC000
Jul 20182018-07-01 00:00:00 UTC2018-08-01 00:00:00 UTC000
Aug 20182018-08-01 00:00:00 UTC2018-09-01 00:00:00 UTC000
Sep 20182018-09-01 00:00:00 UTC2018-10-01 00:00:00 UTC000
Oct 20182018-10-01 00:00:00 UTC2018-11-01 00:00:00 UTC000
Nov 20182018-11-01 00:00:00 UTC2018-12-01 00:00:00 UTC202

What Hacker News says

3 sources
Yeah, the way they talk about this is admittedly confusing. The best way for me to think about it (from [1]) is to mentally add quotation marks around the word “image” whenever the methods mention it. Mathematically the data is stored in higher-dimensional tensors with one dimension representing genomic coordinates, another dimension representing the sequence depth (i.e. one row per sequence read), and additional dimensions representing features of the sequence (such as nucleoside identity, read direction, error probability, match/mismatch with the reference, etc). I use almost the same kinds of tensors for work that has no tangible relation to images or visualisation. It’s simply the most straightforward way of representing this data as a tensor. But the similarity to images is so tantalising that even the paper’s methods [2] fall prey t
Read the rest
o this, even though the dimensionality and minor details are wrong. Furthermore, the term “pileup image” refers to a common way of visualising genome–read alignments [3]. The DeepVariant tensor is not a pileup image but it is very close. And the tensor can be converted in to an image [4] but as mentioned this requires some transformations (splitting the channels, and rescaling the values). [1] https://bioinformatics.stackexchange.com/q/4098/29 [2] I initially claimed the paper didn’t mention this. That’s wrong; apologies. [3] https://www.google.com/search?tbm=isch&q=genome+pileup [4] https://github.com/google/deepvariant/blob/r0.7/docs/visuali...
In Machine learning spots natural selection at work in human genome
Yeah, definitely interested ;) Any chance the course has room for the other side of the coin? Namely, how neuroevolution and genetic strategies inform deep reinforcement learning? Am also interested in learning about the state-of-the-art in cloud based packages. I noticed recently Google released a tool called DeepVariant for use on their genomics platform. https://github.com/google/deepvariant Creating a universal SNP and small indel variant caller with deep neural networks https://www.biorxiv.org/content/early/2018/01/09/092890
In CS 522: Machine Learning Approaches to Decode the Human Genome

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.