Slashdot Mirror


Pocket-Sized DNA Reader Used To Scan Entire Human Genome Sequence (arstechnica.com)

An anonymous reader quotes a report from Ars Technica: A few years back, a company called Oxford Nanopore announced it was developing a radically different way of sequencing DNA. Its approach involved taking single strands of the double helix and stuffing them through a protein pore. With a small bit of current flowing across the pore, the four bases of DNA each created a distinct (if tiny) change in the voltage as it passed through. These could be used to read the DNA one base at a time as it wiggled through the pore. After several years of slow progress, Oxford Nanopore announced that its sequencing hardware would be as distinctive as its wetware: a USB device that could fit comfortably in a person's hand. As the first devices went out to users, it became clear that the device had some pros and cons. On the plus side, the device was quick and could be used without requiring a large facility to support it. It could also read very long stretches of DNA at once. But the downside was significant: it made lots of mistakes.

With a few years of experience, people are now starting to learn to make the most of the devices, as demonstrated by a new paper in which researchers use it to help sequence a human genome. By using the machine's long reads -- in one case, nearly 900,000 bases from one DNA molecule -- the authors were able to get data out of areas of the human genome that resisted characterization before. And they were able to distinguish between the two sets of chromosomes (one from mom, one from dad) and locate areas of epigenetic control in many areas of the genome. In light of all the distinct information it can provide, the machine's error rate is seeming like less of a problem.

76 comments

  1. GATTACA, anyone? by sehlat · · Score: 1

    Just remember it was a cautionary tale and NOT an operations manual.

    1. Re:GATTACA, anyone? by Gravis+Zero · · Score: 3, Insightful

      Just remember it was a cautionary tale and NOT an operations manual.

      Don't be ridiculous! I mean, everyone knows that 1984 is the real instruction manual. ;)

      --
      Anons need not reply. Questions end with a question mark.
    2. Re:GATTACA, anyone? by iggymanz · · Score: 1

      our brains already do the gross DNA analysis with sexism, racism and stereotypes, this is just a fine tuning.

    3. Re:GATTACA, anyone? by sehlat · · Score: 1, Troll

      Don't be ridiculous! I mean, everyone knows that 1984 is the real instruction manual. ;)

      No, it isn't. Orwell was an optimist.

    4. Re:GATTACA, anyone? by Anonymous Coward · · Score: 0

      Stereotypes literaaly means solid impression.

      It is the modern sensibilities who have problems with general facts, when it runs counter to taught narrative. Cognitive dissonance requires them to shit on IQ tests and to continually point out (and exaggerate) rare exceptions as if it were the norm despite being expected occurence via bell curve.

    5. Re:GATTACA, anyone? by Anonymous Coward · · Score: 0

      especially compared to Huxley, who was much more on Point. Even without rats

    6. Re:GATTACA, anyone? by Anonymous Coward · · Score: 1

      Not quite.
      The problem with stereotypes is that the same inductive reasoning that goes into creating superstitions is the basis for stereotypes. And while that kind of reasoning has it's uses, well. The turkey that walks up to the farmer gets a treat every day of it's life... until Thanksgiving.
      In particular there are two ways in which stereotypes fail to be useful:

      1. They presume correlation is causation.
      The problem here is if (for example) it isn't that black people are dumb and prone to criminal behavior because of genes but because they lack education, leaving them dumb and prone to criminal behavior is a waste of civil resources compared to educating them and having them become more productive.

      2. They ignore outliers.
      Outliers are frequently quite valuable and it's better to evaluate each individual on their own merits to avoid discarding them than it is to save time and assume that an individual will perform close to the median for their race. This is especially true when dealing with professions where you need better than average people in general. It doesn't really matter if a white genius is 1 in 100 and a black genius is 1 in 1000 if you need a genius and a black genius applies you should hire them rather than dismiss them on the basis that they're rarer.

    7. Re:GATTACA, anyone? by iggymanz · · Score: 1

      actually, many stereotypes are VERY useful, if something is true 95% of the time it's a useful generalization.

      Also, the turkey was doomed anyway, going for treat or not. So being friendly to farmer made life happier.

  2. Easy Fix by Anonymous Coward · · Score: 2, Insightful

    Just do multiple passes and match the commonalities. Should be an easy way to sort out the errors and make it much more accurate

    1. Re:Easy Fix by Pseudonym · · Score: 5, Informative

      That's what we do now with short reads. It kind of works, but only because we understand in a lot of detail about how errors happen.

      For example, 454 sequencing tends to get the number of nucleotides in a repeat sequence wrong. So, for example, CTAAAGT might be read as CTAAAAGT. Illumina sequencing doesn't have that problem, but tends to degrade along the length of the read. So the last few nucleotides are more likely to be wrong than the first few.

      And this is just read errors; with short-read sequencing, there are also PCR amplification errors, which is why we think nanopore sequencing will do better. When you start "unwinding" a chromosome, the parts that you unwind first tend to get amplified more than the parts that you unwind nearer to the end. Some sequences are amplified more than others for chemical reasons, and the relative error might depend on the specific revision of reagent chemicals.

      We don't really understand enough about nanopore sequencing to be able to develop appropriate algorithms to match long-read sequences together. We don't even know what the right number of multiple passes is yet. And that's important, because genomics and transcriptonomics are important, but the bigger issue for researchers is economics.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    2. Re:Easy Fix by TimothyHollins · · Score: 1

      Isn't the Illumina problem fixed by paired end reads on the rather short fragments?

    3. Re:Easy Fix by Pseudonym · · Score: 2

      Yes and no. Paired end reads give you either longer reads or longer range information. The problem isn't fixed because as the technology gets better we just push up the read length.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    4. Re:Easy Fix by nospam007 · · Score: 2

      "Just do multiple passes and match the commonalities. Should be an easy way to sort out the errors and make it much more accurate"

      Just like an idiot calculating stuff, making him do it multiple times and he'll will be a stable genius.

    5. Re:Easy Fix by bluefoxlucid · · Score: 1

      With machine learning, you can theoretically use a known set of good DNA reads to determine what needs adjustment. That, of course, requires a human to train the machine learning algorithm to better-interpret the data and learn properly. It also requires a lot of manual setup reading and rereading known DNA, as well as making adjustments to the hardware to decrease its error rate as you discover particular error conditions for which you can correct directly.

      Even with all the manual work involved, it's going to give you greater accuracy with less labor. It's not nearly as simple as measuring repeatedly and running a quick statistical analysis, as you observe: we've improved the technology of "counting" over the last decades.

  3. I would be interested by waltlaw · · Score: 2

    in finding out what kinds of DNA is in my pocket,

    1. Re:I would be interested by iggymanz · · Score: 1

      Your own, if you play "pocket pool"

    2. Re:I would be interested by gringer · · Score: 1

      You can find out yourself for the low, low price of $1000 USD. ... or wait a few months for SmidION to come out, which will be a bit cheaper, and plug into your iPhone or Android device.

      --
      Ask me about repetitive DNA
    3. Re:I would be interested by Pseudonym · · Score: 2

      String or nothing!

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    4. Re:I would be interested by mentil · · Score: 1

      Can't wait for Apple/Google to have my sequenced DNA information... what could possibly go wrong?!

      --
      Corruption is convincing someone that the selfless ideal is the same as their selfish ideal.
    5. Re:I would be interested by Anonymous Coward · · Score: 0

      Shaddap faggot.

    6. Re:I would be interested by iggymanz · · Score: 0

      Is that your fantasy about me; sorry I'm straight.

      Meanwhile, we found several faggots' DNA in your underwear's rear panel. You're what the Navy calls "a friendly port".

  4. Stumbling block. by Anonymous Coward · · Score: 0

    "Resisted characterization" and yet people know if there are errors there or not.

  5. Wrong use. by Templer421 · · Score: 1

    Just need to ID marker DNA sequences not the whole thing.

    Scanning for Flu. Searching for H1N1, Negative, H1N2 Negative........... H2N3 POSITIVE! Confirmation Scan? Y/N?

    1. Re:Wrong use. by Anonymous Coward · · Score: 0

      Flu viruses are RNA viruses, not DNA. But the same principle might work with some hardware changes.

    2. Re:Wrong use. by gringer · · Score: 4, Informative

      Direct RNA sequencing can be done with the MinION as well, no hardware change needed:

      https://store.nanoporetech.com...

      Depending on how important it is to sequence all RNA, polyadenylation prior to sequencing might also be needed.

      --
      Ask me about repetitive DNA
    3. Re:Wrong use. by Anonymous Coward · · Score: 1

      EBOLAIDS ... POSITIVE! Confirm plane reservation to Madagascar? Y/N?

    4. Re: Wrong use. by Anonymous Coward · · Score: 0

      Just need to ID marker DNA sequences not the whole thing.

      Scanning for Flu. Searching for H1N1, Negative, H1N2 Negative........... H2N3 POSITIVE! Confirmation Scan? Y/N?

      Are you the retard one or something?

      Maybe not all, but just a little bit, right?

    5. Re:Wrong use. by Anonymous Coward · · Score: 0

      A free ticket away from the shithole that is the US. Yes, please!!

  6. I have one of these... by wisebabo · · Score: 5, Interesting

    ... and it (kinda) works as advertised. It is also VERY low cost (compared to the previous generation of sequencing machines which cost 700K and up, it costs about $1K). The main disadvantages are that 1) it's still inaccurate, maybe only in the ~90% accuracy rate (not a good thing when you're reading 3B base pairs) and 2) the reagents and flow cell used are expensive (so on big jobs you're almost better off using a traditional sequencer). Still, it does do LONG reads which gets over one of the big disadvantages of the previous gen. machines.

    Even with a high error rate, if the errors are UNBIASED then you can overcome them by simply sequencing the same area over and over again to come up with a consensus. This is called "coverage" and usually a factor of 10X is used but if the sequencing technology is cheap enough why not do it 30X or 100X or more?

    For us citizen scientists, you'll still need a way of processing and purifying your DNA, I'm trying to get a Bento Lab (hopefully shipping in a month or two). Also the technology will hopefully get better and better, the next version will supposedly have the nanopore membrane separate from the flow cell so the whole thing won't have to be replaced when the membrane is used up. (The version after THAT supposedly will a tiny device directly attachable to an iPhone with an even tinier replaceable membrane so maybe it'll become really cheap to sequence DNA; at parties even :). Finally, I think they may be moving to freeze dried or otherwise non-perishable reagents so the storage requirements will become a little easier (I have a dedicated battery backed freezer at home).

    Now with CRISPR kits for only $40, there's no end to the fun (and disasters) that we can do with our basement genetic experiments!

    I should mention you'll need a little lab experience and know how to use a pipette and have steady hands! Go take some courses at the local community college and you'll be good to go. (Of course in order to interpret your results you'll need to study BioInformatics, my specialty :)

    1. Re:I have one of these... by Anonymous Coward · · Score: 0

      There are well-known DNA matching algorithms that you can use to match up your 100x runs of the same sequence to find errors, assuming the errors are in different places each time. They find optimal matching regions very efficiently, but it is still slow when you have billions of base pairs in the human genome.

    2. Re: I have one of these... by Anonymous Coward · · Score: 1

      I work for a major company pursuing orders of magnitude synthesis and sequencing more than just about anybody else in the world. We have a bunch of these things in addition to the more traditional sequencers. They fit our long read pipeline very nicely but I'd hesitate to use them on their own.

    3. Re:I have one of these... by Pseudonym · · Score: 3, Interesting

      it's still inaccurate, maybe only in the ~90% accuracy rate (not a good thing when you're reading 3B base pairs)

      Former de novo assembly software writer here. Do we have a good handle on the kinds of errors that you tend to find? You know how 454 reads tends to miscount repeat sequences and Illumina tends to decline in quality along the read. Do we understand where the errors come from?

      Also, are the errors correlated? If you try to sequence the same 500k read twice, will it make errors in the same places?

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    4. Re:I have one of these... by Pseudonym · · Score: 2

      Those algorithms, largely based on De Bruijn graph methods, are specifically designed to handle the short-read, high-coverage case. There's no reason to think that they will work well on the long-read low-coverage case.

      You might be better off just BLASTing them together.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    5. Re:I have one of these... by Anonymous Coward · · Score: 1

      Fuck the iPhone accessory thing.

      I want my DNA sequenced, but I don't want to hand it to some bullshit Cloud AI IoT App company that will sell my DNA to advertisers.

      "Hi! I see your sequence here is AGTAGG, would you like some hard liquor?"

    6. Re:I have one of these... by Cyberax · · Score: 1

      Former Illumina Long Read kit developer here. Nanopore reads are lousy with repeated nucleotides (to be fair, our kit also kinda was because of multiple PCR cycles needed) and it does have a certain GC bias.

      Right now regular Illumina short reads with a little bit of long reads are enough to get phased SNP information from most relevant parts of a human genome. It's also cheaper at scale, human genome sequencing at 3x can be done for less than $500.

      With de-novo assembly it's a bit different. Nanopores provide a good scaffolding for short reads, it's almost like magic.

    7. Re:I have one of these... by Pseudonym · · Score: 1

      Right. So for de novo (as noted, that was my field) it seems to me that the best approach might be to build and clean up a de Bruijn graph from short reads, and then align long reads to the graph to get contigs.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    8. Re: I have one of these... by Cyberax · · Score: 1

      I would do it the other way - align short reads on contigs made from long reads. No need for de Brujn graphs, simple OLC (overlap layout consensus) is sufficient.

    9. Re:I have one of these... by Anonymous Coward · · Score: 0

      I was actually thinking of BLAST as the likely best algorithm.

    10. Re: I have one of these... by Pseudonym · · Score: 1

      The benefit of doing it the other way is you can use existing efficient graph cleanup algorithms like tour bus.

      It will be interesting.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    11. Re:I have one of these... by gringer · · Score: 1

      minimap2 works better for long reads, and can be used in the Canu assembler as the overlapper component for doing read correction.

      --
      Ask me about repetitive DNA
    12. Re: I have one of these... by gringer · · Score: 1

      The benefit of creating scaffolds first from long reads is that it's a lot easier to capture regions where there is a Very-long Complex Tandem Repeat (VeCTR). These regions are collapsed in scaffolds assembled from short reads.

      --
      Ask me about repetitive DNA
    13. Re: I have one of these... by Pseudonym · · Score: 1

      That case would still work because CTRs correspond to a loop in the de Bruijn graph. The theory is that all true contigs are paths in the graph, and you can use the long reads to find each one.

      But I agree that you could do it either way and we don't know which one would be better until we have more experience.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    14. Re: I have one of these... by gringer · · Score: 1

      Not necessarily. If the unit length of the repeat is greater than the fragment length (I've seen tandem repeats with unit lengths of 40 kb), then the region will not be detected as repetitive.

      --
      Ask me about repetitive DNA
  7. Re:Use this to scan a woman's vagina by Anonymous Coward · · Score: 0

    Something tells me you won't be scanning a lot of vagina, scientifically or otherwise

  8. Just hope... by Anonymous Coward · · Score: 0

    no one gets convicted of a crime based on one of these things.

  9. Trap Detector by Anonymous Coward · · Score: 0

    Cuz traps are gay.

  10. Q&A from a previous time by gringer · · Score: 4, Insightful

    I did a Q&A on this sequencer on SoylentNews a couple of years ago:

    https://soylentnews.org/articl...

    The technology has improved substantially since then. Feel free to ask me any more questions about the sequencing. Although I'm not an author on this paper, I'm fairly familiar with the sequencing project that was done, and am happy to answer any general questions you might have on this technology.

    --
    Ask me about repetitive DNA
    1. Re:Q&A from a previous time by ngc5194 · · Score: 1

      Are the errors random, or are they consistent? That is, can we just run strands through enough times to get the error rates down to acceptable levels?

    2. Re:Q&A from a previous time by gringer · · Score: 4, Informative

      Some errors are random, some are systematic. The systematic errors tend to be either small shifts in long stretches of the same base, or interesting features of the DNA (e.g. methylation), and there are a few people trying to work out what those interesting features are.

      A key obstacle to getting people interested in nanopore sequencing (or other types of observational sequencing) is that we have been locked in for so long to the idea of DNA as a sequence of letters that we forget there are other things attached to it that also have functional roles. Nanopore is more accurate when matching sequences at the signal/electrical level, but almost no one is doing that yet.

      --
      Ask me about repetitive DNA
    3. Re:Q&A from a previous time by Iamthecheese · · Score: 1

      How long will it be before I'm turned down for a job because my genes are bad?

      --
      If video games influenced behavior the Pac Man generation would be eating pills and running away from their problems.
    4. Re:Q&A from a previous time by gringer · · Score: 2
      --
      Ask me about repetitive DNA
  11. Re: Use this to scan a woman's vagina by sg_oneill · · Score: 2

    Slashdot trolls in 2017 are fucking lame. Come on man put some effort into it. This is not /b/, itâ(TM)s Slashdot and our trolls traditionally put effort into their work

    --
    Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
  12. Misuse around the corner by Tablizer · · Score: 2

    Employers will use such under the table to screen candidates for medical and/or genetic problems. I've worked for slimebags who would happily cheat at anything to gain an edge.

    1. Re:Misuse around the corner by bluefoxlucid · · Score: 1

      Should I add this to the ACA?

  13. Re: Use this to scan a woman's vagina by Anonymous Coward · · Score: 0

    >in_my_day_trolling_meant_something.jpg

  14. Who remembers the Human Genome Project? by raymorris · · Score: 1

    This reminds me of the Human Genome Project. After a few years of trying to get funding for a fifteen year project to sequence the entire human genome, the Reagan administration allocated $3 billion to get started. It was "finished" 13 years later. Now this iPhone doohickey does it in seconds or minutes.

    1. Re: Who remembers the Human Genome Project? by Anonymous Coward · · Score: 0

      Cave Johnson here: Something about standing on the shoulders of giants, the lab boys told me.

    2. Re:Who remembers the Human Genome Project? by Anonymous Coward · · Score: 0

      I can tell your gene sequence without a doohickey, it seems to be 49% of your mother Billie and 49% from your uncle Bob and you have in general radically less grandparents/great–x–grandparents than expected.

      Inexplicably, there is a small trace of goat DNA in your genome.

  15. Re: Use this to scan a woman's vagina by EETech1 · · Score: 1

    They're even worse this year:)

  16. Re: Use this to scan a woman's vagina by sg_oneill · · Score: 1

    Fair point!

    --
    Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
  17. Re: Use this to scan a woman's vagina by EETech1 · · Score: 1

    Allow me to be the first to wish you a happy New year:)
    Cheers!

  18. usb dna reader by MancunianMaskMan · · Score: 1

    bring on the DNA-reader PAM module so I can log into my laptop by licking instead of swiping my finger. on second thoughts, maybe not a good idea because everyone can get a spit sample and log into my linux...

    1. Re:usb dna reader by Anonymous Coward · · Score: 0

      I've got something you can get into by licking.

    2. Re:usb dna reader by Anonymous Coward · · Score: 0

      I licked it, therefore its mine!

  19. Re: Use this to scan a woman's vagina by Anonymous Coward · · Score: 0

    Your heart is true, you're a pal and a cosmonaut. -PCP

  20. Reminds me proteomics by DrYak · · Score: 1

    Nanopore is more accurate when matching sequences at the signal/electrical level, but almost no one is doing that yet.

    Reminds me matching peptide sequences at the mass-spectrometry level in proteomics (Disclaimer: used to work at GeneBio).

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  21. Assembly and errors by mapkinase · · Score: 1

    There are two plagues in current WGS: errors in sequence: frameshifts on monomer runs, flaky stop codons in the middle of ORFs etc, and problem of assmbly of short reads in repeated sequences.

    This method helps the second problem.

    Errors in sequence can be minimized by doing things several times.

    --
    I do not believe in karma. "Funny"=-6. Do good and forbid evil. Yours, Oft-Offtopic Flamebaiting Troll.
  22. Re: Use this to scan a woman's vagina by Anonymous Coward · · Score: 0

    The correct response: "Use it to scan OP's mouth."

  23. The Back Story To 454 by Anonymous Coward · · Score: 1

    Someone mentioned 454?

    To the best of my knowledge, 454 was a small company on the East Coast, maybe New Hampshire? They were acquired by Roche; the whole operation was moved west.

    Did I say the whole operation? Well, they picked and chose who they wanted and who they didn't. In the case of the IT department, they brought exactly one guy west, and, I infer, laid off everyone else.

    I came in as a contractor - I gathered the impression that part of the deal involved a two-week-long, all-expenses-paid vacation in Hawaii for the brand new IT manager of the brand new Roche Molecular Systems business unit, staffed with former employees of 454, and I was employed by Roche, on a six month contract, starting by covering for the IT manager while he took his two-week-long vacation.

    It was during this period that the manufacturer of the pocket-sized DNA sequencer announced their new product.

    I tried to discuss this new product with some of the people I was working with but they were uninterested and/or hostile towards the concept. In retrospect, this makes more sense once you realize that Roche manufactures huge DNA sequencing machines the size of a desk, and that the new equipment rendered their six-figure hardware as obsolete as dinosaurs.

    The week after the IT manager came back from his vacation he terminated my six-month-long contract. In retrospect I do not believe that Roche intended to employ me for six months, and I believe that they entered the contract in bad faith.

    I think one of the things he was angry at me about was that one of the 454/Roche researchers had asked me why 23 of the 24 CPUs in her team's Linux boxes were idle, and I had replied - drawing upon my three decades of experience with parallel processing R&D - with a brief tutorial on sequential versus parallel processing, including URLs to tutorials, Wikipedia pages and Python libraries. I pointed out the command-line utilities available under CentOS for binding processes to specific cores, and the utilities available for measuring performance (uptime(1), for instance, quite properly displays a line for each of the 24 CPU cores). I explained that software had to be written differently in order to run in parallel. I introduced her to the concept of 'threads'. All part of my job, I thought.

    I later discovered there was some sort of history here of conflict between the researcher(s) and 454, going all the way back to the East Coast, perhaps. The researchers had attempted to install their own instance of Nagios so that they could measure performance - perhaps because they did not feel that they were getting good or useful information from their IT support personnel - and the IT manager who I was filling in for, had DELETED their entire Nagios installation.

    I felt really sorry for the researchers. They were just scientists, trying to get hard numbers, and here was IT, not being helpful, but being POLITICAL - "That's MY job!" - and actually DESTRUCTIVE. It boggled my mind.

    I've played all of the roles in these sorts of dramas. I've been the guy laid off. I've been the guy who stayed. I've been the guy who boxed it up and shipped it. I've been the guy who received the shipments of equipment, unpacked them and re-installed everything.

    The one role I've never played is the Judas who betrays my peer IT employees. I don't do well in environments where I have to withhold information from the people I work with. I've always done better in collaborative environments.

    Nor have I ever destroyed Nagios installations. I would be THRILLED to have a PhD who wanted to know more about the IT side of things. Such a person would be more willing to return the favor and share information from their side of the fence. We would both benefit as a result; and so would the company we worked for.

    It's too bad Roche wasn't the collaborative, R&D-oriented environment I thought it would be. I miss those days.

    Just sayan'.

    1. Re:The Back Story To 454 by Anonymous Coward · · Score: 0

      s/uptime/top/

  24. useful fir characterizing 3rd plagues by Anonymous Coward · · Score: 0

    Wont have to ship samples to first world countries

    1. Re:useful fir characterizing 3rd plagues by gringer · · Score: 1
      --
      Ask me about repetitive DNA
  25. Genetic counseling by Anonymous Coward · · Score: 0

    I would greatly consider paying the $1000 fee for the MinION, if it would save me $10,000+ in specialist fees and gas for diagnosing my daughters possible illness/disease. We've been told by numerous other specialists that we need to be seen by a geneticist to see if she has any genetic disorders causing her symptoms. Which we would gladly do, if her insurance would stop denying the referrals and pay for the testing.

    If it was a simple way of finding out if you/someone had the genetic markers for certain inherited illnesses, I would gladly forego the migraines of dealing with insurance and purchase the MinION and provide my daughter's pediatrician with the results.

    So, my question is.. is this possible with this device? If so, how hard is it to use to look for these markers, and how reliable is it. If it's as low as 80% accurate, I would still consider it, if I could decypher what I was looking at.

    1. Re:Genetic counseling by gringer · · Score: 1

      The MinION is really good at finding structural variants (i.e. large-scale changes in DNA sequence), but not so good for single point variants (accuracy for single base-called sequences is 85-95%, getting to about 99% in consensus; accuracy is much higher at the signal level, but there are no well-developed programs that do variant matching/detection at the signal level).

      I try to encourage people to use the first $1000 for a pilot run, just to see if the MinION is suitable for what they want.

      Finding causal genetic variants is tricky, particularly where multiple places in the genome can influence whether or not a disease appears, and people might appear normal, but be carriers for those variants. A common approach is to compare the patients genome with known unaffected genomes; finding a few other people with the same condition makes the search a lot easier because then it's possible to exclude a large amount of genetic variation from the "cases" as well as control genomes.

      It can be done, and the resources required to enable anyone to do it are publicly and freely available (most importantly is probably R/Bioconductor and the 1000 Genome project); just don't expect it to be easy.

      --
      Ask me about repetitive DNA