Giter Site home page Giter Site logo

Multiple paths per variant about kevlar HOT 4 CLOSED

standage avatar standage commented on September 8, 2024
Multiple paths per variant

from kevlar.

Comments (4)

standage avatar standage commented on September 8, 2024

Increasing k ≥ 15 solves the second case, but not the first.

from kevlar.

ctb avatar ctb commented on September 8, 2024

I wonder if this is caused by false positives? You might try calculating cg.kmer_degree and then taking a look at @camillescott's JunctionCountAssembler code in dib-lab/khmer#1502

from kevlar.

standage avatar standage commented on September 8, 2024

If it's a CountMinSketch FP, this should be handled by loading reads with interesting k-mers into a separate node graph.

from kevlar.

standage avatar standage commented on September 8, 2024

Reviving this dormant thread.

As far as I've been able to tell this issue has been caused primarily by sequencing errors. khmer has plenty of scripts and functions to deal with this, but we for a while we couldn't come up with the secret QC sauce. Trimming or error correction was never feasible for the raw data. Variable-coverage trimming had weird and unintended results on the boring-reads-dumped data. Digital normalization would provide at best a marginal improvement with a risk of loss of sensitivity (lower risk but also lower benefit by raising normalization threshold). So alas, the last few months I've devoted time to, among other things, implementing a greedy assembly algorithm from scratch.

In implementing the assembler, we came up with an approach for partitioning the reads based on shared interesting k-mers. This turned out to be much more useful than khmer's partitioning code, and led to a great discovery: running abundance trimming (not variable coverage trimming!) on each individual partition, followed by greedy assembly, produced reliable contigs!

This morning, I was curious and revisited kevlar collect which I had all but deprecated (this uses khmer's linear path assembly). Turns out, running this on individual partitions that have been abundance trimmed also seems to produce reliable contigs. Sigh.

So it looks like the breakthrough, ridiculously simple in retrospect, is to partition interesting reads by shared interesting k-mers, and then do abundance trimming and assembly on individual partitions. Assembly details may or may not make much of a difference.

from kevlar.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.