Part 5 of 5. Four posts of reasons are enough. This one is about what it looks like when you actually use the thing, and about the name, which people ask about more often than they ask about normalization. Fair enough. One small note first. The command examples below use the usual command line options,… Read More: Using SimurgArray, and the bird behind the name »
Part 4 of 5. Right now SimurgArray lives in a private repository on my own Git server. It has a license, a changelog, a user guide, wheels, a Docker image and a version number that just became 2.0.0. In other words, it looks public. It is not, yet. Publishing code is easy. Publishing it responsibly… Read More: SimurgArray going public: what it takes, and a calendar »
Part 3 of 5. “Benefit to humanity” is a big phrase for a tool that mostly reads binary files. I will try to keep this post the right size. SimurgArray will not cure anything. What it can do is lower a few barriers that currently decide who gets to do genetics research and how much… Read More: SimurgArray: What good could it do? »
Part 2 of 5. Whenever someone tells me they are writing their own genotype caller, my first instinct is to ask whether they have looked around. So it is only fair that I answer the same question about myself. I did look around. There is a lot of good work out there. Some of it… Read More: Are there SimurgArray alternatives? Yes. Why build it anyway? »
Part 1 of 5. Every genotyping array tells a small story before it tells you anything about DNA. A glass slide goes into a scanner, the scanner writes two IDAT files per sample (one red, one green), and a few hundred thousand bead intensities wait for someone to turn them into genotypes. That someone is… Read More: Why SimurgArray should exist? »